By Chuck Fitzpatrick
Agile Evangelist and Project Manager
Cloud City Development
Excerpted from Chuck’s posting
Question: What’s the best methodology?
Answer: It depends.
In the early decades of software development, the emerging industry followed the models of engineering that had served the world well for all of modern history. Collectively, those methodologies can be described as “anticipatory.”
As time passed, the software development community found that many large projects failed because those assumptions proved to be largely incorrect. Product consumers have no idea what they want—they change their minds constantly, so our ability to predict what they want is . . .impossible.
There have been many attempts to address the underlying issues that cause failures in product development, whether they are software or non-software products. The attempts that are proving to be successful turn those earlier assumptions on their heads:
1. Make implementation a part of requirements discovery
2. Incrementally grow the system
3. Flatten the cost curve: If you can keep the cost curve flat, then not knowing what to build today is less of a concern, since the cost to build it later, when you know more, is the same.
I am fascinated with the many ways that humans have created to make the difficult bits and pieces of creating new products move forward in the best possible manner.
—>NOTE: This is a DIGITAL EVENT at your location on your device where-ever you are!
The Agile Business Gap describes the methodology gap between that exists between the origins of an idea or a market insight and the creation of an initial (and ongoing) product backlog of user stories. At it’s core the Agile approaches that we see are software development focused and in most cases anything that is beyond the boundaries of the Product Backlog and a release is largely ignored by any of the Agile methodologies.
“I’m looking forward to discussing how we have applied components of our Product Development Framework to the Agile Business Gap, in a way that embraces the core philosophies of the Agile approach,” states Nick.
NOTE: DAY & TIME!
Monday, April 22, 2013 at the simultaneous times of 3:00 PM PT, 6:00 PM EDT in New York, and 8:00 AM AEST Tuesday, April 23 in Sydney, Australia
Background resources: http://bit.ly/YXRSko
Mark your calendar with the correct time: http://bit.ly/173wtb8
Follow for reminders: http://bit.ly/nbw9Yr
Curated Content: http://bit.ly/TV4Dsp
Questions for Discussion:
PreQ: Please introduce yourself, where you are tweeting from & your involvement with #prodmgmt #prodmgmttalk
Q1 What is the Agile Business Gap?
Q2 Where do you see this Agile Business Gap being a problem?
Q3 Is there a way of closing the Agile Business Gap in larger businesses?
Q4 So what do product managers actually have to do to bridge the Agile Business Gap?
Q5 How does a business start closing the Agile Business Gap?
Q6 What barriers do you see to being able to
close the Agile Business Gap effectively?
See on www.meetup.com