11 - ma ppqa cm

11

IT M a t u r i t y

S e r v i c e s

Project Management11 – Influence of Measurement and Analysis,Configuration Management, and Process andProduct Quality Assurance on Projekt Management

Malte Foegen

- 2 - © 2007 wibas IT Maturity Services GmbHFor student use only

1 Measurement and Analysis

22


Develop and sustain a measurement capability thatis used to support management information needs.

Align Measurement and

Analysis Activities

(SG 1)

Provide

Measurement Results

(SG 2)

MeasurementObjectives

MeasurementResults

Procedures, Tools

Measurement Repository


Measurement objectives and activities are aligned with identified information needs and objectives.

Align Measurement and Analysis Activities (SG 1)

Establish

Measurement

Objectives

(SP 1.1)

Specify

Measures

(SP 1.2)

Specify Data

Collection and

Storage

Procedures

(SP 1.3)

Specify

Analysis

Procedures

(SP 1.4)


Procedures, Tools


33


Typical WP for Aligning Measurement and Analysis Activities

Align Measurement and Analysis Activities

(SG 1)


Procedures, Tools


SP 1.1 Establish

Measurement

Objectives

1. Measurement Objectives

SP 1.2 Specify

Measures

1. Specifications of base and derived measures

SP 1.3 Specify Data

Collection and

Storage Procedures

1. Data Collection and Storage Procedures

2. Data Collection tools

SP 1.4 Specify

Analysis Procedures

1. Analysis specification and procedures

2. Data analysis tools


Measurement results that address identified information needs and objectives are provided.

Provide Measurement Results(SG 2)

Measurement Results

Procedures,Tools


Collect

Measurement

Data

(SP 2.1)Analyze

Measurement

Data

(SP 2.2)

Store Data and

Results

(SP 2.3)

Communicate

Results

(SP 2.4)

44


Typical WP for Providing Measurement Results

Provide Measurement Results (SG 2)

SP 2.1 Collect

Measurement Data

1. Base and derived measurement data sets

2. Results of data integrity tests

SP 2.2 Analyze

Measurement Data

1. Analysis results and draft reports

SP 2.3 Store Data

and Results

1. Stored data inventory

interpretation of analysis

SP 2.4 Communicate

Results

1. Delivered reports and related analysis results

2. Contextual information or guidance to aid in the interpretation of analysis results

Measurement Results

Procedures,Tools



Measurement and Analysis can support your project monitoring and control activities.

Probability

Consequence

Dolla

rs

Reserve Exposure

Tim

e

Defects by ActivityReqts Design Code Test

De

fec

ts

Open Closed

Time

Effic

iency

9/5/1999

118.25

8.25 11

129

CHANGE

Time

Tasks

Com

ple

ted

Earned Value

(BCWP)$ Millions

$ Millions

Months

10/5/1999

PROGRESS

COMPLETION

PRODUCTIVITY

STAFF QUALITY

RISK

CostPerformanceIndex (CPI)

PerformanceIndex (TCPI)

To-Complete

Configuration ManagementChurn Per Month (%)

Requirements ChangePer Month (%)

Voluntary TurnoverPer Month (%)

Overtime HoursPer Month (%)

Actual Cost

(ACWP)

Elapsed Time

Reporting Period

From To

Completed On Time

Total Due

Completed Late

Total Over Due

0 5.52.75

Total Program Perfomance

Efficiency

Quality Gate Quality Gate

Task Status This Period Tasks Completed

Risk Exposure

Risk Reserve

Metrics

Problem

Anonymous Channel

Unresolved Warning

0 5.52.75

0 63

0.70.8

0.9 1.0 1.11.2

1.3 0.70.8

0.9 1.0 1.11.2

1.3

0.51.0

1.5 2.0 2.53.0

3.5 0.51.0

1.5 2.0 2.53.0

3.5 0.51.0

1.5 2.0 2.53.0

3.5 1020

30 40 5060

70

8

1

2

5

BC

BA

C

EA

C

55


… or like this

g y r

g g g

g y r

Reporting date: DD-MM-YYYY

Effort & Rework (h)

-50

0

50

100

150

200

250

300

350

J F M A M J J A S O N D

More/Less Effort WP-Effort Act.Rework Act. Planned

Milestone-Trend-Analysis

01/04

03/04

04/04

06/04

08/04

10/04

12/04

J F M A M J J A S O N DA-Sample B-Sample C-SampleD-Sample E-Sample SOP

N° and Status of Requirements

0

5

10

15

20

25

30

35

