While cleaning out my office in preparation for my big move to California, I ran across my Agile Program Manager “cheat sheet.” I had to laugh because as I reviewed the document, i thought to myself “This makes so much sense. How did i never get this before?”
When I first joined CodePlex, I was going out of my mind insane trying to figure out what my daily PM responsibilities were. So, in typical Sara Ford-like fashion, I told Jim Newkirk we weren’t going to end our 1-1 weekly meeting until he had outlined what was expected of me as a PM each step of the way in an agile development cycle.
3 hours later, I left Jim’s office with this document.
How Agile Works
Each number represents an iteration, which is a week of work. I1, I2, and I3 are the development iterations. The majority of a Program Manager’s time is spent in the pre-I1 iterations, named –3, –2, and –1.
The Epic Story – This is what goes on a sticky note on the whiteboard. For example, “Ratings and Reviews for Project releases” is an epic story with the following stories associated with it.
Pre-Iteration Planning Meeting (IPM) Planning (about 10 weeks out from deployment date)
These are the series of Program Manager tasks that need to be completed in this order:
Iteration Planning Meeting (IPM)