Software Project Management

Knowledge Area: Project Scope Management

1
Dr.Ayesha
Dr. Ayesha Naseer
Naseer
 RECAP
1. What is Software Project Management
2. What are the Project Management Process Groups and Knowledge Areas
3. Which Project Management Approach for a Specific Software Development Methodology
4. Software Project Management Life Cycle Models (Linear PMLC Model, Incremental PMLC Model,
Iterative PMLC Model, Adaptive PMLC Model)
5. Traditional Project Management: How to Scope, Plan, Launch, Monitor & Control and Close a
TPM Project
6. Agile Project Management: How to Scope, Plan, Launch, Monitor & Control and Close a APM
Project
7. Project Integration, Scope, Time, Cost, Quality, HR, Communications, Risk, Procurement, and
Stakeholder Management

Software Project Management 2

Software Project Management
Project Management Knowledge Areas
• The ten Knowledge Areas are part of the PMBOK Guide, and all are present in every project
management life cycle:

1. Project Integration Management

2. Project Scope Management
3. Project Time Management
4. Project Cost Management
5. Project Quality Management
6. Project Human Resource Management
7. Project Communication Management
8. Project Risk Management
9. Project Procurement Management
10. Project Stakeholder Management

3
Software Project Management
Mapping of Ten Knowledge Areas with Five Process Groups (according
to the Project Management Institute (PMI) framework)

4
Software Project Management
5
Putting It All Together: The project Management Framework

6
Software Project Management
 This Lesson Learning Objectives
▪ After reading this lesson students will be able to:
▪ Define project scope management and explain its significance in software project success.
▪ Identify the main phases of scope management and their interconnections.
▪ Describe techniques for effectively collecting project requirements, such as interviews, surveys, and
focus groups.
▪ Create a detailed project scope statement that clearly defines inclusions, exclusions,
deliverables, and boundaries for a software project.
▪ Develop a Work Breakdown Structure (WBS) for a software project, breaking down
deliverables into manageable tasks and work packages.
▪ Describe the process of scope verification, including testing, reviews, and formal approvals.
▪ Evaluate how scope verification ensures that project deliverables meet stakeholder
expectations before project closure.
▪ Explain the importance of controlling scope changes to maintain project quality, timeline, and
budget.
▪ Use change control processes to assess the impact of scope changes, apply appropriate
approvals, and prevent scope creep.
Software Project Management 7
Software Project Management
 Phases of Project Scope Management
• Collect Requirements
• Define Scope
• Create work breakdown structure
• Verify Scope
• Control Scope

8
Software Project Management
 Collect Requirements
Purpose
• Get full understanding of what the business wants Gathering detailed requirements is crucial to ensure the final
product aligns with stakeholders' expectations.
Key Techniques:
• Interviews
• Focus Groups
• Workshops
• Group Techniques
• Questionnaire/Surveys
• Prototypes
Key Outputs
• Functional requirements
• Non-functional requirements

9
Software Project Management
 Define Scope
Purpose: The defined scope provides a clear boundary for what is included in the project and what is not.

Process: Translate the requirements into a detailed project scope statement, which includes objectives, deliverables, and major
project work.

Scope Statement: A clear document stating the work involved, approved by stakeholders to avoid misunderstandings.

10
Software Project Management
 Work Breakdown Structure
Purpose: The WBS is a hierarchical decomposition of the project’s scope into smaller, manageable sections called work packages.

Process: Break down project deliverables into tasks and sub-tasks, which simplifies scheduling, budgeting, and resource
allocation.

Benefits: A well-defined WBS minimizes scope creep by clearly outlining all tasks and deliverables, making it easier to manage
expectations.

11
Software Project Management
 Verify Scope
Purpose: The verification process ensures deliverables meet the defined requirements and gain formal stakeholder approval.

Key Activities: Testing, reviews, and inspections.

Documentation: This stage includes documentation to capture feedback, approval records, and validation results.

12
Software Project Management
 Control Scope
Purpose: Control scope involves monitoring and managing changes to the project scope, ensuring that any changes are properly
evaluated and approved.

Process: Use a formal change control process, which includes evaluating the impact of scope changes on time, cost, and quality
before approval.

13
Software Project Management
 Best Practices in Project Scope Management
