How "AgilePM" and PRINCE2 were used in the same project

m: 44 7533 240 675; e: acdp@d-p-c.net; w: www.d-p-c.net
Project Challenge 2013
Presentation by Antony Della Porta
Copyright © 2013 della porta consulting Ltd. All Rights Reserved. PRINCE2® ® is a Registered Trade Mark of the Cabinet Office
The APMG Swirl Agile Project Management Device is a Trade Mark of APM Group Ltd.

Case Study on Using
AgilePM
in a
PRINCE2 Project
This presentation will be taking a look at a project where
“Agile Project Management” and PRINCE2 methods of
project delivery were successfully employed together. The
project was to delivery a new bandwidth usage protocol,
Quality of Service (QoS), configuration onto a Bank’s National
Network, to enable Application bandwidth prioritization for
the new Java-based applications project for the Retail Bank
Division Teller System
The purpose of this
Presentation
Agile Project Management and PRINCE2® In Projects

Presenter
Antony
C.
Della
Porta
• Antony has over 25 years experience of working in project
delivery, rescue and consultancy roles
• Major verticals such as Finance, Travel, Media and
Pharmaceuticals.
• Established trainer in delivering courses in Project
Management methodologies, and courses relevant to the
delivery and realisation of business strategy.
• Started using PRINCE2®, in earnest, over 14 years ago,
along with Agile Project management
• Fairly unique in having successfully managed and
implemented a number of PRINCE2® -AgilePM projects
prior to quite recently becoming a trainer.
• APMG accredited and member of Institute of Consultants

Introduction to Relationship between
PRINCE2 and AgilePM methodologies
• The following slide will show a graphic view of
the correlation of processes in PRINCE2 and
the Phases employed by Atern Agile Project
Management
• AgilePM established with PRINCE2
• Correlation of the Processes/Stages to
Phases/Increments
• Relationship of plans and lifecycles
Agile Project Management and
PRINCE2® In Projects

Process Overview of PRINCE2 and AgilePM
Key: AgilePM; PRINCE2®

The Project -
St. George Bank Network Upgrade
• Part of bank teller system replacement programme to employ Java based
applications
• Network to introduce QoS (Quality of Service) banding
– Gold for high demand applications (40% b/w)
– Silver for general demand applications (next 30%)
– Bronze – backoffice applications (20% b/w)
• QoS was a new concept indicating that the required solution to Prioritize traffic
would have to evolve
• Scope was two years old so requirements would have to be reviewed as well as
equipment
• Proof of Concept (PoC)facilities no longer available from the incoming Telco
(Optus) so alternative had to be sourced
• PoC was allocated one (1) month to complete defining, testing and piloting the
Gold, Silver and Bronze (as Coulds).
• Estimates for Effort would be broad as new functionality, and no known active
solution for this type of network

• Initial Project Start Up employing PRINCE2® as the primary methodology
• Stage 1- (P2) Initiating a Project used to setup and review Project in detail
• Stage 2 - (P2) Redefine current scope, Tenders for Integrators, Pre Project phase for Stage 3
• Stage 3 – (APM) Define and Develop requirements for technical solution, deploy 1st Pilot
• Stage 4 – (APM-P2) Refine Technical solution (Pilot feedback), 1st Pilot - Engage Integrator
• Stage 5 – (APM-P2) Refine Technical solution (Pilot feedback), 2nd Pilot - Plan National Roll-Out
• Stage 6 – (P2) First group of Retail Banks for Live Upgrade
• Stage 7 – (P2) Upgrade remaining 345 retail branches Nationwide
The Project Plan -

• Initial Project Start Up employing PRINCE2® as the primary methodology
• Stage 1- (P2) Initiating a Project used to setup and review Project in detail
• Stage 2 - (P2) Seek Integrators and Hardware requirements
SU and Stages 1-2 – PRINCE2 – High Level

