Scribd
Upload
8 views

Lecture 7 - Process Maturity Plan - PM

The document discusses establishing commitment processes and project planning for organizational improvement. It covers defining work, estimating time and resources, and creating project plans with goals, schedules, and estimates to track progress.

Uploaded by

sadia amjad
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

Lecture 7 - Process Maturity Plan - PM

The document discusses establishing commitment processes and project planning for organizational improvement. It covers defining work, estimating time and resources, and creating project plans with goals, schedules, and estimates to track progress.

Uploaded by

sadia amjad
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 31

Process Maturity Plan

Focus on highest priority areas for organizational improvement: commitments,


planning, CM, QA
Project Management.
Commitment
Commitment
• Commitment
– Agreement on planned completion date and payment
• Elements of an effective commitment
– Is willingly made
– Considers schedule, amount of work, resources
– Has agreement on:
• What is to be done?
• By whom?
• By when?
– Is explicitly stated
– Is met
– Notify in advance + renegotiate
Project Management Principles
• A plan based on hierarchy of commitments
• A management system to resolve conflicts
(business objective and projects)
• An oversight and review (track progress
against plan)
Commitment Hierarchy
• Organizational/Management Commitment
– Support the professionals when negotiating
changes in requirements
• Probability to meet plans and estimates???
– Support to obtain needed facilities
– Assurance of timely meetings
• Software Professionals’ Commitment
Commitment Process
• Commitment for software delivery by Senior
Executive (for motivation only)
– Work has been defined and agreed upon
– Resource, cost, schedule estimates have been
prepared
– All involved parties agree to plan
– Adequate preparation has been done (risks??)
– Required resources can be acquired
• Commitment after formal reviews
• Enforcement for proper reviews
Establishing Commitment Process
• Through senior management
– Plan before a commitment is made
– Need of training and procedures
The Management System
• Measuring organizations and projects
– Organizations
• Operating plans: in annual terms
– Expenses, capital requirements, annual productivity and profitability objectives,
periodic product delivery commitments
– Projects
• Product plans: in terms of project checkpoints
– Function, cost, schedule, quality, resources, checkpoints
– Conflict?
• Project is not setup on annual basis
• Projects are difficult to be measured on annual basis
• Organizations are measured on periodic (usually annual basis)
– Solution?
• Effective management system to resolve the conflict
– Reviews and contention system
The Management System
• Contention Process
– Review all major decisions with involved parties
– Make a decision in presence of all dissenting
parties
– Determine a knowledgeable agreement
• Quarterly Reviews
– SEPG, SQA
– Visible work items
• Project Phase Reviews
Project Planning
Define what work needs to be done and how?
Project Plan
• Definition of major work items (or tasks)
• Estimate of time
• Estimate of required resources
– Estimate of effort
• Estimate of software size
Decomposing Requirements
1. The spellchecker shall keep track of words being
1. I need a spellchecker typed in the existing word processor
2. I want this spellchecker 2. The spellchecker shall check against each typed
to work with my open word if it is a valid word in the corresponding
source word processing dictionary
software 3. The spellchecker shall highlight the wrong words
(i.e. which are not part of dictionary) while the user
types in the existing word processor.
4. The spellchecker shall give the user an option to
make correction in case there is a wrong word typed
5. The spellchecker shall suggest correct words when
user opts to make a correction against a wrong word
6. The spellchecker shall integrate with an existing
word processor that runs on Linux.
7. The spellchecker shall use Red color to highlight
the wrong words
Project Plan Contents
• Goals and Objectives
– What, for whom, by when, success criteria
• Project scoping and negotiation of requirements
– Functional requirements
– System needs for example compatibility or environmental
constraints
– Customer/User identification, user involvement
– Measures of success s.a. cost, schedule, performance, size
• WBS
• Schedule
• Size and Resource Estimates
Gantt Chart
• Macroscopic Project Schedule
Project Table
Gantt Chart (Contd.)

Source: https://www.workamajig.com/blog/gantt-charts-project-management
Tracking
• Checkpoints/Milestones
• Gantt Chart
• Checkpoint Plan
Accuracy of Schedule Estimates
•
Software Project Cost and Effort
Estimation
• S/W cost and effort estimation will never be
an exact science
– Too many variables
• Human
• Technical
• Environmental
• Political

21
Software Project Estimation
• Options for estimation
– Delay estimation until late in the project
• Attractive, but not practical
– Base estimates on similar projects that have already been
completed
• Unfortunately, past experience has not always been a good indicator
of future results
– Use relatively simple decomposition techniques to generate
project cost and effort estimates
• “Divide and conquer” approach
– Use one or more empirical models for software cost and
effort estimation
• Can be used as a cross-check for the previous option and vice versa
22
LOC Per Function Point
Language Average Median Low High
Ada 154 -- 104 205
Assembler 337 315 91 694
C 162 109 33 704
C++ 66 53 29 178
COBOL 77 77 14 400
Java 55 53 9 214
PL/1 78 67 22 263
Visual Basic 47 42 16 158

www.qsm.com/?q=resources/function-point-languages-table/index.html

23
An Example of LOC-Based Estimation

Function Estimated LOC


User interface and control facilities (UICF) 2,300
Two-dimensional geometric analysis (2DGA) 5,300
Three-dimensional geometric analysis (3DGA) 6,800
Database management (DBM) 3,350
Computer graphics display facilities (CGDF) 4,950
Peripheral control function (PCF) 2,100
Design analysis modules (DAM) 8,400

Estimated lines of code 33,200

24
An Example of LOC-Based Estimation
• Estimated lines of code = W = 33,200
• Let,
– Average productivity = 620 LOC/pm = X
– Labor rate = $8,000 per month = Y
• So,
– Cost per line of code = Z = Y/X = $13 (approx.)
– Total estimated project cost = W*Z = $431,000 (approx.)
– Estimated effort = W/X = 54 person-months (approx)

25
Accuracy of Effort Estimates
•
Delphi’s Technique (Estimating
Inaccuracies)
• Composite
Estimation
Estimating Contingencies
• Programmers’ experience
• Data from prior projects
• Level of knowledge about the new product
• EEA?
Example
References
• SE book by Pfleeger
• SE book by Pressman
• Managing the Software Process by Humphrey
• UCF Slides for Pressman’s and Pfleeger’s Books
respectively

31

You might also like