Share this
Take a learning journey to agile project management
by Carl Weller on 24 April 2015
Most of my career as a “planful” project manager - by that I mean a devotee of PMI and PRINCE2 (yep, I’ve said it and I’m not ashamed of it) – I’ve heard metaphors like “herding cats” or “getting your ducks in a row” being used to describe the business of delivering value to clients. I’ve even used them on occasion.
Looking back, perhaps with a little more understanding, statements like those above are full of subtle meaning; an assumption that the “cats” needed “herding”, and a belief that the problem we were solving was simple enough that all I needed to do was “line up some ducks” (by which I mean create a work breakdown structure and implement a plan).
I like causality, the feeling that I can analyse a situation and come up with a plan. It makes the world feel safer and more ordered. Like many others, I’ve seen the “Agile gap” (aligning adaptive Agile development practices with quite prescriptive Newtonian organisational frameworks) and quite happily sat on my own side of the canyon (for years in fact), expecting agilists to close the gap from their side. In some ways I guess I found early Agile development very challenging to my world view.
Moving on a few years, with a few more scars on my back, I’ve been lucky to be exposed to some deep thinkers, many of them at Equinox IT. I am now gingerly straddling the fence between predictive, planful project management and Agile project management, using adaptive practices. Some I am very comfortable with, others I just need to plug into my frame of reference.
The most significant shift in mindset for me has been acknowledging that the work of software development is complicated, but the added dimension of people and politics found on projects - and in organisations - can make software development very complex. For those of you with a knowledge of the Cynefin framework, or Eddie Obeng’s 4 project types, the meaning is clear; some of our tools are more suited to industrial management in the style of F.W. Taylor than they are for 21st Century knowledge work.
For some work, where the objectives are clear, and the methods well-understood, perhaps it is just a case of lining up a few ducks (or “painting by numbers” according to Obeng). In these cases I’d feel comfortable sticking to a traditional planful project management.
But most of our work isn’t like that anymore. The pace of change is such that value needs to be delivered faster, with better predictability, and the best methods I have seen to do that are those that embrace change as a constant rather than something to be controlled. The people I am “leading” are generally smarter and better informed than I am, and they can generally work out better approaches to deliver value than I can, but they don’t have all the answers either – at least not well in advance as is required in a waterfall approach.
Keeping the cogs aligned to a very detailed plan over time, as the environment changes, requirements change, people move on and off the project, or try and split themselves across multiple projects, becomes harder and harder. You can spend too much time discussing if something is a change or a defect, or updating a Gantt chart, when you could be helping focus on continuous improvement and removing obstacles in the team’s way. An Agile project management approach is much better suited to these situations.
So am I now some sort of convert, suitably equipped with missionary zeal? No, I’m just someone on a learning journey who has found some more tools that work in some situations, and could be adapted for others. But I’m not sitting smugly on my side of the canyon anymore either. I now see a product backlog as just another form of work breakdown structure, and release and sprint planning as a mixture of a continuously evolving schedule and a change control process. If you get past the shape of the tools and think about their purpose, the fit becomes clear. I no longer make misinformed statements like “there’s no such thing as Agile HR management”. In one sense there isn’t, but the practices I’ve seen for building and enabling self-managing teams, using an Agile project management approach, are amazing and would fit just as well in a policy shop (Jurgen Appelo is a must read for managers of all teams, not just software teams).
And if I put my PMI hat back on, there have been concepts like “progressive elaboration” and “rolling wave planning” since the early to mid 2000s (PMBOK 2 and 3 respectively). These are all about iterative planning and planning in detail in the near-term and less granular further out. Unfortunately they are often overlooked and under-used.
The concept of the project plan as a “contract” has been taken too far. It diminishes the complexity of the work we do and sets up adversarial rather than collaborative relationships when the project plan gets “challenged” by reality. What Agile - be it Scrum or Kanban – does is make the process and the conversation easier. Starting an Agile development project means you acknowledge that you don’t know exactly what the future holds, but you agree to work through it together to find that best mix of time, cost and scope that delivers value (By the way, never start an agile project if you don’t have this acknowledgment from the business!).
Carl Weller is a Principal Consultant specialising in Project Management and Agile Leadership, based in our Wellington office.
Share this
- Agile Development (153)
- Software Development (126)
- Agile (76)
- Scrum (66)
- Application Lifecycle Management (50)
- Capability Development (47)
- Business Analysis (46)
- DevOps (43)
- IT Professional (42)
- Equinox IT News (41)
- Agile Transformation (38)
- IT Consulting (38)
- Knowledge Sharing (36)
- Lean Software Development (35)
- Requirements (35)
- Strategic Planning (35)
- Solution Architecture (34)
- Digital Disruption (32)
- IT Project (31)
- International Leaders (31)
- Digital Transformation (26)
- Project Management (26)
- Cloud (25)
- Azure DevOps (23)
- Coaching (23)
- IT Governance (23)
- System Performance (23)
- Change Management (20)
- Innovation (20)
- MIT Sloan CISR (15)
- Client Briefing Events (13)
- Architecture (12)
- Working from Home (12)
- IT Services (10)
- Data Visualisation (9)
- Kanban (9)
- People (9)
- Business Architecture (8)
- Communities of Practice (8)
- Continuous Integration (7)
- Business Case (4)
- Enterprise Analysis (4)
- Angular UIs (3)
- Business Rules (3)
- Java Development (3)
- Lean Startup (3)
- Satir Change Model (3)
- API (2)
- Automation (2)
- GitHub (2)
- Scaling (2)
- Toggles (2)
- .Net Core (1)
- Diversity (1)
- Security (1)
- Testing (1)
- February 2024 (3)
- January 2024 (1)
- September 2023 (2)
- July 2023 (3)
- August 2022 (4)
- August 2021 (1)
- July 2021 (1)
- June 2021 (1)
- May 2021 (1)
- March 2021 (1)
- February 2021 (2)
- November 2020 (2)
- September 2020 (1)
- July 2020 (1)
- June 2020 (3)
- May 2020 (3)
- April 2020 (2)
- March 2020 (8)
- February 2020 (1)
- November 2019 (1)
- August 2019 (1)
- July 2019 (2)
- June 2019 (2)
- April 2019 (3)
- March 2019 (2)
- February 2019 (1)
- December 2018 (3)
- November 2018 (3)
- October 2018 (3)
- September 2018 (1)
- August 2018 (4)
- July 2018 (5)
- June 2018 (1)
- May 2018 (1)
- April 2018 (5)
- March 2018 (3)
- February 2018 (2)
- January 2018 (2)
- December 2017 (2)
- November 2017 (3)
- October 2017 (4)
- September 2017 (5)
- August 2017 (3)
- July 2017 (3)
- June 2017 (1)
- May 2017 (1)
- March 2017 (1)
- February 2017 (3)
- January 2017 (1)
- November 2016 (1)
- October 2016 (6)
- September 2016 (1)
- August 2016 (5)
- July 2016 (3)
- June 2016 (4)
- May 2016 (7)
- April 2016 (13)
- March 2016 (8)
- February 2016 (8)
- January 2016 (7)
- December 2015 (9)
- November 2015 (12)
- October 2015 (4)
- September 2015 (2)
- August 2015 (3)
- July 2015 (8)
- June 2015 (7)
- April 2015 (2)
- March 2015 (3)
- February 2015 (2)
- December 2014 (4)
- September 2014 (2)
- July 2014 (1)
- June 2014 (2)
- May 2014 (9)
- April 2014 (1)
- March 2014 (2)
- February 2014 (2)
- December 2013 (1)
- November 2013 (2)
- October 2013 (3)
- September 2013 (2)
- August 2013 (6)
- July 2013 (2)
- June 2013 (1)
- May 2013 (4)
- April 2013 (5)
- March 2013 (2)
- February 2013 (2)
- January 2013 (2)
- December 2012 (1)
- November 2012 (1)
- October 2012 (2)
- September 2012 (3)
- August 2012 (3)
- July 2012 (3)
- June 2012 (1)
- May 2012 (1)
- April 2012 (1)
- February 2012 (1)
- December 2011 (4)
- November 2011 (2)
- October 2011 (2)
- September 2011 (4)
- August 2011 (2)
- July 2011 (3)
- June 2011 (4)
- May 2011 (2)
- April 2011 (2)
- March 2011 (3)
- February 2011 (1)
- January 2011 (4)
- December 2010 (2)
- November 2010 (3)
- October 2010 (1)
- September 2010 (1)
- May 2010 (1)
- February 2010 (1)
- July 2009 (1)
- April 2009 (1)
- October 2008 (1)