The Future of Project Management

Changing the change function

A Provocation….

You can deliver

a fixed requirement project using Agile techniques

You can’t deliver

a variable requirement project using traditional techniques

Therefore the future of project management is Agile

Changing requirements

Business changes

People’s understanding changes

“I’ll know it when I see it”

Ever increasing pace of change

Change Controls

Requirements

Time Cost Requirements

Time CostFixed

Variable

Construction / Infrastructure Business Change / Software

Agile provides tools, structure, culture and discipline to embrace

change in requirements

Core Agile Practices

Break requirements into small pieces

Prioritise these requirements according to the business need

Deliver “go-live-able” functionality every 2-6 weeks

Collaborative team Combining business and technical resource

Regular and frequent feedback within the team and from “business as usual”

Why Agile?• Requirements can and

should change

• “I’ll know it when I see it” IKIWISI

• Better return on investment

• Deliver business benefit quickly

• Hit deadlines

• Project can be seen to be delivering / on track

• De-risks implementation

Agile RoIWaterfall RoI

Reducing Generic Project Risk

Changing requirements

Estimation

Testing / Acceptance

Integration / Go-Live

Key Person

So what’s getting in the way?

No single methodology is enough

Scrum

XPDSDMEngineeringGovernance / Mgt

Where do I start….?

Collaboration Requirements into User Stories Defining and automating tests

Deployment Scaling to Programmes and Portfolios

Operating in a traditional environment Procurement and contracts

Scrum

XPDSDMEngineeringGovernance / Mgt

So…. what value does Scrum represent?

Scrum focuses on culture…Simplicity

CollaborationSelf-organising teams

Breaking down hierarchyA single voice to represent end-users

Minimising documentation

A belief that traditional project management practices stifle creativity, delivery and good software engineering

A desire that the opinions of software engineers are listened to

…a little narrowly

Culture changes

Eliminate false certaintyEmbrace transparency

CollaborationBring IT and Business together

Appropriate delegation & empowerment Minimise bureaucracy

Encourage team & organisational learning Personal mastery & discipline

Agile is part of and supports the broader change needed for high performing organisations

Core Assumption

“Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand”

Embedding Agile

Cultu

reEngineering

Governance / M

gt

Where do I start….?

Culture change Meta-methodology

Collaboration Requirements into User Stories Defining and automating tests

Deployment Scaling to Programmes and Portfolios

The Future of Project Management

Questions and Answers

This presentation was delivered at an APM event

To find out more about upcoming events please visit our website

www.apm.org.uk/events