Click to edit
Master title style
Software Engineering
Mrs. R.K.Santhia /Assistant Professor-CSE
The main goal of software project
management is to enable a group of
developers to work effectively towards
the successful completion of a project.
Software project Management
Software Project Management
Complexities
The main factors contributing to the complexity of managing a
software project, as identified by are the following:
• Invisibility
• Changeability
• Complexity
• Uniqueness
• Exactness of the solution
• Team-oriented and intellect-intensive work
Responsibilities of a Software Project Manager
Project manager‘s responsibilities into the following two major
categories:
• Project planning: Project planning involves estimating
several characteristics of a project and then planning the
project activities based on these estimates made.
• Project monitoring and control: The focus of project
monitoring and control activities is to ensure that the
software development proceeds as per plan.
Skills Necessary for Managing Software
Projects
Three skills that are most critical to successful project
management are the following:
• Knowledge of project management techniques.
• Decision taking capabilities.
• Previous experience in managing similar projects.
Project Planning
During project planning, the project manager performs the
following activities.
Estimation: The following project attributes are estimated.
• Cost: How much is it going to cost to develop the software
product?
• Duration: How long is it going to take to develop the
product?
• Effort: How much effort would be necessary to develop the
product?
Project Planning
• Scheduling: After all the necessary project parameters
have been estimated, the schedules for manpower and
other resources are developed.
• Staffing: Staff organization and staffing plans are made.
• Risk management: This includes risk identification,
analysis, and abatement planning.
• Miscellaneous plans: This includes making several other
plans such as quality assurance plan, and configuration
management plan, etc.
Fundamental parameter based on
estimations and project plans
The SPMP Document of Project Planning
• Organization of the software project management plan (SPMP)
document
1.Introduction
(a) Objectives
(b) Major Functions
(c) Performance Issues
(d) Management and Technical Constraints
2. Project estimates
(a) Historical Data Used
(b) Estimation Techniques Used
(c) Effort, Resource, Cost, and Project Duration Estimates
3. Schedule
(a) Work Breakdown Structure
(b) Task Network Representation
(c) Gantt Chart Representation
(d) PERT Chart Representation
4. Project resources
(a) People
(b) Hardware and Software
(c) Special Resources
The SPMP Document of Project Planning
5. Staff organization
• (a) Team Structure
• (b) Management Reporting
6. Risk management plan
• (a) Risk Analysis
• (b) Risk Identification
• (c) Risk Estimation
• (d) Risk Abatement Procedures
The SPMP Document of Project Planning
7. Project tracking and control plan
(a) Metrics to be tracked
(b) Tracking plan
(c) Control plan
8. Miscellaneous plans
(a) Process Tailoring
(b) Quality Assurance Plan
(c) Configuration Management Plan
(d) Validation and Verification
(e) System Testing Plan
(f ) Delivery, Installation, and Maintenance Plan
The SPMP Document of Project Planning

Responsibilities of a Software Project Manager

  • 1.
    Click to edit Mastertitle style Software Engineering Mrs. R.K.Santhia /Assistant Professor-CSE
  • 2.
    The main goalof software project management is to enable a group of developers to work effectively towards the successful completion of a project. Software project Management
  • 3.
    Software Project Management Complexities Themain factors contributing to the complexity of managing a software project, as identified by are the following: • Invisibility • Changeability • Complexity • Uniqueness • Exactness of the solution • Team-oriented and intellect-intensive work
  • 4.
    Responsibilities of aSoftware Project Manager Project manager‘s responsibilities into the following two major categories: • Project planning: Project planning involves estimating several characteristics of a project and then planning the project activities based on these estimates made. • Project monitoring and control: The focus of project monitoring and control activities is to ensure that the software development proceeds as per plan.
  • 5.
    Skills Necessary forManaging Software Projects Three skills that are most critical to successful project management are the following: • Knowledge of project management techniques. • Decision taking capabilities. • Previous experience in managing similar projects.
  • 6.
    Project Planning During projectplanning, the project manager performs the following activities. Estimation: The following project attributes are estimated. • Cost: How much is it going to cost to develop the software product? • Duration: How long is it going to take to develop the product? • Effort: How much effort would be necessary to develop the product?
  • 7.
    Project Planning • Scheduling:After all the necessary project parameters have been estimated, the schedules for manpower and other resources are developed. • Staffing: Staff organization and staffing plans are made. • Risk management: This includes risk identification, analysis, and abatement planning. • Miscellaneous plans: This includes making several other plans such as quality assurance plan, and configuration management plan, etc.
  • 8.
    Fundamental parameter basedon estimations and project plans
  • 9.
    The SPMP Documentof Project Planning • Organization of the software project management plan (SPMP) document 1.Introduction (a) Objectives (b) Major Functions (c) Performance Issues (d) Management and Technical Constraints 2. Project estimates (a) Historical Data Used (b) Estimation Techniques Used (c) Effort, Resource, Cost, and Project Duration Estimates
  • 10.
    3. Schedule (a) WorkBreakdown Structure (b) Task Network Representation (c) Gantt Chart Representation (d) PERT Chart Representation 4. Project resources (a) People (b) Hardware and Software (c) Special Resources The SPMP Document of Project Planning
  • 11.
    5. Staff organization •(a) Team Structure • (b) Management Reporting 6. Risk management plan • (a) Risk Analysis • (b) Risk Identification • (c) Risk Estimation • (d) Risk Abatement Procedures The SPMP Document of Project Planning
  • 12.
    7. Project trackingand control plan (a) Metrics to be tracked (b) Tracking plan (c) Control plan 8. Miscellaneous plans (a) Process Tailoring (b) Quality Assurance Plan (c) Configuration Management Plan (d) Validation and Verification (e) System Testing Plan (f ) Delivery, Installation, and Maintenance Plan The SPMP Document of Project Planning