PMI Agile Community of Practice Webinar: Introduction to Agile Planning and Project Management
Just and FYI for you guys. This Monday (August 22nd, 12:oo EDT) I’m doing a reprise of my Agile2011 talk “Introduction to Agile Planning and Project Management” for the PMI Community of Practice. If you are a PMI member and want to check me out live… you can get more information on the webinar at the PMI website.
Introduction to Agile Project Planning and Project Management
If you aren’t a member of PMI… stay tuned to LeadingAgile. I am going to do shortened YouTube versions of both my Agile2011 talks over the next few weeks.
Agile introduces a number of tools and techniques designed to help the team figure out how much software we can build for the time we have, and the amount of money our customer is willing to spend. This talk will introduce the fundamental concepts necessary to break down and estimate our product backlog, how to organize delivery of that backlog for early risk reduction and rapid customer feedback, and how to get stable throughput and predictability as you mature your agile practices. This talk is for those looking to understand how (and why) agile methods lead to better business outcomes.
I attended the 2011 webinar and took notes. Now I am working as a Project Manager on an “Agile” Project and I find that the contents of this presentation are still very timely. I refer to my notes quite often and I finally found a copy of the PowerPoint slides here.
The design of the latest Team Foundation Server, the Application Lifecycle Management (ALM) tool from Microsoft (Visual Studio 2013), follows the thinking behind the slides on Enterprise Project Management (EPM) that come in the later part of the presentation.
Your slides breakdown the concept of an Epic, a Feature and a User story as clearly as one would ever desire and show how each would fit into the development workflow. Luckily, for those who use Team Foundation Server, the workflows you illustrate on these slides can also be replicated on the tool (The task board and the customizable Kanban, which are part of TFS).
On our current project we did not adhere strictly to the SCRUM framework and we have already identified the disadvantage. For future releases, I want to suggest to my team to follow the strict breakdown of requirements into EPIC, feature and user stories the way you have it here along with the workflow described.
Thank you for a wonderful excursion into the world of Agile Planning.