The Agile PMO

14
1 The Agile PMO Presented by Sanjiv Augustine July 22, 2009 From Process Police to Adaptive Governance Why an Agile PMO? Setting up the Agile PMO Scaling Scrum through Adaptive Governance o Project Prioritization & Selection o Portfolio Tracking o Resource Management o Sustainable Agile Adoption Q&A Agenda Adap0ve Governance Adap&ve governance is the collabora’ve, flexible and learning‐based management of programs and por5olios.

description

The Agile PMO: From Process Police to Adaptive Governance: This webcast provides techniques for an Agile PMO and discusses how those concepts are being applied in the industry. Presented by LitheSpeed.

Transcript of The Agile PMO

Page 1: The Agile PMO

1

TheAgilePMO

PresentedbySanjivAugustine

July22,2009

FromProcessPolicetoAdaptiveGovernance

•  WhyanAgilePMO?•  SettinguptheAgilePMO•  ScalingScrumthroughAdaptiveGovernanceo  ProjectPrioritization&Selectiono  PortfolioTrackingo  ResourceManagemento  SustainableAgileAdoption

•  Q&A

Agenda

Adap0veGovernance

Adap&vegovernanceisthecollabora've,flexibleand

learning‐basedmanagementofprograms

andpor5olios.

Page 2: The Agile PMO

2

WhyanAgilePMO?

WhyanAgilePMO?

HowarePMOsDoing?

“TherecentresearchliteratureonPMOsprovidesanambiguouspictureofthevaluecaseforPMOsandsuggeststhetenuousnatureoftheircurrentposi0oninmany

organiza0ons.”

‐HurtandThomas,BuildingValuethroughSustainablePMOs,ProjectManagementJournal,March2009

“53%ofCIOssaytheirITprojectpriori0za0onispoli0callydriven.”

‐CIOInsight,2004

“Theinfluenceofaconserva0ve,process‐orientedpersonalityintotheworldofagile

technologiesandagile‐thinkingtechnologistsisnearlyasra0onalasusinga

WorldWarItrenchwarfaregeneral’smindsettodirecttheeffortsinAfghanistan.”

‐CascaquotedbyThornberry,PMOskeepprojectsontrackandunderbudget,ZDNetAsia

Someofthechallenges/problemsfacedbyPMOs:

•  Lackofauthorityandexecutivesupport•  Lackofdemandmanagement•  Focusonupwardsreporting•  Processstandardizationandauditingrigidity•  Over‐relianceonprojectportfolio

managementtools•  Staffversuslineorganizationalstructure:

createsoverhead,lackofaccountabilityandcareerplateau

•  Misalignmentoftools,techniquesandreportingwithAgilemethods

•  PMOsperceivedas“processpolice”whoblockratherthanenable

Page 3: The Agile PMO

3

SettinguptheAgilePMO

TwoVisionsforthePMO

“Anorganizationalunittocentralizeandcoordinatethemanagementofprojectsunderitsdomain.APMOoverseesthemanagementofprojects,programsoracombinationofboth.”

Agroupofprojectleaderswhoachievetheseresults:

•  Weincreasereturnoninvestmentbymakingcon&nuousflowofvalueourfocus.

•  Wedeliverreliableresultsbyengagingcustomersinfrequentinterac&onsandsharedownership.

•  Weexpectuncertaintyandmanageforitthroughitera&ons,an&cipa&on,andadapta&on.

•  Weunleashcrea0vityandinnova0onbyrecognizingthatindividualsaretheul&matesourceofvalue,andcrea&nganenvironmentwheretheycanmakeadifference.

•  Weboostperformancethroughgroupaccountabilityforresultsandsharedresponsibilityforteameffec&veness.

•  Weimproveeffec0venessandreliabilitythroughsitua&onallyspecificstrategies,processesandprac&ces.

AGuidetotheProjectManagementBodyofKnowledge(PMBOK®Guide),ThirdEdi&on©2004 Declara'onofInter‐dependence,h]p://pmdoi.org[©2005DavidAnderson,SanjivAugus&ne,

