By Michael Connolly
If you lead a PMO or are a PM and your organization is embarking on an Agile adoption you are probably thinking so how do I fit into this new paradigm and still manage the work that I’m currently managing (it won’t manage itself is what you are thinking) ?
Organizations who are now moving towards Agile as a product delivery/SDLC method will find themselves trying to figure out where their PMO and subsequent Project Managers will fit.
The problems they face are several:
Traditional Project Managers:
- Are experienced at managing to a specific plan and resolving resource issues that their specific projects are facing. They are not typically assigned to just one project and the people they work with come and go with much frequency. Project Managers have been for many years the ones who provide confidence that ’someone’ has their hands on the pulse of the projects that are designed to deliver value to the organization.
- Don’t typically look at their projects as value driven, rather they are priority and resource driven. Their focus when they are assigned to a project is about who is on my team, who can I steal from other projects and creating a plan that is often not vetted by the very people who will actually do the work and socializing that with Sr Management.
- Traditional Project Managers are excellent deflectors of blame (yep I learned quickly how to push off issues on to someone else)
- Are not typically contributing members of the team.
I don’t say these things to make Project Managers angry, I was once a PM and a very good one at that (or so I believe). And I’m not at all implying that there isn’t a role for PM’s in Agile, but I will suggest that how you think as a PM will need to change.
For starters you need to find a way to be a contributing member of the team and not just someone who sits on the sidelines like a reporter and records what is going on to report out.
The thing that was different about me was that I always managed my teams more like a Scrum Master would. I found ways to contribute, I gained the trust of my team, I protected them and provided guidance for individuals when they were struggling with something about the organization that didn’t make sense. This process of engagement led me out of the PM role and ultimately into QA Management so there are growth opportunities for PM’s if you are open to learning new things.
If the team needs help in testing, learn something new and help out.
Most Agilists’ may tell you that the Scrum Master and Project Manager role are completely different. Though they are different I would argue that project managers can fill the void of Scrum Master and gain great insight to their projects and be on point to resolve impediments more easily than be bystanders to the entire Agile process.
Here are some key areas that Project Managers should focus on during an Agile Transformation:
- Planning – Is not a function of setting forth an unyielding plan. Rather planning by the team is to facilitate an ever growing understanding of what the team is building. Big Up Front Requirements convey a static nature to projects that simply doesn’t exist. If you disagree actually track the number of times the team has to change their plans (for architecture, etc..) during a typical non-Agile project. Teams that try to predict the future are destined to be wrong a majority of the time. You need to become comfortable with a plan that identifies in detail only 4 weeks.
- Goal – Be an active member of the team and be able to understand both the technical issues that are facing the team and bring them a clear understanding of dependencies with projects and teams that aren’t in their viewfinder.
- Goal – Learn different Agile planning techniques. One of the key things that people miss in Agile adoption is that Planning needs to take place more often and that some level of upfront Discovery is not a bad thing.
- Scrum/Agile Activities – A Project Manager for a Scrum Team needs to:
- Ensure that their teams are performing effective User Story development with techniques such as BDD and Specification by Example.
- Ensure that their teams have a well groomed set of stories in their backlog
- Ensure that their teams have effective Sprint Planning and Estimation sessions
- Ensure that the teams utilize their Retrospectives to drive continuous improvement
- Goal – Become an Agile Evangelist, learn everything you can about Scrum, Story writing, TDD, Continuous Integration, User Story Mapping, BDD, Specification by Example.
- Program Management – Is driven by the overall roadmap. Ensuring that Scrum teams are aligning their user stories to appropriate RMI’s keeps the organization focused on execution progress/success and provides the PMO with a clear view to all of the work that they are managing. As an organization scales this is no small feat, so getting large sets of teams to keep up with story writing and roadmap linking is an administrative task that teams quickly tire of. Project Managers need to provide support and assistance with the management of these types of activities in conjunction with their PO and Scrum Master.
- Technical Knowledge – Though this isn’t as big of a problem as it was 10 years ago, many Project Managers simply don’t understand the underlying technical platform that their teams are working in. I personally don’t think that you can be an effective project manager unless you have this knowledge. Take the time to learn, your team will appreciate it and you will be able to have better fact based conversations with your Stakeholders regarding issues that delay delivery of projects.
Michael Connolly has been working in Software Development for over 20 years, over ten of those working with organizations (some are Fortune 25 organizations) and teams who are either trying to ‘become’ Agile or are already Agile.
Article source: http://www.pmhut.com/pmo-role-in-agile
Powered by Facebook Comments