Appendix 7
Business Requirements Work Plan Template
Business Requirements Work Plan (RWP)
<< Project Name >>
Date prepared (or updated): |
|
Prepared by: |
|
Project sponsor: |
|
Project customer: |
|
Project manager: |
|
Business analyst: |
|
Project ID: |
1. Requirements Work Plan (RWP) Objectives
The objective of this document is to provide details on how the analysis phase of the overall project will be conducted. It describes the methodology, plans, and resources to be employed in creating a Business Requirements Document (BRD), which will ultimately become the blueprint for all subsequent project work. When completed, this RWP should actually be integrated with the project plan to reflect the work to be done during the analysis phase of the project.
2. Deliverables
The primary deliverable of the effort described in this RWP is production of a formal Business Requirements Document, which will then serve as the key project reference for developing and implementing appropriate solutions.
3. Scope
The scope of this document is limited to efforts directed at producing a BRD for the project as it is defined by its charter. It is not the scope of this RWP to actually provide conclusions or recommended solutions. This is a planning document intended to clarify the level of effort, funds, and time needed to conduct the analysis required to position the project for success.
4. Participating Stakeholders
Specify which representatives from each of the following areas will be contacted as deemed necessary to provide a comprehensive understanding of the business requirements pertaining to this project:
■ Sponsors, who contribute directly to the project in terms of resources (funds, labor, equipment, supplies, information, etc.). << provide names and/or organizations >>
■ Beneficiaries, who benefit directly from the project’s results. This typically includes customers and users. << provide names and/or organizations >>
■ Affected parties, who neither sponsor nor benefit directly from the project but who will be impacted by its outcome. Typically this includes individuals or organizations who will need to make some change to their processes or tasks as a result of the project, but who may not see an immediate benefit. (An example would be upgrades to computer workstations throughout an entire organization.) << provide names and/or organizations >>
5. Resource Requirements
Specify the staff, equipment, and external support (as applicable) that will be needed to perform the analysis leading to the BRD. Keep in mind that this is purely the analysis team, not the overall project team.
6. Assumptions
Enumerate anything that might constitute a risk and therefore warrant close oversight and continual updates during the analysis phase, for example, project priority, executive support, sufficient funding, available staffing, and time.
7. Dependencies
Describe the relationship that this project has to other projects or an overall program, and how these dependencies may affect the timely, accurate completion of the BRD.
8. Constraints
List any known limitations on conducting a proper business analysis for the project, for example, schedule, budget, labor resources, partner availability, etc.
9. Attachments
List and attach appropriate supporting and background documents, for example:
■ The project charter
■ The RWP analysis team roster
■ The RWP budget
■ A work breakdown structure (WBS) showing RWP activities
■ Any other items that clarify the efforts to be undertaken to produce the BRD
10. Approvals
