3 ms·
The agile manifesto was never intended to be a value proposition for the business per se, it was intended to be a promise of professional discipline. You don't
by zdragnar 9y ago
The agile manifesto was never intended to be a value proposition for the business per se, it was intended to be a promise of professional discipline.
You don't ask the business if a refactor is okay, because the business doesn't know how to value or risk it. You refactor because that's what a disciplined professional does, in the course of their work.
Think of another profession, if that helps. Teachers don't ask students or administrators if a test would be valuable after a given lesson. Builders don't ask if a hammer would be appropriate for a nail, or if they should use an air gun. There's a certain expectation that they should know and do these things.
Scrum works if the scrum master functions as a mediator for the team to collaboratively prioritize work- ideally, this would be a role, not a job title. Scrum fails if the scrum master is just a project manager tasked with making sure the whole backlog entered by the product owner is done on time.
- sanderjd 9y agoI think I agree with you, but I find your analogies quite lacking, which makes me question our shared premise. Teachers absolutely do have the cadence of tests after lessons dictated to them by administrators. Builders absolutely do negotiate with their customers over whether their "implementation" is sufficient or whether it should be "refactored" (ie. partially or completely torn out and re-done to improve the quality). I'm not sure where this leaves things, but it seems to me that the differing incentives and negotiation between stakeholders is perhaps inevitable.
- zdragnar 9y agoI realized as I wrote it that the analogies were flawed, but I rushed myself a bit to finish writing. The teacher analogy depends entirely on the school district, and perhaps might apply more to a university setting than a grade school one. As for the builder, of course there's a discussion between the builder and the client... On the desired results. What a disciplined builder won't do is ask "can we" when they know that the current status is structurally unsound or flawed. There's some substantial differences in cost / financing and risk between the professions, so it's a bit of a stretch no matter what, I'll grant you that. If we can at least agree that there is a certain amount of discipline that embodies a profession, and that the agile manifesto emphasises priorities characteristic of that discipline (correctly or incorrectly) rather than a "business process" or "project management" scheme, then I think we're agreeing on the important points.