SWE-466 Software Project Management: Chapter 5 - Project Scope Management, Lecture notes of Management Fundamentals

saaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Typology: Lecture notes

2018/2019

Uploaded on 04/01/2019

s-z
s-z 🇸🇦

5

(1)

3 documents

1 / 44

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
SWE-466 Software Project Management
Software Project Management
1
Chapter-5
Project Scope Management
Course Learning Objectives:
¨Understand project scope management and the
process for creating WBS
¨Manage effectively and efficiently software
projects by scope.
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c

Partial preview of the text

Download SWE-466 Software Project Management: Chapter 5 - Project Scope Management and more Lecture notes Management Fundamentals in PDF only on Docsity!

SWE-466 Software Project Management

Software Project Management

1

Chapter-

Project Scope Management

Course Learning Objectives:

¨ Understand project scope management and the

process for creating WBS

¨ Manage effectively and efficiently software

projects by scope.

SWE-466 Software Project Management ¨ Understand the importance of good project scope management ¨ Describe the process of planning scope management ¨ Discuss methods for collecting and documenting requirements to meet stakeholder needs and expectations ¨ Explain the scope definition process and describe the contents of a project scope statement ¨ Discuss the process for creating a work breakdown structure using the analogy, top-down, bottom-up, and mind-mapping approaches Learning Objectives

SWE-466 Software Project Management ¨ 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 What is Project Scope Management?

SWE-466 Software Project Management

1. Planning scope: determining how the project’s scope and requirements will be managed 2. 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 3. Defining scope: reviewing the project charter, requirements documents, and organizational process assets to create a scope statement 4. Creating the WBS: subdividing the major project deliverables into smaller, more manageable components 5. Validating scope : formalizing acceptance of the project deliverables 6. Controlling scope: controlling changes to project scope throughout the life of the project Project Scope Management Processes

SWE-466 Software Project Management ¨ The project team uses expert judgment and meetings to develop two important outputs: A. the scope management plan and B. the requirements management plan ¨ The scope management plan is a supplementary part of the project management plan

1.Planning Scope Management

SWE-466 Software Project Management ¨ How to prepare a detailed project scope statement ¨ How to create a WBS ¨ How to maintain and approve the WBS ¨ How to obtain formal acceptance of the completed project deliverables ¨ How to control requests for changes to the project scope A- Scope Management Plan Contents

SWE-466 Software Project Management ¨ 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 Elicitation: It is the practice of collecting the requirements of a system from users, customers and other stakeholders.

2.Collecting Requirements

SWE-466 Software Project Management Relative Cost to Correct a Software Requirement Defect

SWE-466 Software Project Management ¨ A requirements traceability matrix (RTM) is a table that lists requirements, various attributes of each requirement, and the status of the requirements to ensure that all requirements are addressed ¨ Sample entry in an RTM Requirements Traceability Matrix

SWE-466 Software Project Management ¨ Project scope statements should include ¤ at least a product scope description, product user acceptance criteria, and detailed information on all project deliverables. ¤ It is also helpful to document other scope-related information, such as the project boundaries, constraints, and assumptions. ¤ The project scope statement should also reference supporting documents, such as product specifications

3.Defining Scope

SWE-466 Software Project Management

Sample Project Charter (partial)

SWE-466 Software Project Management Further Defining Project Scope

SWE-466 Software Project Management

What is WBS?

¨ The WBS represents a logical decomposition of the work to be performed and focuses on how the product, service, or result is naturally subdivided. ¨ It is an outline of what work is to be performed. ¨ W B S i s a h i e ra r c h i c a l a n d i n c r e m e n t a l decomposition of the project into phases, deliverables and work packages ¨ A deliverable-oriented grouping of the work involved in a project that defines its total scope.

Level and Elements of WBS

SWE-466 Software Project Management 20