Implementation of an Agile Project Delivery Methodology – 7 Lessons

Date: 
Thursday, August 31, 2017
In 2014, Agile crossed the chasm and went mainstream after years of use in a predominately IT based community. In 2016, it became a buzzword associated with Digital Transformation as numerous organizations examined the benefits of failing fast in an effort to compete in our new digital enterprise. In 2017, while Agile may have become old news, the rate of adoption still varies by region and many organizations still wrestle with how to govern both traditional and Agile modes of operation within a single organization.


Pcubed was recently engaged to implement Agile into an organization’s existing solution delivery methodology within their overall project, program and portfolio management framework. The existing framework is a Mode 1 approach – or one heavily focused on a waterfall delivery.  The client, the Director of IT Assurance and Governance was looking for Pcubed to design a Mode 2 approach (mainly Agile) that could fit into, yet not replace their overall existing PPM structure.

As the engagement was initiated by the Governance function, the focus was on how Agile project delivery could be assured with control points in place, not something traditionally synonymous with an Agile approach.
 
Achieving an Optimal Bi-Modal Framework

Coined by Gartner, Bi-Modal is the practice of managing two separate modes of work: one focused on stable or predictable work i.e. Mode 1; while Mode 2 is focused on new innovations where failure, when learned from, is welcome.

There is an optimal bimodal envelope for each company. 

Pcubed began the project with an Agile Assessment or Program Diagnostic to understand the optimal bimodal approach for the organization rather than relying on market buzzwords to dictate which mode of operation was dominant.  In this case, our client wished for evolution not revolution.  Therefore, the Pcubed approach to the engagement was to produce an initial conceptual view of how the Agile framework might look within their existing structure.

As with any large Business Transformation project, a fundamental aspect of the project focused on Change Management.  The Pcubed team set up meetings with the key stakeholders to understand their current processes and documentation, and to gauge their level of awareness, desire and knowledge of Agile. In addition, the team wanted to judge their ability to successfully implement an Agile delivery approach. Subsequent workshops and presentations were then held to ensure that the stakeholders were involved and informed, and to provide an opportunity to obtain valuable input as the process developed.

This reinforcement completed the ADKAR Model.  This Agile Diagnostic process allowed the team to gain rapid insights into how Agile might be integrated to create a mixed environment where Mode 1 dominates.

An Agile Solution Delivery Methodology

With a general framework in place, Pcubed set out to review existing PPM processes, templates and artefacts. The review process involved modifying or replacing these as appropriate for the addition of the Agile Solution Delivery Methodology into the overall PPM structure.
There were a few key changes necessary to allow flexibility in mode operation for the organization.

  • Pcubed modified our Agile Assessment tool used during the diagnostic above, to provide an initial project assessment tool evaluating scope flexibility, collaboration levels, ease of communication, environmental conditions, suitability to incremental delivery and the team’s overall understanding of Agile; to determine whether a project was suitable for an Agile delivery or better suited to Waterfall.This assessment is now part of the Starting up a Project process (PRINCE2) for all new projects.
     

Solution Delivery Framework with Agile Components

 

  • Second, the introduction of a Sprint 0 stage, or ‘Discovery Sprint’ as depicted on the left on the graphic above, was developed to establish the high-level business requirements, solution design and test strategy, as well as plan the sprints before commencing the sprint cycles.Significant efficiencies were found by reducing the numerous design documents being used for waterfall projects, with one high level end-to-end Solution Design document for Agile projects.
  • Next the Pcubed team established an Increment Review process to enable assurance and ongoing alignment to standards and processes throughout the Project Sprint Cycles. 3 week sprints were agreed as a standard with the Increment Review being conducted after every 2 sprints.
  • Finally, the team revamped the Portfolio and Project level reporting to include Agile components like Cumulative Flow Diagrams and a Project Burnup Chart.  The result was an Agile Solution Delivery Methodology that complemented but did not supplant the client’s existing PPM structure.

 
The Seven Lessons

As with any large Business Transformation program there were a few lessons learned along the way. 

 
 

  1. Level set Agile knowledge and understanding of it across the organisation. The challenge with Government bodies wishing to enable control points is that this doesn’t always align with the true ‘Agilists’ in the organisation, whereas in this situation they were easily accommodated via the introduction of Increment Reviews.
     
  2. Documenting clear change control thresholds helps alleviate any change concerns by making clear the level of changes that could be managed within sprints and which type of changes were required to go through the standard change control process (i.e. impacting on time, cost or the minimum viable product).
     
  3. As always, good ‘hygiene’ is imperative. Putting Quality Data into the toolset, in this case, Team Foundation Server, allowed the team to execute effectively, extracting assurance and reporting needs behind the scenes.
     
  4. Reporting in a mixed delivery portfolio can be conflicting. Whilst traditional waterfall reporting is easily understood by external stakeholders and can be largely automated, to enable consistent portfolio reporting in a mixed delivery environment, the team needed to ensure that the required data points were in the Agile toolset.
     
  5. Involve IT Operations early and often, challenging the roadblocks they put in front of the change. In this case, the team moved from a pre-go live one-time dump of artefacts, to an approach where IT Operations could harvest the information as the project went through the various sprint cycles.
     
  6. Accurate estimating is a fine art that needs to be achieved to deliver an Agile project within planned velocity tolerances. The organization introduced story point estimating, yet required a few sprints for the process to “learn in” where teams were estimating near the level of accuracy of traditional projects.
     
  7. Don’t underestimate the importance of Change Management! Utilizing the ADKAR model, the team developed a process that fit within the organizational culture, ensured senior management support, and highlighted positive reinforcement, training, coaching and communications as keys to its success.

Successfully expediting delivery requires learning through “fast failure” and an iterative development approach with an engaged client. The Client went from no process to a bespoke defined Agile methodology in 6 weeks.  With the bi-modal framework in place, the organization was enabled to benefit from the flexibility, visibility and speed to market that delivering projects in an Agile way offers, while still ensuring that solid project delivery and a process framework were in place for resources to follow whether on an Agile or Traditional project.
 


Duncan Lamont is a Senior Project Management Consultant in our Sydney, Australia, office and is a qualified AgilePM (DSDM), SAFe Agilist and SAFe Program Consultant (SPC4). He has a broad knowledge and understanding of Agile practices as well as extensive experience managing projects and implementing project management methodologies for a range of organizations across industries in the UK, US, Asia and Australia.


For further information on this article and Pcubed, please email info@pcubed.com.