Lesson Overview Lesson Overview Seed Plants Lesson Overview 22.3 Seed Plants.
ScrumPad Overview
Click here to load reader
-
Upload
syed-rayhan -
Category
Technology
-
view
2.005 -
download
0
description
Transcript of ScrumPad Overview
Copyright 2010, Code71 Inc. All rights reserved.www.code71.com www.scrumpad.com
ScrumPad, A Web-based Agile/Scrum Project Management Platform
Developed by Code71www.scrumpad.com
Introduction to ScrumPadr
Page 2www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
What is ScrumPad?
A Web-based Agile Scrum project management platform
ScrumPad VisionScrumPad is fun and social for everyday use
ScrumPad is pragmatic , and not prescriptive or limit ing
ScrumPad is a platform nurturing “a project eco-system,” not just a mere tool
Page 3www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
ScrumPad Focus
Three primary focus areasZero 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
Page 4www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
ScrumPad High Level Concepts
sprintreleaseProject#1
backlog
milestone
ProductPortfolio
Project#2
backlog backlog
backlog backlog backlog
sprintrelease milestoneBacklog
Page 5www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
ScrumPad Core Concepts
story
tasks
messages
impediments
filesbugs
comments
decisions
rules
time
Glossary
tags
Backlog
organization
collaboration
rating
reputation
wiki
Test cases
Page 6www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
ScrumPad Community
UserCompany
Client
Account
Partner
Affiliate
Subscription Project
ExpertAccount owner
Page 7www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
Roles supported
PO
SM Team
Stakeholder
Project Roles Admin RolesRead/Write
access
Readaccess
CompanyAdmin
Users
AccountOwner
StakeholderRead
access
Read/Writeaccess
Page 8www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
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
Page 9www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
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”
Page 10www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
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”
Page 11www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
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
Page 12www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
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.)
Page 13www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
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
Page 14www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
Story/Bug Lifecycle
Open
Inprogress
completed
At least one task = in progress
All tasks = completed
Story Lifecycle
any task = in progress
all tasks = not startedOr descoped
De-scopedRejectedproposed
Accepted by
a product owner
start end
Created by a product
owner
De-scope
cannot be assigned to another sprint
Cannot be deleted
In review
Accept/conditional accept reject
Created by others
Page 15www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
Task Lifecycle
Not started
Inprogress
Completed/Reassigned
Time spent >0 &Time remaining> 0
Time remaining = 0 /Reassigned
Task Lifecycle
Time remaining > 0
Time spent = 0
created
•Cannot be deleted•Must be in the current sprint•Can be reassigned to another developer- a new task will be created
•Cannot be deleted•Cannot be reassigned
start end
•Can delete•Must be in the current or future sprint to delete•Can be reassigned to another developer without creating a new task
•Manual changes to status must follow the same rules. Appropriate feedback should be provided when rules fail.
Time spent = 0
New task
New task if reassigned
Page 16www.code71.com Copyright 2010, Code71 Inc. All rights reserved. www.scrumpad.com
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 [email protected] with your inquiry
• Go to our Web site at www.scrumpad.com and click on contact us link