Create Project

Click on create New Project.
Name your new Project.
Choose color for your Project.
Click on the Create Project button.

Delete Project

Click on the 3 dots in the bottom right corner.
Click on Delete Project.
Confirm the process by clicking on the Delete button.

Archive Project

Click on the 3 dots in the bottom right corner.
Click on Archive Project.
Confirm the process by clicking on the Archive button.
You can find Archived Projects at the bottom of the page.

Create Sprint

Click on your Project’s name.
Click on the Create new sprint button.

Delete Sprint

Click on your Project’s name.
You can find the Trash icon on the left.
Click on the Trash icon.
Click on the Delete button.

Adding data manually

Capacity

Sprint: You can rename your Sprint by clicking on it.
Sprint Interval: You can define your Sprint Interval by selecting the start/end date.
Members: You can add part time members of your project (e.g.: you have 5 developers working full time, one working half time, members should be 5.5.).
Days: You can define working days in your projects.
Personal holidays: Note to put sum days here, the cumulated number of all the days of all your dev team took off during a sprint.
Bank holidays: Note to add the number of holidays only (official holidays as christmas, easter, etc.) and DO NOT multiply this number with the number of your team members.
Developer days Are calculated automatically.

Add Data User Story

Title: Add the title of your user stories and other backlog items here and pay attention to stay on story level and avoid adding sub-tasks as it’ll mess up your sprint insights. (tl;dr: sub-tasks don’t come here).
Story point: You can select story points from the drop-down list.
Spent: You can add spent time.

Original: You can add the original estimate. Add the original estimates here for every backlog item your team worked on in a given sprint. Original estimates are the number of hours your team planned to work on an item before the sprint started.
Remaining: You can add remaining time.
Status:
– Accepted item: Every item (planned or not planned) counts as accepted that the Product Owner decided to accept (at the demo event or any time during the sprint).
– Not accepted item: Every item (planned or not planned) counts as not-accepted that went to demo regardless what the Product Owner decided at the end of the demo.
– Started item: Any item (planned or not-planned) the team started to work on, but did not finish, gets the tag “started”.
– Not-started item: Any item (planned or not planned) the team put in the Sprint Backlog, but did not start working on it counts as an item “not started”.
Planned/Not Planned: Items can be “planned” or “not-planned” . Every item your team could/did plan on at the beginning of the sprint, counts as “planned” and every other item someone threw in during the sprint counts as “not-planned”.
Type: User story-level backlog items fall into 4 types: they can be actual user stories, technical debts, tasks and bugs. Choose accordingly!

Team events

Only events your development team visited or performed comes here. Avoid putting Scrum Master, Product Owner, Business Analyst or any other person’s spent time here. Pay attention to put sum hours here only.(e.g.: You have 4 developers working for 2 hours, then you put 8 hours in the cell here.)

PO log

Your Product Owner’s table. Everything your PO does during a sprint comes here. Note that Hours are sum hours, a cumulated number of all the hours your Product Owner spent on given types of tasks.

SM log

This is your table 🙂 Everything you do as a scrum master during a sprint, put those hours here. Note that Hours are sum hours, a cumulated number of all the hours your Product Owner spent on given types of tasks.