I’ve grouped them accordingly, which will help in further filtering, grouping, highlighting, and generating reports in MS Project. This is depicted below.Īs you may have noticed, the team consists of the developers, the PO, and the SM. This results in less troublesome situations, the likes of which we have explored in a previous article, Lean-Agile Troubleshooting.Īs the Scrum team decides what items are to be pulled into the upcoming Sprint, we need to have team members available. In a Scrum Team, it’s a good practice to have team members who are 100% dedicated, including the Product Owner (PO) and the Scrum Master (SM). To do this in MS Project, we have to drag and drop from the “No Sprint” board column to the “Sprint 1” column.

Feature- 1: Login to the online trading system.

As this PB is presented to the Scrum Team, the team decides to the take the top three items into the Sprint Backlog:

Let’s look at the first three items for our upcoming Sprint, i.e. Select the Sprint Planning Board command from Planning drop down menu.

You can go to this view from Sprint Tools > Sprints tab > Views group. You can prioritize the backlog items with various prioritization schemes.Īn example Product Backlog is shown below in the Sprint Planning Board view with a number of feature items to be delivered for a Stock Trading System.

Before the start of the Sprint Planning event, the PB is ordered with the highest priority items at the top. A set of work items are taken from the PB for every Sprint, which in itself is a short project. The Product Backlog (PB) has all the features that you want to deliver over the life cycle of a product. Towards the end of this article, I’ll demonstrate with a video using the MS Project 2019 Sprint feature available in MS Project Online Desktop Client. I will demonstrate how to break down features into tasks. In this article, we will explore how to create a Sprint Backlog, along with its content items such as features. In fact, everything that you want to do in a Scrum project can be done with MS Project using its in-built Agile features. Some project management practitioners think that the MS Project software is not a suitable tool for managing Scrum projects or Agile projects. The Sprint Backlog, not only takes the product backlog items from the top of the Product Backlog, but can also have individual tasks and other non-feature tasks associated with it. The Sprint Backlog is prepared during the Sprint Planning event, and it’s used throughout the Sprint.

One of the key artifacts in a Scrum Project is the Sprint Backlog, with others being the Product Backlog and (Product) Increment.

Sprint layout backlog