traditional vs lean portfolio management, agile pmo & organisations

Post on 08-May-2015

14.175 Views

Category:

Business

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

This deck showcases how the future can look for organisations as they attempt to scale up agile and lean practices and principles across the entire organisation. Regardless if we have entered to do project/programme/portfolio work, once onsite I find it is a great way to introduce the wider organisation to the ideas that we use to deliver and how they can support all areas and activities in the organisation. Key concepts; - How traditional PMO and organisation are setup - Legacy mindset for are alive and still driving the majority of portfolio/organisation behaviours - Comparisons of traditional and agile/lean mindsets - Principles of agile/lean portfolio/organisation management - Organisational structure - Annual vs Incremental funding (Beyond Budgeting) - Limiting Work in Progress i.e. its only matters how many projects you finish, not start. - Managing and visualising capability - Coping with portfolio complexity through experimentation and validated learning - Removing the concept of projects and focusing on continuous delivery of value - Benefits of agile/lean portfolio/organisation management This deck was compiled using referenced materials and the support of David Joyce (@dpjoyce) and Ian Carroll (@caza_no7)

TRANSCRIPT

ThoughtWorks Local Office Day

Traditional vs Agile/Lean PMO

Dean Leffingwell Many “impediments” rise to a ceiling that is beyond the control of the teams. Sometimes the ceiling is represented by the PMO, a place many agilists perceive to be “the mother ship of impediments.”

Indeed, if you mention the words project office or PMO among a group of agilists in the trenches, reactions will vary, but probably only from negative . . . to very negative.

It should come as no surprise that our agile teams, and programs, are being held accountable to legacy waterfall practices for governance, and traditional methods of project management.

They are based around legacy mindsets, but that was all there was.

Legacy MindsetsWidget engineering“Draw it up, and build it like you drew it”

Order-taker mentality“You build, what we tell you to build”

Maximize utilisation“The more we start, the more we finish”

Control through milestones“If we still can’t tell where we are we’ll just ask for more detailed data”

We can plan a full year of projects“If we only planned in more detail, we could really get it right this year.”

Just get it done“This is the plan ‘we’ agreed to; now execute it”

Project PlaningOrganising for Work, Henry L. Gantt, Harcourt, Brace and Howe, 1919

People UtilisationOrganising for Work, Henry L. Gantt, Harcourt, Brace and Howe, 1919

Peter Drucker

“There is nothing so useless as doing efficiently that which should not be done at all.”

Focus on execution through agileShould it be done? NOT Can it be done?

www.bbrt.org › Beyond-budgeting

Dave Snowdon – Cynefin Model

Programmes are complex adaptive systems,

hence experimentation is required to understand

Programme and projects

How do be a Programme manager – and why they are awesome….Little about delivering value

From Projects to Continuous Delivery of Value

“Traditionally, based on a construction-like metaphor, a “project” gathered some resources together, a set of requirements, a mission, start and end dates, and a project manager.

The project then binds these things to together in a package that tends to become fixed and immutable.

Once started, every project develops its own antibodies to change.No one wants to be part of a canceled project; jobs may be on the line, even if the result was a “successful early failure” of a new product or technology.

How does one innovate in that environment?”

Dean Leffingwell

From Continuous Delivery to Continuous Validated Learning

Lean Startup – Eric Ries Plan, Do, Check, Act - Deming

How does experimentation apply to everything we do

How Programme Wall Could be

top related