Tip#2- Leading you to a Sprint

Product Backlog

After the user stories are written and finalized, they are sorted to create the Product Backlog for the project during the Backlog Grooming meeting. This is a master list of all the work items that have been identified for the project and sorted by priority. Requirements are not constant during this period.The Product Backlog is dynamic and is an ongoing process. Every user story in the Product Backlog is customer centric.

The Product Backlog includes:

User centric stories based on their priority.
Ballpark estimate of the user stories.

Sprint Backlog

In the sprint planning meeting the product owner and the team decide on the user stories that can be moved from the Product Backlog to the Sprint Backlog. The team then identifies the items they can complete during the upcoming sprint. The list of the tasks that will be executed by the scrum team in the upcoming sprint is called the Sprint Backlog.

The items in the Sprint Backlog are fixed after sprint planning, and the team will focus on delivering based on this plan. However, changes in the Sprint Backlog will be inevitable as the work emerges or as the scope is negotiated based on customer feedback.

The Sprint Backlog includes:

The list of user stories within the sprint in order of priority.
The tasks that are necessary to develop each user story.
The estimation points, to complete each task.

Grooming the backlog

Our initial plans will be inadequate, since they are based on insufficient information about what will it take to complete the projects. So instead of investing efforts in trying to sync the project in line with our original plan we also need to spend more of our effort in responding to the changes that will inevitably arise as scrum is more adaptive than predictive.

Grooming includes:

New stories can be added.
Existing stories can be prioritized or removed.
Stories can be sliced into smaller chunks or resized.

Start the Sprint

Once the Sprints Backlog is finalized, you need to start the sprint to really work on the work items. Learn More on how to start a sprint.

What next after you have started the Sprint?

The scrum board. Watch this space for our next tip on scrum board.

Zoho Desk Resources

Desk Community Learning Series
Digest
Functions
Meetups
Kbase
Resources
Glossary
Desk Marketplace
MVP Corner
Word of the Day

Topic Participants
Mughil

Sticky Posts
Tip #28 - Plan less and deliver more using WIP limit in Zoho Sprints
Hello, It's been a while since we met with a quick, interesting tip. As the saying goes, "Too much of anything is good for nothing", today the focus is on delivering your outcomes with the right amount of planning. Your plan should be practical, calculative, and achievable for driving a qualitative success. Laura's plan Laura has a habit of planning her project deliverables before assigning work to her team-mates. Once the plan is finalized, she schedules a general meeting with her team and
Tip # 3- Working on the Scrum board
Continuing from our Tip #2 on leading to a sprint, let's see how to manage the work items on the Scrum board. Once you start the sprint your work items are automatically displayed on the Scrum board where you will actually manage the work items. It is a snapshot of the backlog items identified for the current sprint. The layout of the Scrum board Simply put, the scrum board is just like a physical board with sticky notes on which the work items of the active sprint are displayed. The scrum board
Tip#2- Leading you to a Sprint
Product Backlog After the user stories are written and finalized, they are sorted to create the Product Backlog for the project during the Backlog Grooming meeting. This is a master list of all the work items that have been identified for the project and sorted by priority. Requirements are not constant during this period.The Product Backlog is dynamic and is an ongoing process. Every user story in the Product Backlog is customer centric. The Product Backlog includes: User centric stories based on
Tip #1- Why swimlanes?
Lanes define a clear path to reach your destination. In Agile, swimlane is one such concept that sets a simple and clear process of the work that you do. The concept of swimlane can be related to the pool, where the swimmers gather in their respective lanes to start off. Similar to the pool, work items are grouped in different categories. Each category is referred as a lane and is displayed in horizontal format. Swimlanes are effective in categorizing the work items with respective to specific