Software Engineering, Project Management, and Effectiveness
I was looking for some of my old job descriptions for PM positions in patterns & practices to help out a colleague. While I didn’t find them, I did find some of the questions that I have used to evaluate PM effectiveness:
JD - great set of soft metrics! Do you have an insight on how you can measure PM effectiveness on an agile team? Given that most often PMs perform the roles of product owner and scrum master and the spec delivery is not as detailed as that in traditional models, it would be interesting to hear your take on how you evaluate performance in these situations.
@ Anu -- Good question. Here are some key shifts for a traditional PM moving to an agile team:
- less specs, more user/tech stories
- less documenting, more doing
- less big-up-front-design, more spiking/testing
- less top down, more team empowerment
- the doers of the work, estimate the work
- less fixed-scope and it's done-when-it's-done, more fixed-time and flex scope
- less customer hypotheses, more customer validation
- less big-bang, more flow as you go
With that in mind, some key capabilities are:
- ability to show velocity / progress?
- ability to chunk down and ship value along the path?
- ability to capture/share requirements in the form of stories?
- ability to respond to changing plans?
These are just some quick ideas to get you thinking.