ScrumPad FAQ | Commonly asked questions about ScrumPad and related service

When you signup, ScrumPad makes you the account admin. In order to get the ball rolling, you would need to do the following:

Add users from the admin menu
Create a project
Assign users to the project with one of the three roles- Product Owner, Scrum Master, Team Member.
Start adding stories to Product Backlog, if you are also playing one of these roles.
Create sprint.
From Sprint planning you can create Sprint Backlog, if you are a team member
The team needs to estimate the Sprint Backlog

You are all set to go. Happy Scrumming!

Can a user have multiple roles?

Yes, you can assign multiple roles to a user on a project. from “mange users” on Dashboard. However, we recommend that you follow Scrum best practices in this regard. You could have multiple POs, each focusing on a specific area of the product. You should have one Scrum Master per project. If your project team is located at multiple locations, you would want to have one Scrum Master per location.

What happens when I “descope” or split (rescope) a story from a running Sprint?

If the team spent some time on the story, a new story is created. The original story remains on the Sprint Backlog with a status “descoped.” The new story can be put back into Product Backlog for a future Sprint. Make sure to update the content of the story to reflect the new scope.

In case of a split, a new story is created. If the team spent some time on the original story, it is retained. Make sure to update the content of the story to reflect the reduced scope of the story. Put the new story back into product backlog for future sprint.

How can I find out how the team spent time on a sprint?

You can find timesheet for a sprint from Tracking Time Analysis menu. You will see aggregate time by developer. You can drill down how a developer spent time by story and by day.

How do I post a bug against a story?

You can post a bug from the Story>Option>Bug

How do I organize stories and bugs?

You can organize stories and bugs by adding appropriate tags. You can apply multiple tags. Later, you can search stories and bugs by these tags.

Do I need to explicitly close a Sprint?

No, the system will automatically close a sprint if remaining hours is zero.

I defined a new sprint, but I do not see it on the Dashboard?

ScrumPad considers a sprint as a current sprint by its start date. If your sprint’s start date is in the future, you will not see it in the dashboard yet.

I do not see the time worked on a sprint by the team from time analysis?

The system generates this time report based on the sprint’s start and end date. Please make sure the start and end date did not accidentally change.

I see the time shown from time analysis for a sprint is different from what I thought it should be?

Please see answer of the question "I do not see the time worked on a sprint by the team from time analysis?".

How can I assign a Bug to a Sprint?

Go to Bugs then select Open tab as shown in following picture:

Fig 1: Assigning a Bug to a Sprint
Bugs that are already assigned to current Sprint will be marked with ‘A’ on the left of each bug. The bugs that are not assigned to current Sprint should contain a link ‘Not Yet Assigned’. Use this link to move a bug to current Sprint.

How can I do Sprint estimation?

Select Estimation tab from “Planning>Sprint Planning” menu and you will see the following page:

Fig 2: Estimating a Sprint
This page will display all the Stories and Bugs assigned to the selected Sprint.

Note: If there is no task for a Story or a Bug, you will not be able to estimate time for that Story or Bug

You can easily assign/reassign a task to a user. You can change the estimation under Effort column.
For reference see following picture:

Fig 3: Sprint estimation using ScrumPad

How do I estimate stories using points?

It is a used for release planning and is based on “estimation poker.” It involves three steps:

Request the team for individual estimation
As a ‘Product Owner’, you can go to Planning > Release Estimation and there you will see following page:
Fig 4: Request Estimation

Here you will see the list of all not completed stories. At the left of each story there is a check box and at the right of each story there is a list of users of the project. Note that by default the users are hidden and to show the users you will need to click ‘Show Users’. To send request for estimation you will need to select a story and then select users and press the ‘Invite for (r)estimation’ button:

Fig 5: Invite for (r)estimation

Then emails should be sent to all the users who were selected with this link:
http://www.scrumpad.com/release_estimator/show_pending_stories
Individual team members provide estimates using story points
As a ‘Team member/Developer’ you will receive an email requested for estimation. You will also see the request message in the dashboard as shown in the picture:

Fig 6: Notification in Dashboard for estimation

By clicking either the link in email or in Notice Board you will reach to following page:

Fig 7: Estimating Points
Here you will find the list of stories to estimate. Now select your estimation and click ‘Estimate’.
Finalize estimate from the individual estimates
As a ‘Product Owner’ you will go to Planning > Release Estimation where you will get the same page as shown in Fig 1. Now click ‘Finalize’ and following view will be available:

Fig 8: Finalizing Point
For each story, you will get the estimate provided by each team members. If the team seems to agree on the estimate, you can select a point estimate for the story.

What is default priority, Order of priority, Reorder priority, Story priority and Bug priority?

Default priority
When you add any story or bug, you will get it with a default priority number. Default priority is the maximum priority plus one from the existing story and bug list. Suppose if you have a list with highest priority 125 and in this situation you add a bug, priority of this bug will set to 126.
Order of priority
The priority is set in such a way that priority with low number has the high priority. For example, if you have two stories with priority 1 and 5. Then story with priority 1 has higher priority then priority 5.
Reorder priority
If you drag any story or bug to change its pririty, it will swap its priority with the story or bug in whose position you drop it.
Story priority and Bug priority
Priority is calculate from both story and bug. But when you will see only story list the coressponding priorities are shown. For bug list you will see only their priority.

I have signed up on ScrumPad, but where do I begin?