By: Chris Sims
Agile evangelists claim that extensive written requirements can be dispensed with in favor of lighter-weight 'stories'. It sounds easier, certainly, but can it really be as good? Won't all of the important details get lost?
This Thursday, I'll be staging a participatory showdown between traditional and agile requirements at the East Bay Innovation Group's Project Management SIG Meeting. The event is free for eBig members, and $10 for guests with advanced registration.
May the best requirements win!
The issue will hinge on whether Agile can create long-term profitability windows. With shorter cycles and less dense code, it is too easy for fast followers to erode your premium.
This leads to layers with different release schedules. Each Agile, but outwardly waterfall.
Or, do you put everything on a server to keep it out of the decompiler and reverse engineering environments.
Posted by: David Locke | May 19, 2009 at 08:59 PM