Getting requirements right: avoiding the top 10 traps.
Development teams anticipate the traps of requirements management and intentionally subvert the creation of accurate budgets and timelines.
Products today increasingly depend on sotware to deliver their value. A brakesensor on a car, a home appliance, a medical device—these products all containsotware that plays an increasingly important role. The products are becoming smarter, and they involve more people and teams outside the typical value chain.Smarter management o the requirements process—the oundation o efectivesotware delivery—is increasingly important or delivering these smart products.This white paper presents 10 common and devastating mistakes that project teamsmake in dening and managing requirements. More important, it discusses howto avoid these traps so you can get your requirements right and develop the rightproduct on time and within budget.
Indicated that their project teams will extend theschedule so as to deliver on the promised scopeDescope towards the end of the project tomeet the deadlineHave a flexible budget from the beginning of the projectChange the original schedule to reflect the actual resultsPad the budgetHave a flexible schedule from the beginning of the projectHave a flexible scope from the beginning of the projectWill ask for extra fundsAvoid “scope creep” whenever possible via a “change management” processChange the original estimate to reflect the actual resultsTake a stage-gate approach to funding72%10%12%13%18%18%26%32%34%39%63%10 20 30 40 50 60 70 80
State of the IT Union Survey
Poor requirements management results in inconsistent project outcomes.