SU and Stages 1-2 – PRINCE2 - Detail
• Starting Up a Project: document and sign-off Project Brief and
Approach - Use a hybrid of methodology using PRINCE2 and Agile
• Initiating a Project: Usual IP activities and preparing Stage 2 ,
planning the project to engage both delivery approaches: Agile
for the PoC and PRINCE2 for the main rollout and overall
Organisation and governance mapping for Roles and
Responsibilities
• Stage 2
o Review current scope (2 years old at this point)
o Define resource requirements (original Proof of Concept facilities no longer valid)
o Define Approach for PoC delivery (AgilePM) for Stage 3
o Plan Stage 3 - AgilePM Feasibility/Foundations and then move into first Development Phase
(Exploration and Engineering Timeboxes)

Stage 3 – AgilePM managed Increment (P2 stage) HighLevel
• Stage 3 – (APM) Define and Develop requirements for technical solution,
deploy 1st and 2nd Pilots to check initial design

Stage 3 – AgilePM Development Phase
• Use Feasibility/Foundations to define and prioritize the requirements to be delivered
over how many increments.
• Approach was to build the “Gold” application configuration requirements during the
1st increment and deploy into the 1st Pilot
• Feedback on the 1st Pilot (HeadOffice branch) was fed back to 2nd Timebox for further
refinement
• 2nd Pilot used for checking Telco configurations and hence full “Gold” function

• Agile: Refine Technical solution (Pilot feedback), 2nd Pilot
• PRINCE2: Engage Integrator, Preparations for Hardware builds and
configuration
Stage 4 – Joint AgilePM and PRINCE2

Stage 4 - PRINCE2 managed stage – AgilePM Develop solution
Agile:
• Refine Technical solution for Gold using Pilot feedback (1st Pilot)
• Commence development of configurations for Silver and Bronze
• Deploy Silver and Bronze solutions and commence 2nd Pilot
PRINCE2
• Engage Integrator
• Start planning the roll-out stages 6 and 7 with Integrator
• Define and order hardware requirements

Stage 5 - PRINCE2 managed stage – AgilePM - Develop solution
• AgilePM - Refine Technical solution (Pilot feedback), 2nd Pilot
• PRINCE2 - Plan National Roll-Out in detail

Stage 5 - PRINCE2 managed stage – AgilePM Develop solution
AgilePM
• Timeboxes under this Development Increment used to
• Refine Silver and Bronze applications
• Develop other requirements (including any dropped from earlier Timeboxes)
• Complete Pilot stage and sign-off developed solution now ready for
Deployment and hand back to PRINCE2
PRINCE2
• Finalize plans for 1st Stage roll-out in Stage 6
• Ensure resources in place and hardware (replacement network) preconfigured

Stages 6 and 7 - PRINCE2 managed stages: Main Project Roll-Out
• Stage 6 – (P2) First group of Retail Banks for Live Upgrade
• Stage 7 – (P2) Upgrade remaining 345 retail branches Nationwide

Stages 6 and 7 - PRINCE2 managed stages: Main Project Roll-Out
• Stage 6 - Upgrade the first 20 Branches spread nationally: 5 a night 4
Stage
6
Controlling
a Stage
Controlling
a Stage
nights
• Stage 7 – On successful completion of Stage 6 and sign-off, follow rest of
the Roll-out plan and upgrade the remaining 345 Nation-wide branches
• Post Project – Agile to monitor the success of the Bandwidth Prioritization
Post Project
MP
Work
Package
1
Stage
Boun
dary
MP
Work
Package
1
Closin
g
Project
Stage
7

Summary of Presentation
• PRINCE2 and Atern AgilePM can be used to deliver projects of
varying delivery requirements and needs
• Most projects are probably in reality managed this way
• There are some direct correlations between the processes/
phases of both methodologies
• Not necessary to marry these up directly, more important to
know and understand how each can be best employed for
each project
• This project was in 2003 to show the two approaches being
used together back then!

Contact Details for Presenter
Antony della Porta
Telephone: +44 7533 240 675
Email: acdp@d-p-c.net

How "AgilePM" and PRINCE2 were used in the same project

More Related Content

What's hot (20)

Similar to How "AgilePM" and PRINCE2 were used in the same project (20)

Recently uploaded (20)

How "AgilePM" and PRINCE2 were used in the same project