Your SlideShare is downloading. ×
0
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
ScrumPad Overview
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ScrumPad Overview

2,019

Published on

This presentation provides an overview of ScrumPad- vision, core concepts, and how to use ScrumPad by project roles.

This presentation provides an overview of ScrumPad- vision, core concepts, and how to use ScrumPad by project roles.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,019
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
32
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Introduction to ScrumPadr ScrumPad, A Web-based Agile/Scrum Project Management Platform Developed by Code71 www.scrumpad.com www.scrumpad.com www.code71. com Copyright 2010, Code71 Inc. All rights reserved.
  • 2. What is ScrumPad? A Web-based Agile Scrum project management platform ScrumPad Vision ScrumPad is fun and social for everyday use ScrumPad is pragmat ic, and not prescriptive or limit ing ScrumPad is a plat form nurturing “a project eco-system,” not just a mere tool www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 2
  • 3. ScrumPad Focus Three primary focus areas Zero learning curve- minimize “tool” time, increase “goal” time for users Collaboration- increase project visibility and transparency through encouraging interactions Harvesting knowledge- capture different kinds of project related information that is valuable for long-term success of the project www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 3
  • 4. ScrumPad High Level Concepts backlog backlog backlog Project milestone release sprint Backlog #2 Project milestone release sprint #1 Product backlog backlog backlog Portfolio www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 4
  • 5. ScrumPad Core Concepts collaboratio n time reputation impediments Glossary Backlog tasks comments Test cases rules rating tags bugs story files decisions organization messages wiki www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 5
  • 6. ScrumPad Community Partner Client Subscription Project Account Company User Account owner Affiliate Expert www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 6
  • 7. Roles supported Project Roles A dmin R oles Read/Write access PO Company Account Read/Write access Admin Owner SM Team Users Read access Read Stakeholder access Stakeholder www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 7
  • 8. How will a Product Owner use ScrumPad? • Product Management • Add/Modify stories or bugs • Breakdown stories (progressive elaboration) into smaller ones (a.ka. Split a story) • Have conversation with the team around a story (messaging) • Accept/reject stories proposed by others • Prioritize backlog (through easy drag & drop, direct edit, etc) • Organize stories using tags (tag management) • Plan releases (planning poker, create releases & sprints, baselining releases) • Supporting Sprint Activities • Have conversation with the team around a story (messaging) • Help resolve impediments reported by the team • Accept/reject work done (stories/bugs in review) by the team during a sprint • Descope stories /bugs www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 8
  • 9. How will a Product Owner use ScrumPad? (contd.) • Tracking & Reporting • Analyze time spent(drill down by stories and bugs, or by developers • Analyze Lead time and Cycle time • Analyze estimation trend (see how story points map to actual time spent) • Velocity trends • Compare burndown charts • Track quality trends- (bug fix rate, bug reported rate, bug density report etc.) • Track costs (by release, by sprint, overall) • Track progress ( e.g., work done by components/modules/business areas, release burndown, product burndown etc.) • Track project activity through “Daily Digests” www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 9
  • 10. How will a Scrum Master use ScrumPad? • Supporting Sprint Activities • Use burndown chart & task board to facilitate daily scrum • Help resolve impediments reported by the team • Manage users on the project (add/remove access) • Help plan sprints • Tracking & Reporting • Track time/ point • Cost, quality, progress reports • Help the team understand what the trends are (Bug chart, Estimation, Quality, etc.) and what it means for the project. • Track project activity through “Daily Digests” www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 10
  • 11. How will a Developer use ScrumPad? • Supporting Sprint Activities • Plan sprints (task breakdown, time estimation, capacity planning) • Collaborate on a task (e.g., pair-programming etc.) • Have conversation with the product owner and the team around a story/bug (messaging) • Report daily time (optional for teams only tracking points) • Report impediments, if any, and follow-up/track to resolution •Product Management • Propose stories • Add test cases to stories/bugs • Help product owner with defining acceptance test cases • Participate in planning poker (estimation) • Tracking & Reporting • Burdown charts • Velocity • Bug charts www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 11
  • 12. How will a Tester use ScrumPad? • Supporting Sprint Activities • Track testing activities • Report bugs •Product Management • Propose stories • Add test cases to stories/bugs • Help product owner with defining acceptance test cases • Tracking & Reporting • Burdown charts • Velocity • Bug charts (bug fix rate, bug reported rate) • Cumulative test flow chart in a sprint • Bug density report (i.e. Bugs by components/areas of concern) • Test case report (i.e., stories with test cases, without test cases etc.) www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 12
  • 13. How will an Admin use ScrumPad? • Users management • Add/remove users to projects • Change users’ roles (company level and or project level) • Track ScrumPad access / usage • Project administration • Organize related projects into portfolios • Organize a large project as a portfolio • Provide vendors (design company, any service provider), and / or clients access to projects • Track project activity (using project activity chart) • Company administration • Add/remove vendors or clients and their users www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 13
  • 14. Story/Bug Lifecycle cannot be assigned to another sprint De-scope Cannot be deleted All tasks = completed In In review progress At least one task = in progress Accept/conditional reject accept all tasks = not started Or descoped any task = in progress De-scoped proposed Open completed Rejected Accepted by a product owner Created Created by others by a product owner Story Lifecycle start end www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 14
  • 15. Task Lifecycle •Manual changes to •Cannot be deleted •Must be in the current sprint status must follow the •Can be reassigned to same rules. Appropriate feedback should be another developer- a new Time remaining = 0 / provided when rules fail. ask will be created In Reassigned progress New task if reassigned Time spent >0 & Time spent = 0 Time remaining> 0 Not Time remaining > 0 Completed/ New task started Reassigned Time spent = 0 created ete in the current or int to delete Task Lifecycle eassigned to eveloper without a new task start end •Cannot be deleted •Cannot be reassigned www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 15
  • 16. Contact us • For more details on each feature with screenshots, please visit our features page. • The best way to evaluate ScrumPad is to Sign up for a free 30-day trail and try it on your project • Please let us know- what you like, what you don’t like, and what is missing. We really appreciate candid feedback. • Email us at support@scrumpad.com with your inquiry • Go to our Web site at www.scrumpad.com and click on contact us link www.code71. com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad. com Page 16

×