One of the most exciting news that came out during the last year was the release of Microsoft Planner. The tool provides a web-based interface and allows users to manage tasks right in the browser, completely independent of other tools like SharePoint or MS Project. Having spent a great share of my career in project management and being an avid follower of Agile methodology (I utilize Agile principles when I configure SharePoint sites for my clients), I believe that Microsoft Planner is a game changer for Agile projects. With his post, I would like to explain how you can use Microsoft Planner for Agile and specifically SCRUM projects, with a very little upfront setup.
What is Microsoft Planner?
Up until recently, for those of us working in the SharePoint environment, the tools of choice for task management were Task Web Part or Project Online/Project Server (Microsoft’s PPM solution). Unlike the two choices above, Microsoft Planner provides an unorthodox way to manage projects. No task dependencies or complicated project schedules and no upfront setup or configuration. Instead – a very simple and intuitive interface. I have published a very detailed post on Planner and its features just recently. You can access it here.
Using Planner for Agile and SCRUM
Historically, SharePoint had a Tasks web part available for task management. Despite some pretty robust features, it made the most sense just for Waterfall (phased/sequential) projects and was not compatible with the Agile ones. By the way, you can read a comparison of Planner vs. Tasks Web part here.
The newly released Microsoft Planner is a total game changer and in my opinion is a perfect fit for Agile/Scrum projects. Below I would like to highlight the different areas of Planner as they relate to SCRUM artifacts and explain to you how you can configure Planner to accommodate Scrum Projects.
The sprint backlog is essentially a list of tasks from the product backlog which will be completed in the particular sprint. Sprint backlog can be captured via Buckets in Planner. Essentially, you would name your Planner buckets as Sprint 1, Sprint 2, Sprint 3, etc. and add tasks to each of the Sprints (buckets) accordingly.
The product backlog is the complete list of requirements/tasks to be completed for the project. Product backlog can be set up as yet another bucket. As you design your sprints and proceed from one sprint to the next, you can move tasks from product backlog bucket to sprint bucket and vice versa by easy drag and drop (Planner feature).
User stories in Scrum are short descriptions of a feature from the business user perspective. Since this is often expressed as text, an ideal place for this is OneNote notebook, that is part of every plan in Microsoft Planner/Office 365 Group.
Daily Scrum Meetings
In case the team is not co-located, Skype (that is part of your Office 365 subscription) is a great way to handle those 15-30 minute daily stand-ups.
OneNote is a perfect tool to capture meeting notes from daily stand-ups (or Skype) meetings. By the way, reference this post to learn more how to use OneNote effectively for meeting notes. When it comes to SCRUM Daily meetings themselves, the only three questions need to be addressed during the meeting are:
1. What did I do yesterday that helped the development team meet the sprint goal?
2. What will I do today to help the development team meet the sprint goal?
3. Do I see any impediment that prevents me or the development team from meeting the Sprint goal?
Sprint Burndown Chart
The Sprint burndown chart is a chart showing remaining work in the Sprint Backlog. While Planner does have task summary charts available, they are not in the format of the typical Sprint burndown chart.
However, such chart can manually be maintained using the statistics from the Planner itself. Each task can include the estimated/remaining effort info which can assist the Scrum Master in the preparation of the Sprint Burndown Chart.
From that point on, the Scrum Master can use Excel to pull the information together and display info via a chart.
Image Credit: Wikipedia
Release Burndown Chart
Release Burndown Chart shows the amount of work (tasks or user stories) left vs. the number of sprints. As with the previous chart, the statistics for this diagram can easily be obtained from the Planner buckets and charts and can manually be maintained/built in Excel.