It’s got to be more effective to deliver each minimal marketable feature to production, without delays, where it can earn value for the business than to batch and queue unvalidated decisions . Hasn’t it?
AGILE IN ACTION
Search Posts
-
This work is licensed under a Creative Commons Licence
Recent Posts
- System failure is inevitable so design for a fast recovery
- Delight comes as a surprise in unexpected places
- Help create business agility. Bake quality in
- Governance - Friend or Foe?
- 70% Forum
- Measuring purpose. Measuring customer delight
- Stop pushing features and start delighting users
- Lost without a goal
- Emotion creates the common language
- Five sneaky ways to kill an initiative
Archives
- ► 2012 (16)
- ► 2011 (24)
- ► 2010 (31)
- ► 2009 (41)
- ► 2008 (69)
-
▼
2007 (152)
- ► December (11)
- ► November (7)
- ► October (17)
- ► September (8)
- ► August (7)
- ► July (13)
- ► June (15)
- ► May (24)
-
▼
April (14)
- Does the Agile Manifesto need refactoring? Should it be extended?
- Self-management and self-leadership
- Improve quality to increase productivity
- Self-organisation again
- Breaking habits
- Self-organisation
- Put customers first and everything else follows
- I just came from there ...
- Defect tracking tools and waste
- Individuals and interactions over processes and tools
- Are you missing the point?
- Scrum Master, Master of Ceremonies and Quartermaster
- When you put it like that ...
- Become a certified Agile Software Specialist!
- ► March (19)
- ► February (7)
- ► January (10)
- ► 2006 (128)
- ► 2005 (63)
- ► 2004 (2)
2 Comments
NO, it hasn’t got to be more effective to deliver each minimal marketable feature to production, because those features don’t instantly and automatically earn value for the business (at least not for the kind of B2B commercial software business that I work in). In my world, new features only earn value when their release is accompanied by a host of supporting activities involving operations, order fulfillment, technical support, professional services, and sales. If those activities aren’t properly planned, coordinated, and executed, the new feature in question may actually destroy value rather than earn it. For that reason, it makes more sense to coordinate the release of multiple features at once. That said, I'm strongly in favor of frequent, small releases. Just not too small or too frequent. We do them quarterly.
Hi Andy
Sounds like you're working in an enterprise organisation. Let me ask a question: If you could reorganise whatever you wanted, say the composition of the team, would it be possible to include those things you list as part of the 'marketable feature' and it's delivery? If not, could you please elaborate on the types of obstacles you would anticipate.
I think this is a common challenge facing a very agile and lean approach. So it would be interesting to hear your thoughts.
Simon.