Download Scope Managment-Software Project Managment-Lecture Slides and more Slides Software Project Management in PDF only on Docsity! Copyright 2009 Scope refers to all the work involved in creating the products of the project and the processes used to create them A deliverable is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes Project scope management includes the processes involved in defining and controlling what is or is not included in a project docsity.com Copyright 2009 Collecting requirements: defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them Defining scope: reviewing the project charter, requirements documents, and organizational process assets to create a scope statement Creating the WBS: subdividing the major project deliverables into smaller, more manageable components Verifying scope: formalizing acceptance of the project deliverables Controlling scope: controlling changes to project scope throughout the life of the project docsity.com Sample traceability matrix
, [REQ1/REQ1REQ1REQ1REQ1REQ1REQ1REQ1REQ1REQ1REQ1/REQ1REQ1REQ1
Re
Rea mae uc | uc | uc | uc } uc | uc | uc |} uc | uc | uc |TECH|TECHITECH
Identifiers [Te
AA: | 422e | AES: 264) | 22s | 23.1123) 23324 | Si. | si2t | Ay | A: | 1.3)
docsity.com
A requirement is “a condition or capability that must be met or possessed by a system, product, service, result, or component to satisfy a contract, standard, specification, or other formal document” (PMBOK® Guide, 2008) For some IT projects, it is helpful to divide requirements development into categories called elicitation, analysis, specification, and validation It is important to use an iterative approach to defining requirements since they are often unclear early in a project docsity.com
Figure 5-2. Relative Cost to Correct
a Software Requirement Defect
‘1 | | | | |
Operation
a
3 Test
ot
a
€
ou
e Code
Q
2
a .
2 Design
a
Requirements
T T T T qT T
0 20 40 60 80 100 120
Relative Cost to Correct a Defect
Source: Robert B. Grady, “An Economic Release Decision Model: Insights into Software Project Management.”
Proceedings of the Applications of Software Measurement Conference (Orange Park, FL: Software Quality
Engineering, 1999), pp.227-239.
docsity.com
Table 5-1. Sample Requirements
Traceability Matrix
Requirement Name Category Source PSY e101)
No.
R32 Laptop Hardware Project charter Complete. Laptops
memory and corporate ordered meet require-
laptop ment by having 4GB
specifications of memory.
docsity.com
Key inputs for preparing the project scope statement include the project charter, requirements documentation, and organizational process assets such as policies and procedures related to scope statements as well as project files and lessons learned from previous, similar projects As time progresses, the scope of a project should become more clear and specific docsity.com Table 5-3. Further Defining Project Scope
Project Charter:
Upgrades may affect servers. .. (listed under Project Objectives)
Project Scope Statement, Version 1:
Servers: If additional servers are required to support this project, they must be compatible
with existing servers. If it is more economical to enhance existing servers, a detailed
description of enhancements must be submitted to the CIO for approval. See current server
specifications provided in Attachment 6. The CEO must approve a detailed plan describing
the servers and their location at least two weeks before installation.
Project Scope Statement. Version 2:
Servers: This project will require purchasing ten new servers to support Web, network,
database, application, and printing functions. Virtualization will be used to maximize
efficiency. Detailed descriptions of the servers are provided in a product brochure in
Appendix 8 along with a plan describing where they will be located.
docsity.com
