Over many years I have come across numerous examples of both successful and unsuccessful project management implementations.
Whether it was based on a PMBoK, APM or PRINCE2 method made no difference, they quietly thrived or noisily failed. The answer for a higher implementation success rate seems to elude many, in spite of all the conferences attended.
Along comes Agile with all its flavours, into the mainstream of change management for IT as well as many other project genres.
So will we do a better job of implementing agile ways of working, and actually get our strategic and operational changes implemented effectively?
Well so far it appears that the answer is no, with some exceptions. A wave of Agile implementations is taking place across all types of companies, started with enthusiasm, only to end up in a thrashing muddle of disjointed techniques, confusing terminology, blurred roles and baffled customers and stakeholders.
To me the primary, single problem from which all other failure points derive, is a lack of a single senior manager stepping up and taking ownership of his or her company’s Agile implementation.
Without this leadership the root causes of Agile implementation failure kick in, and I’ve explained a few of these below. Before I get to them, let me share an acid test you can use to assess if your Agile implementation is going be a winner, It’s one question; Are you implementing your Agile way of working using a Waterfall or an Agile approach?
Ok, so you’ve just stopped your Agile transformation project and need to see a few root causes of implementation. Let’s start with some Principles from DSDM’s™* Agile Programme Management.
*DSDM™ DSDM is a leading Agile approach, looked after by the Dynamic Systems Development Method.
Principle – Agile programmes are iterative
Agile promotes iterative and incremental development for a number of reasons, one of which is because the detail of the final result is not known, often due to a lack of understanding of the journey and how we will be able to apply the new technology or approach, in this case, how will Agile work for us, given that we have never applied it before? So surely implement this complex organisational change in small testable increments, learning, adjusting and improving as you go. This will reduce the risk of applying a completely new way of working. So no waterfall, select the right Agile approach to start with, and led by a senior management champion to get everyone thinking without invoking their cognitive bias’s**.
**Cognitive bias: a pattern of deviation from rationality in judgment, whereby inferences about other people and situations may be drawn in an illogical fashion. Individuals create their own “subjective social reality” from their perception of the input.
Principle – Benefits are realised incrementally and as early as possible. (Or “starting with the end in mind”, if I take a note from Steve Jenner’s Benefits Management approach).
A large company, one of many, has just “finished” an organisation wide implementation of Agile, using up vast amounts employee production time and funding, only to find, after a far too long waterfall cycle that the Agile way of working is not functional or practical. In fact, they started with the wrong Agile model to begin with.
So imagine if an executive had insisted that before millions were spent, some real benefits needed to be proved early in the initiative. This executive would also ask that the ultimate vision of the Agile implementation would be describable and coherent, clear in what the measurable benefits would be and could be realistically achieved. Yes, whilst you do not do much detailed planning in Agile, you must have an excellent thoughtfully crafted vison to set direction to all stakeholders that leads to real benefits to ensure ongoing commitment.
So much for ignoring some key principles, let’s look at just one key driver from the Agile Alliances’ Manifesto. It’s called “Customer Collaboration”.
It’s mandatory for Agile to work closely with the customer. But on the whole left out because it’s so difficult, and culturally different to the common current silo’ed way of working from behind PC screens. But only your customer can tell you what they want, and just like you, they probably won’t get it right the first time and they’ll change their minds. It’s hard at first, but with some new skills (like workshop facilitation) it makes team work fulfilling and ultimately far more successful.
Now, you’re the Agile implementation executive, think who are your customers that you have to work so closely with to get Agile thinking in place across the organization? That many hey!
Making the right choice for your personal career or business!
At some point in your career, as with most people, you will reach point when you start asking yourself how you can develop your skills and best demonstrate your ability to a potential employer. Having formal certifications is an excellent way to do this and putting yourself ahead in the recruitment process remain imperative if you are looking to climb the career ladder.
Snap Tech offers a variety of approaches to Agile working:
Scrum is a process cutting through complexity to focus on building software that meets business needs in order to, incrementally and empirically, deliver working software. According to Scrum it provides a simple framework for team collaboration on complex software projects (even though the concept of a project or project lifecycle is not recognized. It does not recognize the traditional role of ‘project manager’, there is no ‘project board’, you don’t have ‘stage boundaries’, there is a move away from project documentation such as a business case, a project plan, work packages and product descriptions. Essentially it provides for an ‘empowered’ team able to make decisions and create what the business desires. It remains very popular amongst the agile fraternity.
The remaining dilemma is that many organizations have to and want to remain to be seen as having proper governance and control in place. They have embedded for example PRINCE2®, never fully understanding how to or tapping on its ability to be tailored to be agile, whilst retaining the governance so desperately needed. As a result of this lack of understanding and based on the need of organizations for governance AgilePM (Agile Project Management) became a viable option. AgilePM retains the idea of projects, project managers, project steering groups, stages (increments), business cases and pre-project work. In addition, AgilePM provides a number of documents that can be used if needed. A natural flow from AgilePM became AgilePgM™ (Agile Programme Management) placing more emphasis on incremental delivery and recognizes that the programme (including potential incremental deliveries, projects and change initiatives) will evolve over time and cannot be defined up front. Whilst a roadmap to the future can be created, only the relatively immediate future state can be defined in any detail.
More recently PRINCE2 Agile, providing a way of blending agile with PRINCE2 saw the light of day helping individuals and businesses that have already embedded PRINCE2 as their preferred project management method with its solid provision for governance. PRINCE2 Agile shows you how you can get the best of both worlds; introducing the use of agile concepts and practices, demonstrating how you can blend them into the structure of a PRINCE2 environment.
What qualification should you then choose?
PRINCE2 still remain a key certification demanded by many organizations. Agile, is however gaining more momentum and if you want to remain ahead of the pack some certification in agile is becoming the course of choice for prospective employers in certain circumstances. There is increasing evidence and experience from professionals in the project management industry to suggest that the two methodologies do not necessarily clash and can be moulded in to a hybrid methodology depending on the situation.
A natural decision would be for organizations and individuals already embedding PRINCE2 to go the PRINCE2 Agile route as this immediately helps you to bring both of these capabilities together under one umbrella.
AgilePM provides for an independent project management lifecycle incorporating an agile solution development cycle into one. It brings with it also the aligned AgilePgM that gives organisations an agile programme management capability.
In conclusion the fact remains mastering multiple approaches to PM approaches be it more traditional or agile allows for recognition of expertise and enables better decision making within organisations and provides for better career prospects.
About the Author
Guy Eastoe is a thought leader and an APMG accredited consultant specialising in portfolio, programme, change and benefits management. He has been consulting and training in this space forever.