
Dashboard
The Dashboard feature is available to all Scrum roles - Product Owner, ScrumMaster, and Developers. The Dashboard allows one to get an over all status of the project. You should be able to see
- Burndown chart of a project.
- Project member list.
- Current sprint.
- Time information of current sprint by developer.
- Commitment borad of current sprint.
- Sprint calendar.
- Notice board.
- Impediments of current sprint.
Top
Time entry and tracking
Developers can input actual and remaining hours as well as report impediments by tasks. Time Analysis under 'Tracking' is a good tool for Product Owner and Scrum Master to find out how the team is spending time either by story or by developer.
- Tasks assigned to a developer.
- Estimated time to complete for each task.
- Actual time spend in each day.
- Time spent on individual task.
- Remaining time on individual task.
Top

Backlog managment
Both story and bug are part of a backlog. Open product backlog includes both stories and bugs prioritized . However, bug has an explicit visibility in ScrumPad. Anybody can create stories or post bugs. Stories proposed by anybody other than Product Owner will be in proposed state. A product owner needs to accept the stories to be included in the product backlog. A story in progress can only be descoped or split to retain the history. The status of story or a bug is automatically updated based on the time entry done by the developers.
Story in ScrumPad inherently supports As a/an "role" can "action" so that "benefits" format. Also accpetance tests are integral part of a story. Stories in ScrumPad is designed to support "Card, Conversation, and Confirmation" style of requirements elaboration.
- Sprint backlogs- list of stories by sprints
- Product backlog with different dispositions- open backlog, completed backlog, stories with open bugs, and all stories
- Bug backlog- open bugs, assigned to sprints, assigned to me, and closed
- Story and task cards can be printed in pdf format to support physicall task/commitment board
- Stories can be exported and imported
Top
Sprint planning
Sprint planning is a three-step process in ScrumPad- Scope, Capacity, and Estimate. Each step has a tab.
- Sprint backlog can be created from product backlog under 'Scope'.
- Available hours for each developer can be determined under 'Capacity' tab.
- Stories can be broken down into tasks and estimate in hours.
- As the final step, estimates can be validated against the capacity at the individual as well as team level.
Top
Release planning
In ScrumPad, release planning is a core activity. A project can be organized into releases and sprints in a tree view. Stories can be assigned to sprints. ScrumPad supports "planning poker" style estimation using story points. A story point table is provided by default. Product owner can customize it for the team. Developers can individually provide poitn estimates. Product owner can finalize the estimate for stories based on consensus. Stories and be estimated and moved in bulk.
- List of releases.
- List of sprints under each release.
- List of stories under each sprint
- List of stories not assigned to any sprints
- A point matrix table.
Top
Collaboration
Scrumpad faciliatates collaboration in many ways. Project teams can have threads of conversations around stories, bugs, impediments, and projects by posting messages. They can notify each other of any updates to projects through emails. Team can chat with each other and later can refer to the conversation from chat hostory as needed. Also team can capture reprospective sessions to help follow through on recommendations.
Top

Publisher website: http://www.scrumpad.com/