© 2014 Point of Sail Implementing Agile/Scrum with a Tradition PMO… and Making it Work PMI Pittsburgh Chapter Meeting 12 June 2014

© 2014 Point of Sail© 2014 Point of Sail

Implementing Agile/Scrum with a Tradition PMO…

and Making it Work

PMI Pittsburgh Chapter Meeting

12 June 2014


Can a PMO and Agile/Scrum Coexist


What Does Agile / Scrum Want


What Does The PMO Want


What Does The Customer Want


A Little About Agile / Scrum




Making It Work Together

Agenda


Transparency

Insp

ectio

n Adaption

First Leg - Transparency

Aspects of the process that affect the outcome must be visible to those managing the outcome

Aspects of the process that affect the outcome must be visible to those managing the outcome

The Three Legs of Scrum


Transparency

Insp

ectio

n Adaption

Second Leg - Inspection

Various aspects of the process must be inspected frequently enough so that unacceptable

variance in the process can be detected

Various aspects of the process must be inspected frequently enough so that unacceptable

variance in the process can be detected



Transparency

Insp

ectio

n Adaption

Third Leg - Adaption

If one or more aspects of the process are outside of

acceptable limits adjustments to the process must be made

If one or more aspects of the process are outside of

acceptable limits adjustments to the process must be made



Scrum framework consists of…

• Scrum Teams• Time-Boxes• Artifacts• Rules

Scrum Concepts


• Optimized for flexibility and productivity:– Self-Organizing– Cross-Functional– Work in Iterations– Accountable to themselves and the

Product Owner

Scrum Concepts – Scrum Teams


• Three Roles:– Scrum Master– Product Owner– The Team…that does the work



Ham n’ EggsHam n’ EggsInvolvedInvolved CommittedCommitted



• Scrum Master - “Pig” Scrum Process• Product Owner - “Pig” Product Backlog• Team - “Pig” Sprint Backlog

• Everyone else…a “Chicken”

• The Product Owner Drives the Order The Team Drives the Schedule





Time Boxes…

• Release Planning Meeting• Sprint Planning Meeting• The Sprint• Daily Scrum• Sprint Retrospective

Scrum Concepts – Time Boxes


Principal Artifacts…

• Product Backlog• Sprint Backlog• Release Burndown• Sprint Burndown

• The Product Itself

Scrum Concepts - Artifacts


Scrum Concepts - Rules

Rules…

• Bind Together Scrum’s Team, Time-Boxes, and Artifacts

• Purpose of Sprint• Definition of Done• Undone Work




Project Phasesand

Artifacts

Orderand

Audit

=

=



Life of A Project

What Does the PMO Want - Order


Phase PMO

Initiation Project CharterBusiness Case

Planning Project PlanRequirements

Execution

DevelopmentTesting

Training Plan

Controlling

Change ManagementRisk/Issues Management

Agenda and MinutesStatus Reporting

Sign-Off

Closing Post Implementation Project Survey

What Does The PMO Want - Audit


What Does the Customer Want






Making It Work


Making It All Work

Life of A Project

Q Q Q Q Q Q P

A A A A A A A

/Scrum/Scrum

RetroRetro RetroRetro RetroRetroPppp

Q Q Qq q q q

A A A A A

A A A A


Phase PMO Agile/Scrum

Initiation Project CharterBusiness Case

Planning Project PlanRequirements

Product Backlog

Execution

DevelopmentTesting

Training Plan

Product BacklogSprint BacklogSprints/Scrums

Controlling

Change ManagementRisk/Issues Management

Agenda and MinutesStatus Reporting

Sign-Off

Product Burndown

Sprint BurndownRetrospectives

Planning

Closing Post Implementation Project Survey

Making It All Work with the PMO


Constraint

PMO Agile/Scrum

Scope Requirements Document

Product Backlog

Time Project Plan Product Burndown

Cost Cost Model (Project Plan)

Cost Model (Product Backlog)

Quality Gate Post Inspection/Adaption

Making It All Work with the Customer


Can a PMO and Agile/Scrum Coexist


Documents

© 2014 Point of Sail Implementing Agile/Scrum with a Tradition PMO… and Making it Work PMI Pittsburgh Chapter Meeting 12 June 2014