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
IntegrationProject Plan DevelopmentProject PlanVery High
ScopeInitiationProduct DescriptionModerate
ScopeInitiationProject CharterModerate
ScopeScope PlanningScope StatementModerate
ScopeScope PlanningScope Management PlanModerate
ScopeScope DefinitionWork Breakdown StructureModerate
ScopeScope DefinitionWBS DictionaryModerate
ScopeScope VerificationFormal AcceptanceLow
TimeActivity DefinitionActivity ListsLow
TimeActivity SequencingProject Network DiagramLow
TimeActivity Duration EstimatingActivity Duration EstimatesModerate
TimeSchedule DevelopmentProject ScheduleModerate
TimeSchedule DevelopmentSchedule Management PlanLow
CostResource PlanningResource RequirementsModerate
CostCost EstimatingCost EstimatesModerate
CostCost EstimatingCost Management PlanLow
CostCost BudgetingCost BaselineHigh
CostCost ControlEstimate at CompletionModerate
QualityQuality PlanningChecklistsHigh
QualityQuality PlanningQuality Management PlanLow
QualityQuality PlanningOperational DefinitionsModerate
Human ResourcesOrganizational PlanningRoles & Responsibility AssignmentsModerate
Human ResourcesOrganizational PlanningStaffing Management PlanLow
Human ResourcesOrganizational PlanningOrganization ChartLow
Human ResourcesStaff AcquisitionProject Team DirectoryLow
CommunicationsCommunications PlanningCommunications Management PlanLow
CommunicationsInformation DistributionProject ReportsLow
CommunicationsInformation DistributionProject Presentations Low
CommunicationsPerformance ReportingPerformance ReportsModerate
CommunicationsPerformance ReportingChange RequestsLow
CommunicationsAdministrative ClosureProject ArchivesLow
CommunicationsAdministrative ClosureLessons LearnedLow
CommunicationsAdministrative ClosureProject ClosureLow
RiskRisk Management PlanningRisk Management PlanModerate
RiskRisk IdentificationIdentified Risks & TriggersModerate
RiskQualitative Risk AnalysisList of Prioritized Risks & Lists Risks for Additional Analysis & Risk Ranking for the ProjectModerate
RiskQuantitative Risk AnalysisPrioritized List of Quantified Risks & Probabilistic Analysis of Project & Probability of AchievingModerate
RiskRisk Response PlanningRisk Response PlanModerate
RiskRisk Monitoring & ControlWorkaround PlansLow
RiskRisk Monitoring & ControlCorrective ActionsLow
ProcurementProcurement PlanningProcurement Management PlanLow
ProcurementProcurement PlanningStatement of WorkModerate
ProcurementSolicitation PlanningProcurement DocumentsModerate
ProcurementSolicitation PlanningEvaluation CriteriaLow
ProcurementSolicitationProposalsLow
ProcurementSource SelectionContractLow
ProcurementContract AdministrationCorrespondenceLow
ProcurementContract CloseoutFormal Acceptance and ClosureLow

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
DateAuthorDescription
3 Jul 2004Robert PerrineInitial release.
4 Jul 2004Robert PerrineProcurement 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 2004Robert PerrineUpdated to refl ect changes identified while creating the Work Breakdown Structure. Also renamed document to refl ect the WBS numbering scheme.
17 Nov 2007Robert PerrineConverted back from Adobe to html. I recommend against using Adobe products.
Authorization to Proceed
5 Jul 2004Robert Perrine - Chairman, Change Control Board
17 Nov 2007Robert Perrine, Owner of the product