www.dsdm.org

Scaling Agile

Steve Messenger

Chairman DSDM Consortium

www.dsdm.org

Agile works

2

• Small multi-functional team

• Work together

• Easily Communicate

• Empowered

• Focused on outcome

• Iterative and incremental approach

• Business closely and continuously involved

• Good product results

www.dsdm.org

Complexity

3

• Part of a bigger whole

• Value against other initiatives

• Many more activities have to be done

• Business Processes

• Infrastructure

• Location

• Benefits realisation

www.dsdm.org

Scaling in Nature

3

www.dsdm.org

Scaling in Nature

3

www.dsdm.org

Scaling

3

www.dsdm.org

Scaling

3

• Design and Architecture

• Vision and Planning

• Governance and culture

• Communication

www.dsdm.org

Design and Architecture

2

• Enough up-front design

• Desired business structure

• TOPI

• Everyone knows where they are

• Flexible

• Evolves, with the agreement of all stakeholders

www.dsdm.org

Design and Architecture

2

• System Architecture Definition Produced in Project Foundations and evolves through project

• For large, transformational programmes, Business Architecture Model produced in Programme Foundations

www.dsdm.org

Vision and Planning

2

• Everyone understands purpose and business opportunities

• Informed decisions that move towards to vision

• What is important / has to be done before something else?

• How can incremental benefit be achieved?

www.dsdm.org

Vision and Planning

2

• Business Vision, Business Case and Delivery Plan produced in Project Foundations

• For large transformational programmes, Business Vision, Business Case, Benefits Realisation Plan and Roadmap produced in Programme Foundations

www.dsdm.org

Governance and Culture

2

• Clear governance strategy

• Understand business priorities

• Give up projects for greater good

• Decisions at lowest possible level

• Prioritise benefits

• Prioritise requirements

• Fast and efficient

www.dsdm.org

Gated Review Processes

Typical Gates

1. Permission to investigate an idea

2. Permission to build a Business Case

3. Business Case approval – go ahead

4. Permission to test deliverables

5. Permission to deliver

6. Project closure

7www.dsdm.org

www.dsdm.orgwww.dsdm.org

Scaling to Programmes

4

www.dsdm.org

Communication

2

• Teams take responsibility

• Provide Information

• Get Information

• See Potential Problems

• Leaders Facilitate

• Understand Each Team

• See Potential Problems

• Facilitate Conversations

www.dsdm.org

Roles incorporating SCRUM

www.dsdm.org

www.dsdm.orgwww.dsdm.org

www.dsdm.org

Summary

4

• Scaling Agile is possible – but not how we think

• Learn from natural world

• The four themes

• Design and Architecture

• Vision and Planning

• Governance and Culture

• Communication

This presentation was delivered at an APM event

To find out more about upcoming events please visit

our website www.apm.org.uk/events