ChristopherAvery,AlistairCockburn,MikeCohn,DougDeCarlo,DonnaFitzgerald,JimHighsmith,OleJepsen,LowellLindstrom,ToddLi]le,KentMcDonald,PollyannaPixton,PrestonSmithandRobertWysocki.]

HowbestcanaPMOaidindeliveringbusinessvalueacrossmultipleprojects,programsandportfolios?

Page 4: The Agile PMO

4

•  Encourageface‐to‐facedialogueacrosslevels•  Createoverlappingmanagementwith“linkingpins”•  RuntheLean‐AgilePMOasanAgileprojectteam

Source:TheLean­AgilePMO,SanjivAugustineandRolandCuellar(CutterConsortium2006)

Organiza0onalStructure

Oscilla0ngBetweenInforma0onDiscoveryand

Integra0on

Acentralizedstructureworkswellfordiscovery,becausetheindividual’sroleistoWind

informationandreportitback.Incontrast,arichlyconnected

networkworksbestforintegrationanddecision

making,becauseitallowstheindividualtoheareveryoneelse’sopinionaboutthe

expectedreturnfromeachofthealternatives.

‐AlexPentland,HowSocialNetworksNetworkBest,HarvardBusinessReview,

February2009

Imagefromwww.crea'on'ps.com/bees.html

•  Optimizeforthroughput,notutilization

•  LimitWorkinProcess(WIP),notteamfreedom

•  ObsessabouttheFlowofvalue,nottheprocess

LeanPrinciplesfortheAgilePMO

Throughput

Throughputinprojectpor5oliomanagementistherateatwhichprojectsnetmoneyforthebusiness.

Page 5: The Agile PMO

5

AgilePMOsconsiderScrumteamstobetheircustomers,andsupportthemin:

•  Bringingleandisciplinetoprojectprioritization&selection

•  TrackingprojectportfoliosusingAgiletrackingtechniques

•  Movingtowardsastableteamsmodelofresourcemanagement

•  ScalingandsustainingagileadoptionbysupportingandempoweringScrumteams

AnAgileRoleforthePMO

Adap0veGovernance

Adap&vegovernanceisthecollabora've,flexibleand

learning‐basedmanagementofprograms

andpor5olios.

ProjectPrioritization&Selection

Page 6: The Agile PMO

6

TheTypicalProjectPorXolio

Source:TheLean­AgilePMO,SanjivAugustineandRolandCuellar(CutterConsortium2006)

•  ToomuchWorkinProcess(toomanyin‐Wlightprojects)

•  Noprojectprioritizationbybusinessvalue

•  Resourceover­utilization

•  Dangerousvariation(largebatchsizes,unregulateddemand,irregularrateofservice)

•  Terminatesickprojects•  Splitlargeprojectsinsmallerones•  Prioritizeprojectsbybusinessvalue,atleastwithinbusinessunit

•  Limitdevelopmenttimeframetomonths•  Re­prioritizeprojectsregularly

1

Development

3 24

Li\le’sLaw

WIP

Comple&onRate

Por5olioRealignment

BusinessGoals&Strategy Produc0on Sunset

CycleTime=

Backlog

Page 7: The Agile PMO

7

•  Shouldwedothisprojectatall?•  Determinerankingcriteria•  Rankprojectsandcreaterankedprojectbacklog

ProjectIden0fica0on&Selec0on

ExampleProjectSelec&on

Page 8: The Agile PMO

8

PortfolioTracking

•  Featureslaidoutonindexcardsasperoverallreleaseplan

•  Cardcolorsidentifyagileteams

•  Labelsidentifydependentteams

•  Rowstrackfeaturestreams•  Columnstracksprints/timeline

Por5olioAlignmentWall

Page 9: The Agile PMO

9

ManagetheFlow

•  Limitrequestbacklogtoafewitems•  PrioritizerequestsbyValue•  Measuretimetodeliversmall,medium

