Agile Development adapted

"The mix of Customer Development and Agile engineering dramatically increases the odds of new product and company success, while reducing the need for upfront cash and eliminating wasted time, energy, money and effort." - Steve Blank and Bob Dorf

The figure above is a summary of the changes suggested here for the Agile Development process. They are:
  • Distribute one MVP for each development team. (One MVP
  • Constantly interview end users and measure the degree of use of each feature being added to the production environment. (End User Acceptance)
  • Minimize the agile meetings for planning and estimates by changing them to a quick task prioritization based on empirical data extracted from the production environment metrics. (Mini Iteration Plan
  • Engaging the development team directly with end users, so that developers have the right inputs to create the best solutions for software that is being built. (Improvement Meetings
  • Quickly create tasks, dynamically, based on the data extract from the measurements of the software use. (UDD)

Unfortunately, the "Customer" word in the Agile Manifesto, not necessarily means the end users. It is normally interpreted as the Product Owner or the person that is paying for the software to be built, but not the person that is actually going to use it.

"Agile Development is just a better and fast Waterfall. What we need is a new software development model."

Working vs Viable

Wich ones are VIABLE implementations?


While you don't have real users using the product, you can't say it is viable.


No comments:

Post a Comment