Tip #4 - Status Timeline
This week let's have a quick understanding of the interesting enhancement in Zoho Sprints. Did you happen to see something called 'Status Timeline' in your work item details section? - Yes? - Then you are ready to know what it actually does. No? - Quickly navigate to your work item details page and click Status Timeline from the top navigation bar.
What does it do?
Tracks the time taken by a work item to move across statuses on the scrum board. It also helps you know the number of days the work item was idle in a particular status. Apart from this, it also tracks the maximum and minimum time the work item remained in a particular status.
When to view?
The ideal time to view your status timeline is when the work item is not delivered on the actual end date. What if the admin or sprint owner wants to know the actual reason for the delay? They can directly navigate to the status timeline and view the work item's progress across statuses.
How does it benefit?
- You can track the status in which the user has spent the maximum and minimum time.
- If the work item is assigned to multiple users, you can track the user who has moved the item to a different status.
- Track the recurrence of the status if the work item is transitioned multiple times to the same status.
- It also indicates a 'Yet to close' status if the item is yet to be moved to any of the closed statuses in the sprint.
- If it's a parent item you can check the number of subitems added to it in a particular status.
- You can also view the status timeline for each individual subitem.
Use the status timeline to know the complete workflow of your work item, so that you can never miss any bottlenecks that hinder the progress. Check out our
resource center
and email to
support@zohosprints.com
for any queries.
Topic Participants
monica
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 andTip # 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 boardTip#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 onTip #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