I agree with your post. I think alot of the misunderstanding arises because people equate software development with project management where the cardinal sin is not to meet the deadline. IMO, this should be replaced with a “quest for value” where software developers and other stake holders communicate regularly about whether the feature set is sufficiently rich, coherent and debugged enough to trigger it’s roll out. It is a process that needs a certain amount of open-endedness to produce the “value” that all parties are ultimately “questing” after and will “discover” when the project starts to to come together. The metaphor of a “quest” is probably more descriptive of the software development process than the metaphor of a “project” governed by deadlines.
My comment to developers has been that if they see their job as to simply implement what’s on the card, their job might as well go to the cheapest offshore supplier
I agree with your post. I think alot of the misunderstanding arises because people equate software development with project management where the cardinal sin is not to meet the deadline. IMO, this should be replaced with a “quest for value” where software developers and other stake holders communicate regularly about whether the feature set is sufficiently rich, coherent and debugged enough to trigger it’s roll out. It is a process that needs a certain amount of open-endedness to produce the “value” that all parties are ultimately “questing” after and will “discover” when the project starts to to come together. The metaphor of a “quest” is probably more descriptive of the software development process than the metaphor of a “project” governed by deadlines.
My comment to developers has been that if they see their job as to simply implement what’s on the card, their job might as well go to the cheapest offshore supplier