Requirements Definition - Project and Outcome Success Drivers, PMI's Road Map: Q&A

Allan has provided ERP project implementation services for over 17 years to clients in the United States, Canada, Mexico, United Kingdom and France. His engagements covered supply chain, fulfillment chain, and manufacturing processes.

  Business Analysis   Requirements Management  

Our webinar Requirements Definition - Project and Outcome Success Drivers, PMI’s Road Map with Allan Meltzer was incredibly popular. Here he offers advice based on your questions that he was unable to address during the session.

1. If scope requirements originate from the sponsor and the rest of the stakeholders, and if these requirements are met, why isn’t business value provided?
At the sponsor’s level, the requirement is normally an overview statement (mission or goal) describing the product, service or event. It’s an input to the initiating process where the business case and project charter are developed. The sponsor’s stated requirement goes through the business analysis phase to a further level of detail that will allow the requirement to be verified and validated that intended business benefits goals and objectives are achievable.

2. How does the definition of requirements management vary for agile projects? Often, there is no clarity on requirements. How can I elicit requirements and prioritize them?
There are many methods that are available to elicit and prioritize requirements. The objective is the same, to get to a definition that is clear, concise and verifiable. Based on the nature of the project’s outcome, different paths are taken. One kind of path has requirements complete before the next phase can start. …

Please log in or sign up below to read the rest of the article.