Recursion Project
2 Scope
2-3 Scope Statement
2-3-1 Purpose
The purpose for this document is to analyze the product that is the justification for this project. This document
is a transition between the Product Description and the Work Breakdown Structure. The Product Description
will evolve, through progressive elaboration toward a detailed description useful to the end user of the product.
The Work Breakdown Structure will evolve into the tasks on the project schedule.
The purpose for this project is to demonstrate the use of the PMI methodology through a comprehensive set
of project documents.
2-3-2 Copyright
Summer 2004, Irvine, California, USA, copyright by Robert E. Perrine, PMP. Offered as is, with no warranty regarding the accuracy
or suitability of this material. Copyright reserved. You are, however free to copy and distribute these documents with the following
restrictions.
- You may not charge for use or distribution of this material.
- Your usage of this material is conditioned upon your compliance with the PMI Code of Ethics.
- All distributions must be made with the intent to further the collected wisdom of humanity.
- You may not remove my name or my copyright notices from these documents.
2-3-3 Table of Contents
Recursion Project
2 Scope
2-3 Scope Statement
2-3-1 Purpose
2-3-2 Copyright
2-3-3 Table of Contents
2-3-4 Product Description
2-3-5 Major Components
2-3-6 Deliverables
2-3-7 Exclusions
2-3-8 Revision History and Authorization to Proceed
2-3-4 Product Description
The product to be built during the course of this project is a set of documents. It is expected that there will be
about thirty total documents, but that number will be refined during the course of this project. These documents
must be made available through an internet portal. A more comprehensive description of the product is
included in document “Recursion 002 Product Description”.
2-3-5 Major Components
The major components of this product are the organized around the nine PMBOK 2000 knowledge areas.
- Communication
- Scope
- Time
- Human Resources
- Cost
- Quality
- Procurement
- Risk
- Integration
An additional major component is the metadata for this project. Documents like the “Recursion 001 Guidelines”
are not found within the PMBOK list of outputs. Instead, that type of document is assumed to pre-exist
as an Organizational Policy or a Planning Methodology.
2-3-6 Deliverables
Note that the following list contains more than the estimated thirty documents. It is anticipated that several of
these documents will be merged into one. For now, the planning estimate will remain at 30.
Methodology
| Knowledge Area
| Process
| Document
| Complexity
| | None
| Methodology
| Guidelines
| Very High
|
Knowledge Areas
| Knowledge Area
| Process
| Document
| Complexity
| | Integration | Project Plan Development | Project Plan | Very High
| | Scope | Initiation | Product Description | Moderate
| | Scope | Initiation | Project Charter | Moderate
| | Scope | Scope Planning | Scope Statement | Moderate
| | Scope | Scope Planning | Scope Management Plan | Moderate
| | Scope | Scope Definition | Work Breakdown Structure | Moderate
| | Scope | Scope Definition | WBS Dictionary | Moderate
| | Scope | Scope Verification | Formal Acceptance | Low
| | Time | Activity Definition | Activity Lists | Low
| | Time | Activity Sequencing | Project Network Diagram | Low
| | Time | Activity Duration Estimating | Activity Duration Estimates | Moderate
| | Time | Schedule Development | Project Schedule | Moderate
| | Time | Schedule Development | Schedule Management Plan | Low
| | Cost | Resource Planning | Resource Requirements | Moderate
| | Cost | Cost Estimating | Cost Estimates | Moderate
| | Cost | Cost Estimating | Cost Management Plan | Low
| | Cost | Cost Budgeting | Cost Baseline | High
| | Cost | Cost Control | Estimate at Completion | Moderate
| | Quality | Quality Planning | Checklists | High
| | Quality | Quality Planning | Quality Management Plan | Low
| | Quality | Quality Planning | Operational Definitions | Moderate
| | Human Resources | Organizational Planning | Roles & Responsibility Assignments | Moderate
| | Human Resources | Organizational Planning | Staffing Management Plan | Low
| | Human Resources | Organizational Planning | Organization Chart | Low
| | Human Resources | Staff Acquisition | Project Team Directory | Low
| | Communications | Communications Planning | Communications Management Plan | Low
| | Communications | Information Distribution | Project Reports | Low
| | Communications | Information Distribution | Project Presentations | Low
| | Communications | Performance Reporting | Performance Reports | Moderate
| | Communications | Performance Reporting | Change Requests | Low
| | Communications | Administrative Closure | Project Archives | Low
| | Communications | Administrative Closure | Lessons Learned | Low
| | Communications | Administrative Closure | Project Closure | Low
| | Risk | Risk Management Planning | Risk Management Plan | Moderate
| | Risk | Risk Identification | Identified Risks & Triggers | Moderate
| | Risk | Qualitative Risk Analysis | List of Prioritized Risks & Lists Risks for Additional Analysis & Risk Ranking for the Project | Moderate
| | Risk | Quantitative Risk Analysis | Prioritized List of Quantified Risks & Probabilistic Analysis of Project & Probability of Achieving | Moderate
| | Risk | Risk Response Planning | Risk Response Plan | Moderate
| | Risk | Risk Monitoring & Control | Workaround Plans | Low
| | Risk | Risk Monitoring & Control | Corrective Actions | Low
| | Procurement | Procurement Planning | Procurement Management Plan | Low
| | Procurement | Procurement Planning | Statement of Work | Moderate
| | Procurement | Solicitation Planning | Procurement Documents | Moderate
| | Procurement | Solicitation Planning | Evaluation Criteria | Low
| | Procurement | Solicitation | Proposals | Low
| | Procurement | Source Selection | Contract | Low
| | Procurement | Contract Administration | Correspondence | Low
| | Procurement | Contract Closeout | Formal Acceptance and Closure | Low
|
2-3-7 Exclusions
Only the documents itemized above will be included in this project. All other documents are hereby formally
excluded, unless authorized by an approved Change Request.
Note, however, that the process of Progressive Elaboration means that additional deliverables are likely to be
discovered during the other planning processes. While the Scope Statement is “definitive” initially, it will be
made obsolete once the Work Breakdown Structure is defined.
Based upon the Project Manager’s evaluation, items added to the Work Breakdown Structure might or might
not warrant re-editing the Scope Statement.
2-3-8 Revision History and Authorization to Proceed
| Date | Author | Description
| | 3 Jul 2004 | Robert Perrine | Initial release.
| | 4 Jul 2004 | Robert Perrine | Procurement was moved from an Exclusion to an Inclusion. Also, the prior version of this document was focused on Initiation and Planning. This update corrects that by adding documents from Execution, Controlling and Closing.
| | 5 Jul 2004 | Robert Perrine | Updated to refl ect changes identified while creating the Work Breakdown Structure. Also renamed document to refl ect the WBS numbering scheme.
| | 17 Nov 2007 | Robert Perrine | Converted back from Adobe to html. I recommend against using Adobe products.
| | Authorization to Proceed
| | 5 Jul 2004 | Robert Perrine - Chairman, Change Control Board
| | 17 Nov 2007 | Robert Perrine, Owner of the product
|
|