andlargerequests•  Trackandmanagework­in­process

(WIP)tooptimizethroughput•  Optimizedeliveryspeedbylimiting

work‐in‐processtoobservedcapacity,thusensuringcontinuousWlowofvalue.

0 25 50 75 100 125 150 175

9-O

ct

23-O

ct

6-N

ov

20-N

ov

4-D

ec

18-D

ec

1-Ja

n 15

-Jan

29-J

an

12-F

eb

26-F

eb

11-M

ar

Time

Features

Inventory Started Designed Coded Complete Bad:Raggedflow,longcycle&me(StartedtoCompleted)

Be\er:Smoothflow,fastdelivery

IdentifyandaddressbottlenecksinworkWlowstagestosmoothFlowofvalue.

ResourceManagement

Page 10: The Agile PMO

10

Tradi0onalResourceManagement

•  Runmanyprojectsconcurrently,withsimilarpriorities

•  Splitresourcesbetweenmultipleprojects

•  Stressmaximumresourceutilization

•  ROIonlyafterprojectsaredone Time

Projects&Resources

ROI

CostsofTask‐Switching

Source:ManagingNewProductandProcessDevelopment,ClarkandWheelwright,p.242,1992

Page 11: The Agile PMO

11

•  Multiple,stableteamseachfocusedonasingleprojectatatime

•  Dedicatedtoplatformsorlinesofbusiness

•  Platformownerprioritizesnextproject

•  Result:o  Supportmultiplelinesofbusiness

simultaneouslyo  Focusedeffortresultsinquick

deliveryforindividualprojectso  Clearaccountability

o  Stabilityandpredictability

Source:TheLean­AgilePMO,SanjivAugustineandRolandCuellar(CutterConsortium2006)

StableTeams

Leanorganizations:•  Dedicatecoreresourcestoeachprojectteam

•  Ensurethateachteamhasallresourcesneededtocompleteprojects

•  Stressmaximumprojectthroughput

•  ROIdeliveredincrementallywitheachprojectrelease

LeanResourceManagement

ROI

Time

Projects&Resources

Page 12: The Agile PMO

12

“…foralargeorganizationtoworkitmustbehavelikearelatedgroupofsmallorganizations.”

­E.F.Schumacher,SmallisBeautiful

Conqueranddividebybuildingafederationofagileteams:•  Buildthe“whole”intothe“parts”•  Setasizelimit(e.g.7+/‐2people)•  Togrow,breakoffnewintegratedAgileteamswhenteamsizelimitisreached

•  CoordinateathigherlevelviaAgilePMO

ScalingAgileTeams

SustainableAgileAdoption

Page 13: The Agile PMO

13

•  Conductone­on­onesessionswithmanagersandexecutives

•  Establishatrainingcurriculum•  CreateanAgilecareerpath•  LocateAgilecoachesintheAgilePMO

•  Provideprojectteamcoachingandmentoring

•  ProvidetrainingandcoachingonAgileEngineeringtechniques

Educa0onandCoaching

Createadefinedandreliableprocess:•  Standardizehigh­levelprocesssteps,deliverables,toolsandartifacts

• Agreeonprocessauditprocedures• Developstandardprocessmetrics

ProcessStandardiza0on

Page 14: The Agile PMO

14

ContactUsforFurtherInforma0on

[email protected]

OntheWeb:

http://www.lithespeed.comhttp://www.sanjivaugustine.com

"IonlywishIhadreadthisbookwhenIstartedmycareerinsokwareproductmanagement,orevenbe]eryet,whenIwasgivenmyfirstprojecttomanage.Inaddi&ontoprovidinganexcellenthandbookformanagingwithagilesokwaredevelopmentmethodologies,ManagingAgileProjectsoffersaguidetomoreeffec&veprojectmanagementinmanybusinessselngs."JohnP.Barnes,formerVicePresidentofProductManagementatEmergis,Inc.