Please login or join to subscribe to this thread
Requirements Management Plan is part of the PM Plan which is done during the planning phase following the initiation of the project. Prior to project initiation, business case and measurable objectives are determined.
I agree, projects should not rush because although it is an iterative process, yet they mind start with the wrong or different requirements that can best suit the project.
It depends on the organization's project management maturity.
there are certain organizations which follow copy book style of BA and then project is initiated. In that case, BA should be defining the requirements (in detail or high level) along with business case, which will be initial documents based on PM can work on.
In certain other organizations, new initiatives are directed to PM and both BA and PM is done by PM.
In any case, requirements elicitation is definitely required in order to understand and clearly state the expected output from the project
You as the PM are under tight deadlines. Your sponsor asks you to hurry the requirements up. What is your response?
Requirements should not be rushed into as what a project delivers as part of product is dependent on this. Having said that how much elicitation is needed or how deep one should go is dependent on the nature of the project and also the organization maturity.
With regards to "expectations for the business analysis process and the road map for pursuing the work", this should be done before the requirements elicitation and should be part of project charter and business case.
And I couldn't agree more about "how much" elicitation is needed. That seems to be the never-ending debate of how much is enough, but so long as the risk is called out not to go to far to either extreme, I believe as a practice we are making progress.
Please login or join to reply