• Each phase of Project Scope Management – from requirements collection to
scope control – contributes to defining and maintaining clear project
boundaries.
• Best Practices:
• Engage Stakeholders Early: Ensure stakeholders are involved in requirements
collection and scope definition to prevent misunderstandings later.
• Frequent Reviews and Sign-Offs: Verify scope periodically with stakeholders to
ensure alignment and approval.
• Document Everything: Document requirements, scope changes, and approvals to
track project alignment.

14
Software Project Management
Project Scope Management
Real world Example
Mobile Baking Application

15
Dr.Ayesha
Dr. Ayesha Naseer
Naseer
 Collect Requirements
• In Mobile Banking App:
• Stakeholder Interviews: The team conducts interviews with bank executives to
identify business goals, such as offering seamless transactions, secure account
access, and real-time alerts.
• End-User Surveys: To understand customer expectations, surveys reveal desired
features like mobile deposits, funds transfers, and an easy-to-use interface.
• Key Outputs:
• Functional Requirements: Account access, funds transfer, transaction history, bill payment,
and customer support.
• Non-Functional Requirements: Security, scalability, and response time.
• Result: A detailed requirements document to guide the project's next steps,
ensuring stakeholder expectations are clearly captured.

16
Software Project Management
 Define Scope
• In Mobile Banking App:
• Project Scope Statement:
• Inclusions: Core banking features like account login, balance check, fund transfer,
and transaction history. Additionally, basic customer support and security protocols
are included.
• Exclusions: Advanced features like investment tracking, credit score monitoring, and
voice-activated transactions, which will be reserved for a later version.
• Finalized Scope Document: The project scope document details these
boundaries, ensuring all stakeholders understand the project’s focus, with
unnecessary features filtered out to prevent scope creep.

17
Software Project Management
 Work Breakdown Structure
In Mobile Banking App:

Top Level (Level 1): Mobile Banking Application Development.

Modules (Level 2): Account Management, Transaction Processing, Security, and User Interface (UI).

Tasks (Level 3):

For Account Management, tasks include designing the account login system,
setting up account details retrieval, and testing.
For Security, tasks include encryption setup, vulnerability testing, and securing third-party integrations.

Work Packages: Each task or subtask, such as "Account Details Retrieval" under Account Management,
is assigned to team members with deadlines and budget allocations.

Result: The WBS offers a visual map and structured approach, making it easier to manage development,
testing, and deployment.

18
Software Project Management
 Verify Scope
In Mobile Banking App:

User Acceptance Testing (UAT): Key stakeholders, including bank representatives and a test group of
customers, use the app to confirm its functionality and ease of use.

•Users confirm that they can successfully log in, view balances, transfer funds, and receive alerts,
as specified in the requirements.

Formal Sign-Off: After UAT, stakeholders sign off to acknowledge that the app meets the defined scope.

Result: With successful UAT and stakeholder approval, the project team can move forward,
ensuring that any remaining work aligns with the accepted project scope.

19
Software Project Management
 Control Scope
In Mobile Banking App:

Change Request: Midway through the project, the bank requests an additional feature to
support integration with digital wallets.

Impact Analysis: The project manager evaluates the added time, costs, and
resources needed to incorporate this feature.

Decision: If approved, the project scope document and WBS are updated, and
additional resources may be allocated to avoid delays.

Control Scope Creep: By formally documenting and approving changes,

the project stays aligned with its initial goals, ensuring new features don’t disrupt the timeline or budget.

Result: By controlling scope changes, the project team protects the timeline and budget,
ensuring that the final product remains close to the originally defined vision.

20
Software Project Management
Class Activity
Case Study: Customer Relationship Management (CRM)
Background: Consider a scenario where a software development team is tasked with
building a new customer relationship management (CRM) system for a rapidly growing
business. The project stakeholders emphasize the importance of delivering the CRM system
within a specific timeline while ensuring that it meets the evolving needs of the sales and
customer service teams.
Design the following Project Scope Management activities for CRM project.
1. Collect Requirement
2. Define Scope
3. Create WBS
4. Verify Scope
5. Control Scope

21
Software Project Management
Resources
• Chapter 5: Information Technology Project Management, Kathy
Schwalbe

22
Software Project Management