What's NewSeminar: How to Capture Customer Requirements and Develop Project Scope
Gregory D. Githens will provide pragmatic techniques for capturing, specifying and managing requirements. 2-3 April, 2014, Scottsdale, Arizona.
Can you afford project and program failures?
The same complex global environment that makes project success so important has also impacted the way requirements management needs to work. The pressure is on to deliver the right results, on-time and on-budget – and your organization can't afford needless project and program failures caused by weak requirements management or inaccurate requirements gathering.
Changing customer demands, new technologies, evolving competition and financial uncertainty mean that you shouldn’t just define the outputs of a project or program. Instead, you need to:
- Empower stakeholders — both internal and external — to be proactive in project planning by defining the short- and long-term business results that must be met and the associated metrics to show benefits realization.
- Allow project and program managers to make trade-offs in order to reach important strategic targets rather than simply delivering inflexibly defined outputs.
- Focus less on management and control; focus more on being adaptable to the real-life factors you and your project will face.
With a solid understanding and application of requirements management practices, you can reduce project and program failure — and more fully meet the needs of both your customer and your entire organization.
Improve your practice of requirements management
Use this page for resources and updates you can use to both gain a solid understanding of requirements management and continuously improve your practice of it.
Complexity is Increasing
Let's talk about complexity. On average, how many requirements does a project contain?
Building great products? It's hard. And it's not getting any easier.
More than 70 percent of projects contain at least 100 requirements, and 20 percent of project contain at least 1,000. That's a lot of requirements to track.Source: 2011 The State of Requirements Management report, Jama Software