27
Copyright 2009 by Process Performance LLC Discipline Centric Process Framework The Dewey Decimal System for Software Development Process Control
| Date post: | 20-Jan-2018 |
| Category: |
Documents |
| Upload: | ginger-nichols |
| View: | 213 times |
| Download: | 0 times |
Copyright 2009 by Process Performance LLC
Discipline Centric Process Framework
The Dewey Decimal System for Software Development Process Control
Copyright 2009 by Process Performance LLC
The Problem• Every project takes on a life of its own.• Project repositories are unique to each project and
difficult to navigate.• If a cost accounting system is used it is too complex
and often misleading. • Historical data is of little use for current project
prediction modeling.
Copyright 2009 by Process Performance LLC
The Goal• Make all projects look alike, regardless of lifecycle
chosen, with respect to:• Project web representation• Configuration management structure (Visual Source
Safe, ClearCase)• Project accounting (timesheet program)
• Create a framework to capture historical data that is supportive of prediction modeling.
Copyright 2009 by Process Performance LLC
The Quest
Find a lifecycle independent framework that addresses all the
project assets.
Copyright 2009 by Process Performance LLC
Topics• Aligning terminology• Software Development Process Hierarchy• Ten Disciplines (AKA Workflows)• Building a Common Framework• Applying the Framework• Advantages
Copyright 2009 by Process Performance LLC
Align Terminology
Lifecycle A collection of activities and artifacts that areundertaken and created to execute a softwaredevelopment effort.
Phase Lifecycle subdivision associated with activitiesand artifacts.
Workflow A executable thread of related activities.
Discipline A collection of related activities and artifactsthat fulfill a fundamental need of softwaredevelopment.
Copyright 2009 by Process Performance LLC
Development Lifecycle Hierarchy
ActivityArtifact
BuildingBlocks
Inception Elaboration Construction Validation Transition
Phase
Lifecycle
Static Model
Copyright 2009 by Process Performance LLC
Dynamic Process Elements
Role I am a project leader. What are myresponsibilities and when are they required?
Workflow I need to get this new requirement added tothe project. How do I go about doing thatand what needs to be done?
Discipline Are you sure all the bases are covered tobuild a quality software product?
Copyright 2009 by Process Performance LLC
Lifecycle and Dimensions
PM Role
Lifecycle
W orkflowNew Rqm t
Copyright 2009 by Process Performance LLC
The Ten Disciplines of Highly Effective Software Development
• Business Modeling• Requirements• Analysis & Design• Implementation • Validation• Deployment
• Project Management• Configuration & Change
Management• Environment• Training
Copyright 2009 by Process Performance LLC
Lifecycle and Disciplines
Requirem ents
Analysis &Design
Validation
Copyright 2009 by Process Performance LLC
Disciplines can be Universally Applied to Lifecycles
Analysis &Design
Analysis &Design
Analysis &Design
Copyright 2009 by Process Performance LLC
Use Disciplines as the Framework
Copyright 2009 by Process Performance LLC
Applying the Framework
Copyright 2009 by Process Performance LLC
A Common Navigation Paradigm
Discipline
Project Web
WBS/Planview
Dev. Lifecycle(AKA Cartography)
PAL
Prediction Models
Project Repository/VSS
Development Lifecycle
Visual Source Safe
Artifact List
WBS/Planview
Copyright 2009 by Process Performance LLC
Prediction Modeling
Copyright 2009 by Process Performance LLC
RUP and Disciplines
Copyright 2009 by Process Performance LLC
DLM Actual Data from Planview
Requirements Work Flow
051015202530354045505560657075
8/6/2000
8/13/2000
8/20/2000
8/27/2000
9/3/2000
9/10/2000
9/17/2000
9/24/2000
10/1/2000
10/8/2000
10/15/2000
10/22/2000
10/29/2000
11/5/2000
11/12/2000
11/19/2000
11/26/2000
12/3/2000
12/10/2000
12/17/2000
12/24/2000
12/31/2000
1/7/2001
1/14/2001
1/21/2001
1/28/2001
2/4/2001
2/11/2001
2/18/2001
2/25/2001
3/4/2001
3/11/2001
3/18/2001
3/25/2001
4/1/2001
4/8/2001
4/15/2001
4/22/2001
4/29/2001
Work Weeks
Hou
rs
Copyright 2009 by Process Performance LLC
DLM Actual Data from Planview
Analysis & Design Work Flow
0
25
50
75
100
125
150
175
8/6/2000
8/13/2000
8/20/2000
8/27/2000
9/3/2000
9/10/2000
9/17/2000
9/24/2000
10/1/2000
10/8/2000
10/15/2000
10/22/2000
10/29/2000
11/5/2000
11/12/2000
11/19/2000
11/26/2000
12/3/2000
12/10/2000
12/17/2000
12/24/2000
12/31/2000
1/7/2001
1/14/2001
1/21/2001
1/28/2001
2/4/2001
2/11/2001
2/18/2001
2/25/2001
3/4/2001
3/11/2001
3/18/2001
3/25/2001
4/1/2001
4/8/2001
4/15/2001
4/22/2001
4/29/2001
Work Weeks
Hou
rs
Copyright 2009 by Process Performance LLC
DLM Actual Data from Planview
Project Management Work Flow
051015202530354045505560657075
8/6/2000
8/13/2000
8/20/2000
8/27/2000
9/3/2000
9/10/2000
9/17/2000
9/24/2000
10/1/2000
10/8/2000
10/15/2000
10/22/2000
10/29/2000
11/5/2000
11/12/2000
11/19/2000
11/26/2000
12/3/2000
12/10/2000
12/17/2000
12/24/2000
12/31/2000
1/7/2001
1/14/2001
1/21/2001
1/28/2001
2/4/2001
2/11/2001
2/18/2001
2/25/2001
3/4/2001
3/11/2001
3/18/2001
3/25/2001
4/1/2001
4/8/2001
4/15/2001
4/22/2001
4/29/2001
5/6/2001
5/13/2001
Work Weeks
Hour
s
Copyright 2009 by Process Performance LLC
Key Points (1/2)• Having a common navigation approach greatly
simplifies the project infrastructure. • Aligning the Disciplines with widely accepted process
models (RUP and CMM) eases acceptance. • Software Development Process Due Diligence (QA) is
more easily applied and understood.
Copyright 2009 by Process Performance LLC
Key Points (2/2)• A common framework supports the construction of a
historical database that can be used to predict project success.