J F M A M J J A S O N DOpen InAnalysis ApprovedImplemented Tested Rejected

N° and Status of Change Requests

0

10

20

30

40

50

60

70


Backlog Submitted Under Analysis Accepted Rejected

N° of completed Work Packages

-10

0

10

20

30

40

50

60

70

80


Backlog Planned Actual D-Sample E-Sample

N° and Status of Defects

0

10

20

30

40

50

60

70


Backlog Open InWork Implemented Closed

N° and Status of Non-Compliancies

0

5

10

15

20

25


Backlog Found Open Resolved

Progress Rate (PR) of Requirements

0

10

20

30

40

50

60

70

80

90

100


%

PR Planned PR

Critical Computer Resources

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

J F M A M J J A S O N DMemory Load CPU Load Runtime90%-Limit 75%-Limit


… or like this

Hours

66


Be sure to understand your projects‘ objectives. Establish and maintain only those measures that can be maintained with real data. Less might be more.

�Decide what you need to know/ask

�Define what you need to monitor in order to have an answer to your question

�Only measurements that are maintained are useful – rather work with few measurements that work (e.g. just one) than with too many.

�Be aware of nice looking charts withz lots of data – motsly they are not maintained. Adapt the number of measurements to your project‘s and organization‘s size.


2 Configuration Management

77


Configuration Management establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits.

Establish Baselines

(SG 1)

Track and Control

Changes (SG 2)

Configuration Management System

Establish Integrity

(SG 3)

Change Request Database

Change Request

Audit Results

Action Items

Reports


Baselines of identified work products are established.

Establish Baselines

(SG 1)

Establish a

Configuration

Management

(SP 1.2)

Identify

Configuration

Items

(SP 1.1)

Create or

Release

Baselines

(SP 1.3)

Configuration-Management-System

Change Request Database

88


Typical work Products for Establishing Baselines

Establish Baselines (SG 1)

SP 1.2 Establish a

Configuration Management

1. Configuration managementsystem with controlled work products

2. Configuration management system access control procedures

3. Change reuest database

SP 1.1 Identify

Configuration Items

1. Identified configurationitems

SP 1.3 Create or Release

Baselines

1. Baselines

2. Description of baselines


Change Requests Database


Changes to the work products under configuration management are tracked and controlled.

Track and Control Changes

(SG 2)

Change RequestDatabase

ChangeRequest

Control

Configuration

Items

(SP 2.2)

Tack Change

Request

(SP 2.1)

99


Typical Work Products for Tracking and Controlling Changes

Track and Control Changes

(SG 2)

SP 2.2 Control

Configuration Items

1. Revision history of configuration items

2. Archives of the Baselines

SP 2.1 Track Change

Requests

1. Change requests

Change RequestDatabase

ChangeRequest


Establish Integrity (SG 3)

Integrity of baselines is established and maintained.


Establish

Configuration

Management

Records

(SP 3.1)

Perform

Configuration

Audits

(SP 3.2)

Audit Results

Action Items

Reports

1010


Establish Integrity (SG 3)

Typical Work Products for Establishing Integrity


Audit Results

Action Items

Reports

SP 3.2 Konfigurationsaudits

durchführen

1. Configuration audit results

2. Action items

SP 3.1 Establish Configuration

Management Records

1. Revision history of configuration items

2. Change log

3. Copy of the change requests

4. Status of configuration items

5. Differences between baselines


SPI.PPQA + SPI.VER + SPI.VAL (Quality Engineering)

A 100 SPI.VER ReviewChecklist_Results [updated]

A 101 SPI.CM ReviewChecklist_Baseline [updated]

A 102 SPI.VER TestCasesPublishedMaterial

W 195 SPI.PPQA CMMIConformityChecklist [for project - updated]W 103 SPI.VER BugList

A 104 SPI.REQM RequTraceabilityMatrix [continued]

A 105 SPI.CM BaselineReviewProtocol [from Baseline

Review for Release 1]A 106 n/a BugfixBaseline [for Release 1]

T 107 SPI.VER PortalContentTest [Test Results]

T 108 SPI.VER BugfixPortalContent

T 109 SPI.PPQA NoncomplianceList

C 110 SPI.PPQA FixedNoncompliances

C 111 SPI.PPQA QualityPlan [updated]

C 220 SPI.CM ConfigurationManagementPlan

A 224 SPI.VER AcceptanceChecklist [updated]

A 225 SPI.VER AcceptanceLog [updated]

A 226 SPI.VER AcceptanceMinutesTemplate [updated]

