Copyright 2009 by Process Performance LLC Process Cartography A Graphical Approach to Process...

Copyright 2009 by Process Performance LLC

Process CartographyA Graphical Approach to Process Definition

Presented byRudy Gamberini


Quiz

CMM Capability Maturity Model

PAL Process Asset Library

BHB Big Honkin Binder


What is Process Cartography?

Process - a series of activities that produce a desired result or product

Cartography - the art of map making


Initiating a process improvement program without having a clear understanding of your existing development process is like taking a car trip, to a new destination, without using a map to chart your course.

You would eventually succeed but the efficiency of your trip would be questionable.

Real Men Don’t Use Maps


Sure Signs You are Lost

• Don’t know where to begin to initiate a process improvement program.

• Everyone has a different opinion about what process is actually being followed.

• Your auditors are given three different names for the same document.

• You tried to collect process metrics but the data was garbage.


Sure Signs You are Lost

• New hires are trained in fifteen minutes, using your white-board with lots pretty color, interesting lines, boxes, arrows, and clouds.

• Your development staff is never quite sure about anything.

• Project repositories look more like a maze for information hiding than an organized library of project information.


Key Features of Maps

• Enable efficient navigation of new territory• Utilize minimal graphical symbols to get the information

across• Learning curve measured in minutes • Convey a lot of information very efficiently


Fundamentals of Maps• Area specific• Utilize landmarks to support orientation • Simple symbols, few symbols (legend)• Unique graphics (distinguishable, colors)• Form and function (map looks like the area it

represents)


Your Mission

You have been dropped off in the woods with a compass, notebook, and a pencil. You must find your way out and be able to lead someone back to you original starting point.

What would you do?


Getting StartedIdentifying the Landmarks

Map making begins by identifying the area being mapped and surveying it for identifiable landmarks.

Area equates to LifecycleLandmarks equates to Artifacts (AKA Work Products)


Lifecycle Phases

Phase ActivityInception Defining at a high level what the

product is and its scope.Elaboration Expanding on the original ideas to a

level of detail that is sufficient toinitiate product design.

Construction Detailed design, build and initial test.

Transition Final test and beta release.

Live Production support and enhancementevaluation.


Phase-Artifact Table

Phase ArtifactInception Business Justification, Product

Requirements SpecificationElaboration Product Functional Specification, Project

Plan, Project Schedule, Risk ManagementPlan

Construction High Level Design, Detailed Design, SystemTest Cases/Results

Transition Product Acceptance Test Cases/Results,Project Debrief

Live Final Release/Release Note, Support andField Reports


Map Symbols

Activity - actions that either create or mature artifacts

Milestone Artifact - artifacts that have matured to their final state and are considered important

Phase - a collection of activities and artifacts

Activity

MilestoneArtifact[state]

Phase


Mapping Symbols

Metric - measurements used to monitor and control the process

Artifact - Work Product, tangible, has a known state

Synchronization Bar - splits and joins parallel processes

Trigger - initiates process execution, permits reentrance

Artifact[state]

Metric


Phase-Artifact Map

Inception

New

Prod

uct

Elaboration

BusinessJustification[approved]

ProductReqmt Spec[approved]

Artifact Table


Putting it all together

Inception

New

Prod

uct

Elaboration

Construction

Transition

ProjectDebrief[draft]

Live

ProductReqmt Spec[approved]

BusinessJustification[approved]

ProjectSchedule

[approved]

PFS[approved]

Risk M gmtPlan

[approved]

High-levelDesign

[approved]

System TestCases

[Approved]

ProduceAcceptance

Test[approved]


First Level Map

Inception Elaboration Construction Transition Live


Phase Exit CriteriaInception Software Development Plan

Road MapRisk ListVision Document

Elaboration Iteration PlanUse Cases ModelRequirements Matrix

Construction Design ModelArchitectureCode

Transition Deployment ModelInstallation ManualRelease Note

Exit Criteria by Phase


Map Expansion

[changes com plete]

Refinem ent Cycle

Create/Update LLD Review

Low LevelDesign[draft]

Low LevelDesign

[reviewed]

MeetingMinutes

PeerReview

Low LevelDesign

[apprvd]

CreateSystem Test

Case

System TestCases[draft]

PeerReview

System TestCases

[apprvd]

EnterConstruction

Construction


Process Pattern

Activity Artifact Activity

Artifact

[quality gate]

Refinem ent Cycle

M etric


Symbol Extensions

Compact Refinement Cycle - simplified way to represent an iterative refinement cycle. Useful in capturing peer review sessions.

Refinem tCycle


Demo


Key Learning Points

• Maps are only valuable if they cover the area you desire to explore.

• An organization’s development practices are unique and therefore require their own maps.

• Using some else’s map is like navigating NY with a map of Chicago.


Key Learning Points cont.• For maps to be useful the symbols must be few in

number and visually unique.• Landmarks are the most important part of the map. • If your process map is getting too complex it is

probably at too low a level of detail.


Early Adopters

• Boeing Space Division• Xerox• Nokia• US Army (CMM level 3)• US Air Force• Mountside Software (Netherlands)• REUTERS (globally deployed)


For Additional Information:[email protected]

Copyright 2009 by Process Performance LLC Process Cartography A Graphical Approach to Process...

Documents

Transcript of Copyright 2009 by Process Performance LLC Process Cartography A Graphical Approach to Process...