After reading 'The True Role of a PM on Agile Projects' from Mike Griffiths - I started to think about what a PM does (at least from my experience) and (of course) put a mind map together (above) - first draft. If you click on it, you'll see the detail. I'm sure I'm missing about 25% of the activities - and it's focused on software development (most of it could be applied in other efforts...). So, where I am a very big proponent of Agile, I have some doubt about the limited list provided in the article.
Hi Meade,
ReplyDeleteThanks for your comments, my post was intended to outline core roles and principles to focus on and is missing a whole host of activities that need to occur.
I like your mind map of tasks, but again this is incomplete also, for instance I see no reference to Quality. (e.g. monitoring Quality, QA planning etc.) The same goes for sub-contractor management and elements of estimation.
Another trouble with trying to generate exhaustive lists is that many of these roles are domain specific, so to keep it applicable I stuck to a high level. However, I could have done a better job of explaining that this is by no means a complete list.
Best regards
Mike