When "Working software" is NOT a good measure of progress
Software is like surgery. Nobody wants surgery.
Is "Working software" really the primary measure of progress?
If the goal is to uncover better ways of developing software then, well, yeah.
The biggest challenges of incremental software delivery
Incremental/iterative software development challenges many of our deeply-ingrained assumptions about efficiency and control.
Why "Plans are worthless, but planning is everything" is (usually) BS
I'd rather see a conversation about planning, rather than ending debate with a cheap quip.
Subscribe to the Daily Commit
Every day I write about improving software delivery at small companies like yours. Don't miss out! I will respect your inbox, and honor my privacy policy.Unsure? Browse the archive.
If we don't use story points, how do we measure team effectiveness?
With respect to Goodhart's law, the DORA metrics are a place to start.
Reader question: Alternatives to Story Points for Sprint planning
My opinion is that days are usually better than story points, for the simple reason that they're less confusing.
When Theory of Constraints fails
Theory of Constraints is powerful, but like all models, sometimes wrong.
No, "Project Management" is not anti-agile
Even the manifesto talks about projects. So where did this idea come from?
Cross-team dependencies should be low-context
Cross-functional teams or highly specialized teams? Both can work, but the latter requires low-context dependencies.
How unplanned work affects flow vs batches
How does your team respond to unplanned work? Does it lead to crunch time?