Configuration Managenent gives you the status of your work products in your work breakdown structure/schedule.

Possible Status:•Assigned (A)• In Work (W)• In Test (T)• In Acceptance (C)•Released (R)

1111


Baselines define your planned targets in your project. At least the milestones should be baselines.

A baseline is a set of specifications or work products that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through change control procedures.

SPI.PPQA + SPI.VER + SPI.VAL (Quality Engineering)

A 100 SPI.VER ReviewChecklist_Results [updated] Initial Plan Tested

A 101 SPI.CM ReviewChecklist_Baseline [updated] Initial Plan Tested

A 102 SPI.VER TestCasesPublishedMaterial Initial Plan Tested

W 195 SPI.PPQA CMMIConformityChecklist [for project -

updated]

Initial Plan Tested

W 103 SPI.VER BugList Initial Plan In Work

A 104 SPI.REQM RequTraceabilityMatrix [continued] Initial Plan Tested

A 105 SPI.CM BaselineReviewProtocol [from Baseline

Review for Release 1]

Initial Plan In Work

A 106 n/a BugfixBaseline [for Release 1] Initial Plan In Work

T 107 SPI.VER PortalContentTest [Test Results] Initial Plan In Work

T 108 SPI.VER BugfixPortalContent Initial Plan Tested

T 109 SPI.PPQA NoncomplianceList Initial Plan In Work

C 110 SPI.PPQA FixedNoncompliances Initial Plan Tested

C 111 SPI.PPQA QualityPlan [updated] Initial Plan Released

C 220 SPI.CM ConfigurationManagementPlan Initial Plan Tested

A 224 SPI.VER AcceptanceChecklist [updated] Initial Plan Released

A 225 SPI.VER AcceptanceLog [updated] Initial Plan In Work

A 226 SPI.VER AcceptanceMinutesTemplate [updated] Initial Plan In Work

The (planned) Baseline

The (planned) Status


3 Process and Product Quality Assurance

1212


Process and Product Quality Assurance PA provide staff and management with objective insight into processes and associated work products.

(SG 1)

Objectively Evaluate

Processes and

Work Products

(SG 1)

Provide Objective Insight

(SG 2)

Reports and Records

Relevant Stakeholders


Relationships between the process areas Product and Process Quality Assurance, Verification and Validation

�The process area Product and Process Quality Assurance (PPQA) ensure that the performed process and associated work products and services adhere to applicable process descriptions, standards and procedures.

�The process area Verification (VER) ensure that the selected work products meet their specified requirements.

�The process area Validation (VAL) ensure that a product or a product component fulfills its intended use when placed in its intended environment.

1313


Adherence of the performed process and associated work products and services to applicable process descriptions, standards and procedures is objectively evaluated.

Objectively Evaluate Processes and Work Products

(SG 1)

Reports and Records

Objectively

Evaluate Work

Products and

Services

(SP 1.2)

Objectively

Evaluate

Processes

(SP 1.1)


Typical WP for Evaluating Objectively Processes and Work Products

Objectively Evaluate Processes and Work Products

(SG 1)

Reports and Records

SP 1.2 Objectively Evaluate

work Products and Services

1. Evaluation Reports

2. Noncompliance Reports

3. Corrective Actions

SP 1.1 Objectively Evaluate

Processes


2. Noncompliance Reports

3. Corrective Actions

1414


Noncompliance issues are objectively tracked and communicated, and resolution is ensured.

Provide Objective Insight (SG 2)

Reports and Records

Establish

Records

(SP 2.2)

Communicate Communicate

and Ensure

Resolution of

Non-

compliance

Issues

(SP 2.1)Relevant Stakeholders


Typical WP for Providing Objective Insight

Provide Objective Insight (SG 2)

Reports and Records

SP 2.2 Establish Records

1. Evaluation logs

2. Quality Assurance Reports

3. Status Reports of Corrective Actions

4. Reports of Quality Trends

SP 2.1 Communicate and

Ensure Resolution of Non-

compliance Issues

1. Corrective Actions Reports


3. Quality TrendsBetroffene

1515


Quality Audits are done to projects and the organizationat several points.

Project Phase

milestonemilestone

Project Phase

milestone

Project Phase

milestone

Milestone-ReviewDone at specfic

points of each project

Project-Setup-WorkshopDone at start of each project

Mini-Assessment/Audit/ReviewRandom selection of project

and when it is done


Assessment-Principles

Use a Process-Framework (CMMI)

Adhere to the nondisclosure

Management Support

Face the assessment as a team

Focus on Action

1616


