August 1, 2012 by Stephanie SUTANTO
No one admits it but software planning and the steps involved – requirements – are just guesses in disguise. Software managers typically devote a large amount of time in pre-planning, outlining every possible scenario, use case, back-end integration point, and business rule. Then they build a project plan, assign a team or choose a vendor, set a ship date, and are inevitably disappointed, frustrated, and compromise vast sums of money if the software fails to take off.
Instead of all this guessing, shouldn’t requirements be treated as mere hypotheses, and be worked on quickly to figure out if they’re right or wrong? Read more