Top Influencers











See all Requirements Management Influencers

Advance Your Career

The Four Levels of Agile Requirements

PREMIUM on-demand webinar

This webinar is dedicated to discussing the 4 levels of requirements and why it is important to gather the right level at the right time and not dive into the details too early. Sally Elatta will discuss 4 techniques for slicing EPICs into smaller deliverables and also share how you can use Business Value Points for prioritizing features. Whether or not you’re using Agile, you will absolutely walk away with tips to help you improve your current requirements approach.

Integrating Value Engineering and Project Management

PREMIUM on-demand webinar

Project Management (PM) is a vital globally accepted tool that provides best practices to help ensure successful project delivery. Requirements relating to cost and value require special attention. This presentation will discuss the integration of value engineering and project management to increase understanding and improve project delivery. 

Blog Insights

Requirements Management Ruminations

by Sally Elatta, Abdulilah Angaa, Victoria Cupet, Beth Ouellette, Elizabeth Larson, Rich Larson, Mike Frenette, Mary Gorman, Ellen Gottesdiener, Jhansi Vijayarajan, Bobbye Underwood, Cameron McGaughy

A collaborative blog with contributions from members of the PMI Requirements Management Community of Practice and various authors and presenters who have dealt with the topic of requirements management.


by Michael Joseph Frenette

Effective requirements collection, management and traceability plus smart PM practices equals project success.

Save Time With Tools And Templates

System Requirements Specification

PREMIUM deliverable

The System Requirements Specification (SRS) document describes all data, functional and behavioral requirements of the software under production or development.

Strategic Requirements Template


This deliverable aligns with the concepts expressed in the article Strategic Requirements Management. This template should be used in conjunction with a more traditional requirements document to assist in the prioritizing of features and the finalizing of scope elements. It can also support discussions around changes in scope during the project. The cells below provide a basic summary of each column.

Requirements Management Plan


The Requirements Management Plan is primarily used for communications, giving all stakeholders a view on how this process is managed for your project. It completely answers the very common question, "How are you identifying and managing your project requirements?"

Project Impact Analysis on Scope

PREMIUM deliverable

Even a small change can have a huge effect on a project. This impact analysis study will help you measure the effect of a potential change on your project's scope.

Requirements Candidate Summary


This planning guide will help you with the review and selection of project requirements to be included in the current scope. All requirements candidates are captured here, along with some basic information about them. Each candidate is then scored based on a number of different factors. The completed template provides a validation that the requirements ultimately approved are the ones that are the most appropriate for inclusion.

Project HEADWAY Change Request Log

PREMIUM deliverable

The primary purpose of this document is to track the status of change requests that have been created on the project. For smaller projects or projects where the scope is well defined, the log may not be useful. For larger, more complex projects, or for those projects where there is a lot of change, a change request log can be very useful.

Project Scope Statement

PREMIUM deliverable

The project scope statement details your project's deliverables and describes the major objectives, which includes measurable criteria for success. Use this template to document the six essential elements.

Learn From Others

Effective Requirements Writing

by Kenneth Darter, PMP

Every project has requirements, but if they aren't written well from the very beginning then it's highly unlikely that they will be met. Following these four guidelines will help the requirement writer get a good start on writing effective requirements that will filter through the entire project lifecycle.

Business Needs: Are Projects Aligned?

by Jiju (Jay) Nair, PMP

Extensive studies and industry surveys over the last decade have revealed that lack of alignment to business needs is a major factor for project failure. Recent trends have indicated that project teams continue to cut corners during the planning stages of the project even while exploring options to elevate their project success rates. Are you practicing effective requirements analysis and management?

The Dimensions of Change in Requirements Management

by Victoria Cupet, Michael Frenette, Salah Haswah, Thea Hughes & Leandro Mingoti

Although requirements define the desired state of the organizational change, they are themselves subject to change. Regardless of the whether a project is using a traditional or adaptive framework, controlling changes through established processes is necessary. Learn about four steps to create a common vision and get the necessary commitment and compliance from the involved stakeholders.

Use Cases or User Stories: Where Should Agile Teams Start?

by Kevin Aguanno, PMP, MAPM, IPMA-B, Cert.APM, CSM, CSP

Should an agile team begin with requirements documented as use cases or user stories? Proponents from both sides of the debate make good arguments, leading to confusion for many who are just getting started with agile practices.

Being a Great Sponsor

by Michelle Stronach

Being a sponsor is a role, not a position--and with the role comes responsibility. How do you ensure optimal success for the project? How do you go from being a good sponsor to a great sponsor?

Rules for Surviving a Project Zombie Apocalypse

by Rob Saxon

Project issues and risks, like zombies, move relatively slowly. It’s extremely rare that a project manager will be introduced to a project one day and be overwhelmed by the same failed project the next. Therefore, like survivors of a zombie apocalypse, project managers have time to prepare--and to look for those indications that projects are turning...

From Bad to Worse

by Andy Jordan

Some projects turn bad without warning. On other occasions, you can see the problems coming--yet it seems as though there's nothing you can do to prevent them. Think you're a Super PM who can save the day? Think again...

Ready, Set, Go...and Ready Again: Planning to Groom the Backlog

by Andy Berner

For an agile project to progress smoothly, the backlog must be groomed and ready for each sprint. That work must be included in your project plan. This article gives you five points to consider when planning that work.

Three Requirements Gathering Warning Signs

by Joe Wynne

A successful requirements definition phase takes a lot more than a good BA and enough time. There are time bombs hidden out there, but you can find them if you listen for the ticking. Here are three problems that can blast the success of your requirements gathering, how to spot them and how to react constructively.

Ask a Question

Discussion Rules

Recent Questions

Topic Originator Last Post New Total
how does project management differ from general management practice  Errold Mathibe  May 23, '14 6:15 PM 
What are the most common requirements management mistakes?  Andy Jordan  May 23, '14 5:56 PM 
Scope management and requirements management  Elizabeth Harrin  May 23, '14 5:29 PM 
Best practices for requirements management  Andy Jordan  Feb 17, '14 2:13 PM 
  Mark All Read
See All Questions

"In youth we learn; in age we understand."

- Marie von Ebner-Eschenbach