capability maturity model integration project monitoring and control software management 2008 –...

25
Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Upload: dale-mclaughlin

Post on 03-Jan-2016

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Capability Maturity Model Integration

Project Monitoring and Control

Software Management 2008 – 2009

Alexander IdeNiels Soetens

Page 2: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

2 / 25

Project Monitoring and ControlPurpose

Monitoring the project’s process

Recognize deviation of the project plan

Significant deviation? → take corrective actions

Page 3: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

3 / 25

Project Monitoring and ControlSpecific Goals

SG 1 Monitor Project Against Plan

SP 1.1 Monitor Project Planning Parameters

SP 1.2 Monitor Commitments

SP 1.3 Monitor Project Risks

SP 1.4 Monitor Data Management

SP 1.5 Monitor Stakeholder Involvement

SP 1.6 Conduct Progress Reviews

SP 1.7 Conduct Milestone Reviews

Page 4: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

4 / 25

Project Monitoring and ControlSpecific Goals

Usage of Trac

Create and assign tickets to a specific person

Create deadline (usually milestones)

Easy to monitor the completion of a milestone

Other: Microsoft project,…

SP 1.1 Monitor Project Planning Parameters

Page 5: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

5 / 25

Project Monitoring and Control Specific Goals

Page 6: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

6 / 25

Project Monitoring and ControlSpecific Goals

Commitments are set with every milestone

Regularly review commitments (at meeting)

Identify commitments that have not been satisfied

SP 1.2 Monitor Commitments

Page 7: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

7 / 25

Project Monitoring and ControlSpecific Goals

Usage of War Room List

Specify the risk and rate its importance

Communicate and discuss risks at meetings

Resolve major risks as quick as possible

SP 1.3 Monitor Project Risks

Page 8: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

8 / 25

Project Monitoring and Control Specific Goals

Page 9: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

9 / 25

Project Monitoring and ControlSpecific Goals

Periodically review documentation

Identify and document issues and impacts

Documentation on Trac, Dropbox, Googlegroups, SVN

SP 1.4 Monitor Data Management

Page 10: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

10 / 25

Project Monitoring and ControlSpecific Goals

Periodically review stakeholder involvement

Hadra case:

Project review (Markomo)

Gathering workflow informatio (Guido)

MashedUp case:

Assitents = stakeholders and monitor everything

Document results made by stakeholder involvement

SP 1.5 Monitor Stakeholder Involvement

Page 11: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

11 / 25

Project Monitoring and ControlSpecific Goals

Progress reviews with assistants

Daily small scrum meetings

Sprint scrum meetings

SP 1.6 Conduct Progress Reviews

Page 12: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

12 / 25

Project Monitoring and ControlSpecific Goals

Two week milestone review meeting

Review accomplished work

Weekly review meeting with assistant

Guidance with the projects progress

In MashedUp these are +- stackeholder meetings

SP 1.7 Conduct Milestone Reviews

Page 13: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

13 / 25

Project Monitoring and ControlSpecific Goals

SG 2 Manage Corrective Action to Closure

SP 2.1 Analyze Issues

SP 2.2 Take Corrective Action

SP 2.3 Manage Corrective Action

Page 14: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

14 / 25

Project Monitoring and ControlSpecific Goals

Collect and analyze issues

List issues needing corrective actions

Analyze issues to determine need for corrective action

SP 2.1 Analyze Issues

Page 15: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

15 / 25

Project Monitoring and ControlSpecific Goals

Corrective action plan

Revising estimates and plans

Adding resources

Changing processes

Revising project risks

SP 2.2 Take Corrective Action

Page 16: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

16 / 25

Project Monitoring and ControlSpecific Goals

Monitor corrective actions

Analyze results of corrective actions

Determine and document appropriate actions

SP 2.3 Manage Corrective Action

Page 17: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

17 / 25

Project Monitoring and ControlGeneric Practices GG 2

GG 2 Institutionalize a Managed Process

GP2.1 Establish an Organizational Policy

GP2.2 Plan the Process

GP2.3 Provide Resources

GP2.4 Assign Responsibility

GP2.5 Train People

GP2.6 Manage Configurations

GP2.7 Identify and Involve Relevant Stakeholders

GP2.8 Monitor and Control the Process

GP2.9 Objectively Evaluate Adherence

GP2.10 Review Status with Higher Level Management

Page 18: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

18 / 25

Project Monitoring and ControlGeneric Practices GG 2

GP2.1 Establish an Organizational Policy

Determine the roadmap that has to be followed to create a good monitor plan

GP2.2 Plan the Process

Create the planing of the process and maintain it

GP2.3 Provide Resources

Provide the resources, the programs and the systems

Page 19: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

19 / 25

Project Monitoring and ControlGeneric Practices GG 2

GP2.4 Assign Responsibility

Determine who is in charge of the process

GP2.5 Train People

GP2.6 Manage Configurations

Make levels of control to group the work products

Page 20: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

20 / 25

Project Monitoring and ControlGeneric Practices GG 2

GP2.7 Identify and Involve Relevant Stakeholders

Examples of involvement:

Assessing project against plan

Reviewing:

Project risks

Progress

Data management

Resolving issues

Page 21: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

21 / 25

Project Monitoring and ControlGeneric Practices GG 2

GP2.8 Monitor and Control the Process

GP2.9 Objectively Evaluate Adherence

Checking if everything is according to plan

GP2.10 Review Status with Higher Level Management

Page 22: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

22 / 25

Project Monitoring and ControlGeneric Practices GG 3

GG 3 Institutionalize a Defined Process

GP3.1 Establish a Defined Process

GP3.2 Collect Improvement Information

e.g.:

Records of significant deviations

Corrective action results

Page 23: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

23 / 25

Project Monitoring and ControlFindings

Strengths

• Multitouch monitors workload.

Opportunities for Improvement

• WAFL finds it difficult to control fellow students.

• WAFL underestimated the risks

Proposed Actions

Page 24: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

24 / 25

Project Monitoring and ControlGlossary

CMMI Capability Maturity Model Integration

PMC Project Monitoring and Control

Page 25: Capability Maturity Model Integration Project Monitoring and Control Software Management 2008 – 2009 Alexander Ide Niels Soetens

Alexander IdeNiels Soetens

25 / 25

Project Monitoring and ControlReferences

CMMI for Development version 1.2 http://www.sei.cmu.edu/publications/documents/06.reports/06tr008.html

Software Quality Assurance within the CMMi frameworkhttp://www.software-quality-assurance.org/cmmi-project-monitoring-and-control.html