March 8, 2012 at 10:01 pm #155611
March 22, 2012 at 4:35 pm #155613
I’d explain that the costs are roughly the same as what you would see with a traditional approach. You see, the (probably many more) business analysts will disperse and interview the user/customers and then also have to find some mechanism to reconcile disparities (this is usually far from transparent). Or you’ll bring everyone together in several group workshops then usually have to deal with the time arguing among different viewpoints (if people don’t hold back).
Using an Agile approach and getting a committed customer (and in particular a product owner), you take about the same time, but entrust the growth of your product to the business as opposed to having some form of reconciliation occurring within IT. Additionally, you are only performing the story development just in time; if you deliver enough value early, you can defer the costs. You also reduce the risk of getting things wrong due to having captured everything upfront and the environment changing.
I view using an Agile approach and stories not having a cost reduction effect, but a risk reduction effect:
– more clarity of requirements
– more control to the business (and thus meeting more user’s needs)
– smaller chunks
Hope that helps!
You must be logged in to reply to this topic.