“We don’t need no stinkin’ project manager!” That’s the phrase I hear sometimes from software developers. They view project managers as getting in the way and serving as “glorified secretaries” (no offense to those hard-working administrative assistants out there).
Generally, I respond by educating them on the typical benefits of a good project manager, such as the following 10 frequently cited benefits:
1.Clarifying goals
2.Resolving barriers and issues
3.Managing stakeholder expectations and needs
4.Managing the schedule and budget
5.Ensuring clear requirements
6.Anticipating and managing risks
7.Managing scope changes
8.Communicating milestones and status
9.Making presentations
10. Being accountable and facilitating the overall project direction
When it comes to traditional projects, certainly an effective project manager who does these things well clearly adds value in improving predictability, perception and the likelihood of success. But can the same be said for agile projects? Or is there a different set of skills and/or roles needed?