steve messenger, dsdm consortium
DESCRIPTION
An agile programme to restructure a companyTRANSCRIPT
www.dsdm.org
Separation
Steve Messenger
Chairman DSDM Consortium
www.dsdm.org
Agenda
The Business Transformation The Approach Using DSDM
Foundations and Teams Exploration and Engineering Deployment
Summary
2www.dsdm.org
www.dsdm.org
History of DSDM
• Evolved from RAD
• Created Collaboratively by practitioners for practitioners
• DSDM Consortium not for Profit
• Agile Manifesto Founder
• 1995 DSDM V1• 2003 DSDM V4.2• 2007 DSDM Atern• 2011 Agile PM• 2014 – DSDM Agile
Project Framework
3www.dsdm.org
www.dsdm.org
• Agile PM Certified Trainer• Chairman, DSDM Consortium• DSDM Advanced Practitioner• DSDM Certified Trainer• DSDM Certified Examiner• Agile Foundation certified examiner• Agile Advanced Practitioner Certified Examiner• Training, Coaching and Consultancy• DSDM Early Adopter – Boston Globe
4www.dsdm.org
Steve Messenger
www.dsdm.org
Steve Messenger
• Director, Herald Associates Limited• Over 30 years experience in Software, IT and Project
Management• PRINCE 2 accredited• Industries worked in
– Pharmaceutical– Newspaper– Control Systems– Insurance (Lloyds of London)– Local Government– Hydrographic – Electronic Sea Charts
5www.dsdm.org
www.dsdm.org
The Business Transformation
2
• Pharmaceutical Company
• Organisation already had number of separate companies
• Structure not meeting current business requirements
• Re-structure organisation into new company model
www.dsdm.org
Complexity
3
• Affected all aspects of organisation:
• Legal; Finance; IT; Supply Chain; HR; Procurement; Sales
• Short timescale for delivery
• Solution unclear
• Needed to consider
• All Business Processes
• All locations
• The company organisation
• Information
www.dsdm.org
Decided to Use DSDM
2
• Feasibility / Foundations to set the basis for the programme
• Overall Business Design
• Roles and Responsibilities
• Evolutionary Development to carry out the changes required
• Technical
• Process
• Organisational
• Informational
www.dsdm.org
Foundations
2
• Created the Vision so everyone understood the purpose and business imperatives
• Determined key areas to be involved
• Supply Chain; Finance; Legal / Tax; HR; IT
• Through a series of workshops, iterated through the best business design to meet the separation requirements
• Determined High – Level Changes required
• Planned, including risks, early benefits
www.dsdm.org
Foundations – Project Organisation
2
www.dsdm.org
Foundations - Teams
2
Legal Team
Finance Team
IT – ERP Team
Supply Chain Team
HR Team
IT – Other
International Finance and Tax
Head of Finance
Me
Legal
www.dsdm.org
Evolutionary Development
2
• Each team had major objective(s)
• Iterated to determine best solution in their area
• Understood level of empowerment
• Understood interfaces and dependencies
• Cross – team integration
• Team daily stand ups
• Cross team weekly stand ups
• Electronic project room
Legal Team
Finance Team
IT – ERP Team
Supply Chain Team
HR Team
IT – Other
www.dsdm.org
Deployment
2
• Many IT changes to ERP could be deployed early
• Similarly other IT systems
• New T’s and C’s for Employees
• New stationery
• Company Set Ups
• Information prepared
• Full switch over
• September not January
• Bedded in by January
Legal Team
Finance Team
IT – ERP Team
Supply Chain Team
HR Team
IT – Other
www.dsdm.org
Agile Programme Management
www.dsdm.org
Summary
4
• DSDM worked well on large, complex project
• Small teams around a central business model / architecture
• Iterating to best solution
• Good Communication
• Good Leadership
• Well defined vision
• Beware Legal!
www.dsdm.org
Questions?
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