4 Exercise


Exercise: Do MA and PPQA.

Task and Results:

1. 4 Teams define a Burndown Chart and prepare a template and training material (MA) – in a Sprint.

2. 1 Team prepares and does PPQA for the 4 teams to check if they do Scum properly.

3. 1 Team prepares and does PPQA for the PPQA team to check if they do the PPQA properly.

Goal:

� Do Scrum, MA and PPQA.

Duration

� Sprint of the 4 teams (50 min)

� Sprint Review of the QA team in front of class. (5 min)

� Sprint Retrospective of the QA team with the results of QA on QA team (5 min) Ex

erc

ise

1717


Exercise: define a Burndown Chart and prepare a template and training material (MA).

Tasks

1. Planning Meeting (5 min)

2. Sprint (10+2 / 10+2 / 10+2)

3. Sprint Review (5 min)

4. Sprint Retrospective (5 min)

Results (divide the work in your team!):

1. Burndown Chart Template

2. Test for the Burndown Chart

3. Training Material for your solution

4. Checked your solution against CMMI MA

5. Tested Burndown Chart

Goal:

� Do MA and Scrum Ex

erc

ise


Exercise: prepare and do PPQA for the 4 teams to check if they do Scum properly.

Tasks


2. Do QA on the 4 teams

3. Sprint Review in front of class (5 min)

4. Sprint Retrospective in front of class (5 min)


1. Checklist for Scrum

2. Issues found in doing PPQA for the 4 teams

Goal:

� Do PPQA

Hints:

� Coordinate work with the teams you support in the team‘s PlanningMeeting

� Give your feedback in the Sprint Retrospective of the teams Ex

erc

ise

1818


Exercise: prepare and do PPQA for the PPQA team to check if they do the PPQA properly.

Tasks


2. Do QA on the QA team

3. Sprint Review on your own (5 min)

4. Sprint Retrospective in front of class (5 min)


1. Checklist for PPQA

2. Issues found in doing PPQA for the PPQA team

Goal:

� Do PPQA

Hints:

� Coordinate work with the PPQA team in the PPQA‘s Planning Meeting

� Give your feedback in the Sprint Retrospective of the PPQA Ex

erc

ise


Revision History

Rev. no.

State Date Comments Responsible

1.0 Finished 17.10.2004 Initial version Malte Foegen

1.1 Finished 22.01.2006 Current template, added version history Malte Foegen

1.2 Finished 04.02.2006 Definition of Baseline added Malte Foegen

1.3 Finished 23.12.2007 Update layout, added burndown chart Malte Foegen

1.4 Finished 08.02.2009 New exercise Malte Foegen

Target status: finishedTemplate-Version: 3.6

1919


Trademarks and Service Marks

Capability Maturity Model; Capability Maturity Modeling; Carnegie Mellon, CMM; and CMMI are registered in the U. S. Patent and Trademark Office by Carnegie Mellon University.

IDEAL; Personal Software Process; PSP; SCAMPI; SCAMPI Lead Assessor; SCAMPI Lead Appraiser; SEI; SEPG; Team Software Process; and TSP are service marks of Carnegie Mellon University.

iNTACS is a registered trademark by the International Assessor Certification Scheme

Special permission to use CMMI® for Development, Version 1.2 (CMU/SEI-2006-TR-008 ESC-TR-2006-008), copyright 2006 by Carnegie Mellon University, in the combination of CMMI and ITIL is granted by the Software Engineering Institute. The SEI and CMU do not directly or indirectly endorse wibas IT Maturity Services GmbH’s work.

IT Maturity Services is a registered trademark by wibas IT Maturity Services GmbH

wibas IT Maturity Services is official SEI Partner of the Software Engineering Institute of the Carnegie Mellon University for SCAMPI appraisals and CMMI training. For inquiries, call:

wibas IT Maturity Services GmbHYvonne FischerCustomer Relations ManagerOtto-Hesse-Str. 19 B64293 DarmstadtGermanyTel: 0049 - 6151 - 50 33 49 - 21Fax: 0049 - 6151 - 50 33 49 - [email protected]


Otto-Hesse-Str. 19 B • 64293 Darmstadt • Germany • Phone +49 / 6151 / 50 33 49 - 0 • Fax +49 / 6151 / 50 33 49 – 33 • www.wibas.de

Hintermettlen 7 • 6318 Walchwil • Suisse • Phone +41 / 41 / 51122 - 90 • Fax +41 / 41 / 51122 - 91 • www.wibas.ch

11 - ma ppqa cm

Documents