SE-868: Software Project Management

Course Introduction
 SE 868: Software Project Management
 Credits: 3
 Instructor: Assistant Professor Dr. Mehwish Naseer
 Enrollment Code for LMS :179530862
Course Assessment
Exam: 1 Mid Term and 1 Final
Home work: 3 Assignments
Term Paper 1 Term Paper as Semester Project
Quizzes: 6 Quizzes
Grading: Quizzes: 10%
Term Paper + 10%
Assignments:
1 Mid Term: 30%
Final Exam: 50%
Course books
 Text Books:
 Software Project Management, Bob Hughes and
Mike Cotterell, McGraw-Hill Education; (Latest Edition).
 A Guide to the Project Management Body of Knowledge,
(PMBOK Guides), (Latest Edition).
 Reference Books:
 Mastering Software Project Management: Best Practices,
Tools and Techniques, Murali K. Chemuturi and Thomas
M. Cagley Jr., J. Ross Publishing, (Latest Edition).
 Effective Project Management: Traditional, Agile,
Extreme, Robert K. Wysocki, Wiley; (Latest Edition).
Term Paper
 Find a topic related to software project
management.
 Every one must write his/her own paper.
 Plagiarizing (copying) others cannot get score.
 Presentation and submission of Term Paper at
the end of semester
Course Outline
Intro to Software Project Management
PMI Framework/ Knowledge Areas
Project Management Tools
Organizational Structure
Project Planning
Project Evaluation
Project Selection
Software Effort Estimation
Course Outline
Activity Planning
Software Risk Management
Resource Allocation
Monitoring and Control
Managing Contracts
Managing people in software environments
Working in Teams
Software Quality
Software Project Management
Objectives:
 Define the scopes of SPM

 Understand what project managers worry about

 Define the phases of a software project

 Explain the factors of management

 Be conscious of that a project needs elaborative

planning, supervision and control

 Identify stakeholders and their objectives

 Define the criteria of success

Introduction to Project Management
What is a Project?
 A project is a temporary endeavor undertaken to
produce a unique product or service

Temporary Characteristics of Unique

Projects

 Temporary – Definitive beginning and end

 Unique – New undertaking, unfamiliar ground
 CHARACTERISTICS OF A PROJECT
 Projects are Temporary;
 Temporary does not necessarily mean short in duration:
 Many projects last for several years.
 Temporary means that every project has a definite
beginning and a definite end.
 The end is reached:
 When the project’s objectives have been achieved, or
 When it becomes clear that the project objectives
cannot be met and the project is terminated.
 Projects are Unique;
 Unique, product, service, result

11
 CHARACTERISTICS OF A PROJECT
A Project;
Has specific objectives
Has a start and end date
Has a budget
Has an ‘owner’/’sponsor’
Produces specific deliverables
Can vary vastly in size, complexity and
duration
May be a phase within a larger project or a
phase within a program
12
Project Success

Customer Requirements Completed within allocated

satisfied/exceeded time frame

Completed within allocated Accepted by the customer

budget
Project Failure

Poor Requirements
Scope Creep
Gathering

Unrealistic planning and Lack of resources

scheduling
Project Vs Process
 A process is a repetitive activity like a plant turning
over and producing the same product.
What is Project Management
Project Management is the application of skills,
knowledge, tools and techniques to meet the
needs and expectations of stakeholders for a
project.
Refers to guiding the project work to deliver the
intended outcomes.
Project teams can achieve the outcomes using a
broad range of approaches (e.g., predictive,
hybrid, and adaptive).
What is Software Project Management?
 Software project management is dedicated to the
planning, scheduling, resource allocation, execution,
tracking, and delivery of software and web projects.
 Project management in software engineering is distinct
from traditional project management — software in
project management has a unique life cycle process that
requires multiple rounds of testing, updating, and
customer feedback.
 Most IT-related projects are managed in the Agile style to
keep up with the increasing pace of business and iterate
based on customer and stakeholder feedback.
Triple Contraint
Time

Quality
Cost Scope
Triple Contraint
Increased Scope = increased time + increased cost

Tight Time = increased costs + reduced scope

Tight Budget = increased time + reduced scope.

Project Life Cycle
Initiation Phase
 3 main things
 Objectives
 Scope Constraints
 Project charter
 Initial vision of the project
 Deliverables
 Constraints
 Risks
Initiation Phase
• What are the goals of this project?
• Why now?
• What business benefits will this give us?
• Defining major stakeholders earlier
Initiation Phase
• Communicating with stakeholders to understand the
purpose and desired outcomes of the project
• Clarifying resources like budget and time constraints
• Confirming team size and roles required
• Determining how often and which stakeholders will be
involved throughout the project
Initiation Phase
• Tools and documents:
• Project proposal: The project proposal defines a
project and outlines key dates, requirements, and
goals.
• Project charter: This is a definitive document
that describes the project and main details
necessary to reach its goals. This can include
potential risks, benefits, constraints, and key
stakeholders.
• RACI chart: A RACI chart plots the roles and
responsibilities of members on a project team.
Planning Phase
Key to successful project management
Focuses on developing a roadmap for the team to
follow.
Planning Phase
 Determine the steps to actually achieve the project goals—the
“how” of completing a project.
 Roles and responsibilities are clearly defined,
• Deciding on milestones that lead up to goal completion
• Developing a schedule for tasks and milestones, including time
estimates and potential time buffers
• Determining how and how often to communicate with team
members and stakeholders
• Creating and signing documents such as non-disclosure
agreements (NDAs)
• Assessing and managing risk by creating a risk register
• Holding a kick-off meeting to start project
Planning Phase
• Tools and documents:
• Scope Statement – A document that clearly defines the project,
including the business need, benefits of the project, objectives,
deliverables, and key milestones. A scope statement may change
during the project, but it shouldn’t be done without the
approval of the project manager and the sponsor.
• Work Breakdown Schedule (WBS) –This is a visual
representation that breaks down the scope of the project into
manageable sections for the team.
• Milestones – Identify high-level goals that need to be met
throughout the project and include them in the Gantt chart.
Planning Phase
• Tools and documents:
• Gantt chart: A horizontal bar chart in which
members can see what tasks must be completed in
what order, and how long each is expected to take
• Risk register: A chart that lists risks associated
with the project, along with their probability,
potential impact, risk level, and mitigation plans
Execution Phase
• Assign resources
• Execute project management plans
• Procurement management if needed
• Task assignments are executed
• Status meetings
• Update project schedule
• Modify project plans as needed
Execution Phase
• Using tools like GANTT or burndown charts to track
progress on tasks
• Responding to risks when they manifest
• Recording costs
• Keeping team members motivated and on task
• Keeping stakeholders informed of progress
• Incorporating changes via change requests
Execution Phase
• Tools and documents:
• Change requests: These are documents used
to propose changes to a project’s scope or goals
• Burndown chart: This chart breaks down
tasks on a granular level and visualizes the
amount of time remaining
•
Execution Phase
• Ensures that project results align with the
management plan.
• Project managers use key performance indicators
(KPIs) to determine if the project is on track
• Project Objectives
• Quality Deliverables
• Effort and Cost Tracking
Closing Phase
 Contractual Closeout
 Post Production Transition
 Lessons Learned