TDD:
Write no production code without a failing test.
Stop writing that test as soon as it fails, or fails to compile.
Stop writing production code as soon as the failing test passes.
Refactor both and then repeat.
Cycle time: ~10-60 seconds.
Political polarization is an illusion created by media, politicians, and ideologues for financial and ideological reasons.
Most of us actually agree about most things; and would support reasonable compromises if we could see through the fog of misdirection.
HERE IT IS! THE BIG NEWS! OVER 20 YEARS IN THE MAKING! EARTHWORM JIM IS BACK! WITH THE ENTIRE ORIGINAL TEAM AND EXCLUSIVELY ON THE INTELLIVISION AMICO!! LIVE CHAT WITH THEM DURING OUR 1ST DESIGN MEETING THIS SATURDAY! PRESS RELEASE: https://t.co/cKRPUcprzH
IMHO, it's not at all Agile for stories to be funneled to the team from a "product" organization (or worse, an executive team) via a PO. The stories should emerge from the team as a result of the team talking to customers on a regular basis.
You can do Scrum until you're blue, but if you're fighting your code to make small changes, agility is impossible. Fix that first. Bad code costs real money and adds real delay. The cost of that delay often easily exceeds the cost of a rewrite.