Skip to main content

The case for Project Management in Agile?

OK, I know how most of the Agile community feels about Project Managers:
Process over People
Meetings
Documentation

Urrgh...

But however you name the role (Agile Delivery, Scrum Master, Project Manager) and whoever does it  - someone needs to help the team to:

Plan
Track
Deliver
Communicate

Being a group of incredibly talented engineers does not give a team the right to ignore 3.5 of these.

All too often, engineers want to dive in to designing and building great software, but see planning as a hassle, tracking as a waste of time (or an abuse of their rights), communication as an alien concept and delivery (the fun bit) as something that will be done when it's done.

It may be popular to talk about being a 'self-organising team' and railing against any form of 'order' being imposed.  But why is that order being imposed?  Maybe it's to deal with the chaos that your s-o-t has failed to deal with so far.

As organisations scale and the senior leadership gets further and further from the day-to-day, they don't want to impose rules and process for the sake of it.  But a few months of teams being unable to commit to delivery estimates, flagging issues at the last moment, and generally being a black box from which unpleasant surprises regularly emerge - well, that forces the issue.

It's not an attempt to stifle your creativity, slow you down, or oppress you in the workplace.  It's an attempt to stay in business.

So when I say 'Project Management', I don't necessarily mean Project Managers.  Just someone in every team with a PM's mindset.

- Can we consistently plan and execute sprints/iterations in a highly dependable fashion?
- Are we laser focussed on our next milestone/release and delivering its benefits?  Are our stakeholders aware of what we're working on, why and when we're looking to be live?
- Are we on track? Are we managing expectations?  Are we feeding our learnings into longer term planning and communicating that early and often?

Any decent management team wants to manage by exception.  When things go wrong - and of course things always do - you'll be the team that is able to point out the impacts early, replan if needed, and make sure changes are communicated.   

The trust this will engender from any good leadership team should mean more freedom in your day to day. 



Comments

Post a Comment

Popular posts from this blog

Continuous (Self) Improvement

“Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy Introduction: Most people talk a great game about continuous improvement.  And as a group, most of us truly agree with and see the benefits of, the concept as applied to our projects and teams. Sprint Retrospectives, Post Implementation Reviews, 5S, DMAIC, PDSA (not the dog people) and so on. But... Do you practice it personally ?  I don't mean training courses, formal development plans and all the other bureaucracy that people step through stoically every year in a bid to get a pay rise.  I'm referring to the small (but meaningful) improvements we can make every day. Or to work in an Agile principle: "At regular intervals, the team (of one in this case) reflects on how  to become more effective, then tunes and adjusts  its behavior accordingly." Step 1: Feedback (aka input to the CI process): Of course, all improvements need to be identified i...
Post a Comment
Read more

Definition of Done - An example

Done? To call a story 'Done-Done' we should refer to two things: the acceptance criteria for each story the team’s Definition of Done The DoD is defined by the team and should be updated whenever it seems appropriate e.g if there's a big change in the team or the work; or the team simply sees the need for a change. If you have project based teams, it's something to agree before timebox 1 kicks off. If you're more product based and continuously working through an ever growing backlog, slot it into a timebox kick-off, a retro (if that's where it was discussed) or just grab 10 minutes after the daily stand-up. An Example: Here's a basic example created by a team I was working with: ---------------------------------------------------------- A. Dev done ---- Code review done ---- Unit Tests written and passing ---- Integration tests written and passing B. Test complete ---- Manual Testing complete – Acceptance Met ---- Automation Tests written and ...
Post a Comment
Read more

Agile Armchair Generals

If you're an Agile practitioner of any sort you will understand what I mean by Armchair Generals (if not, it may be an idea to check if you are one..). Apropos of nothing an email arrives that questions the management of your project in terms of whether it is properly 'Agile'. Feedback is, of course, a great tool.  But it must always be understood within the context of the person providing it. So when the email lands questioning the type of contingency you've built into your project or the depth of analysis performed on your requirements set, ask yourself: 1. Has the questioner spotted something you and the team have missed? It happens.  That's why independent reviews can be helpful. 2. Has the questioner misunderstood something about your project?  If so, maybe your communications weren't quite clear enough or they've missed something - it happens, we're all busy. If the questioner has understood the topic correctly and is simply disagreeing ...
Post a Comment
Read more