Professional Documents
Culture Documents
The Backlog Tab: Goal is to provide a simple view of the Features and Stories on one single backlog list. We also see the story points and any change management notes. The bottom
has total initial scope and tracks how many new stories were added so we can measure scope changes.
1 - Security
1 1.1 As a Customer I want to Login so that I can access my account 2 1
2
3 1
1.2 As a Customer I want to register for new online account so I can access my information
3 1
1.3 Customer retrives forgotten password
Cancelled this story on 12/22 due to product owner request.
2 2 Will send email to customer service to get password reset.
1.4 Customer adds password hint
2 - Profile Management
3 2.1 Customer creates new profile 5 1
This was a 5 and was re-estimated during the retropsective to
2 1
2.2 Customer updates existing profile information 2 because the team found that most of the work was already
3 - Place Order done in 2.1.
4 3.1 As a Customer I want to search the product list so that I can find what I want. 3 1
3.2 Customer browses all products 2 1
5 3.3 Customer adds product to cart 5 1
3.4 Customer completes order 8 1
Added this story during iteration 2. Product Owner approved
5 1 on dd/mm/yy
* 3.5 Customer views product reviews
4 - Order Maintenece
4.1 Customer checks order status 2 1
4.2 Customer cancels recent order 2 1
4.3 Customer searchs order history 3 1
100 - Non Functional Stories
100.1 Migrate customer data from legacy system to new oracle db 8 1
100.2 Develop High Level Architectural diagram for new system 2 1
100.3 Develop high level ERD and Logical database diagrams. 3 1
100.4 Develop High Level business process models 2 1
100.5 Design look and feel for site and high level site navigation prototype 3 1
Original Story Points for Release 1 58
New Points for Release 1 7
Total Points for Release 1 65 11% Change in scope
A - Vendor Selection
A1- As a … I want to develop the RFP we will submit for vendor selection so that our needs
and qualifications are shared with potential vendors.
1.1 as a …. I want to develop/brainstorm the list of catagories to include in the RFP
1.2 as a .. I want to identify the stakeholder departments affected so I can invite them
1.3 as a .. I want to include questions and requirements from the ABC dept
1.4 as a … I want to develop initial draft of RFT
1.5 as a … I want to review the RFP and gain consensus on final draft
A2- As a … I want to submit the RFP to the potential vendors so they can respond to it.
A3- As a … I want to select our top vendor based on their RFP responses so we can move
forward with the contracting processes.
B - Contracting
This is a powerful view of the release plan on a project. It shows each iteration plan in detail and answers: what stories are planned, what
is the target for each story, what was the actual outcome, who is the owner/manager of that story. How does are target vs actual velocity
look? how are we doing overall? Release Burnup Tab links to this one for it's data.
Setup Iteration
STORY STORY GOAL
STORIES Owner
POINTS
100.5 Design look and feel for site and high level
site navigation prototype 3 Beth Smith Done Done
#REF!
Iteration #3 Story Points Iteration 7 9
Cumulative 63 52
Iteration Cost Iteration $ 90,000.00 $ 120,000.00
Cumulative $ 360,000.00 $ 408,000.00
FINAL
USER TRAINING
PRODUCTION
PROJECT TRANSITION
HELP DOCUMENTATION
REGRESSION AND INTEGRATION TESTING
USER ACCEPTANCE & SIGNGOFF
10/31/2011
Move to Production
These are powerful charts you can show to your business product owner (and to the team) to track progress. The Earned Value tracks how many story points were actually delivered compared to the
also tracks the very important SCOPE line which tracks total backlog points and measures any changes to it.
The Cost tracks traget vs actual dollar burn in addition to the funding line that tracks how much we were funed for and any funding increases over time.
The bottom graph tracks number of defects and impediements per iteraiton. Defects are bugs found during regression testing.
Total
Start End Targeted Actual Projected Story Pts Start End Targeted Actual Projected Total Funding
Iteration 0 12/30 12/30 18 10 58 Iteration 0 11/19 12/11 $ 90,000.00 $ 85,000.00 $ 450,000.00
Iteration 1 12/30 12/30 33 28 58 Iteration 1 12/12 1/1 $ 180,000.00 $ 178,000.00 $ 450,000.00
Iteration 2 12/30 12/30 56 43 63 Iteration 2 1/2 1/30 $ 270,000.00 $ 288,000.00 $ 450,000.00
Iteration 3 12/30 12/30 63 52 63 Iteration 3 1/31 2/20 $ 360,000.00 $ 408,000.00 $ 550,000.00
Iteration 4 12/30 12/30 66 66 66 Iteration 4 2/21 3/12 $ 450,000.00 $ 550,000.00
Pre-Release 3/29 4/19 Pre-Release 12/30 10/31 $ 540,000.00 $ 550,000.00
(We can also create a burn up chart that would show actual business value using Business Value Points. Email me for more information Sally@AgileTransformation.com)
Story Points Delivered $600,000.00 COST
100 $550,000.00 $550,000.00 $550,000.00
$540,000.00
$500,000.00
$408,000.00
Cost
$400,000.00
66 66 $360,000.00
63 63 63
60
58 58 56 $300,000.00
52 $288,000.00
$270,000.00
43
40
$200,000.00
33 $180,000.00 $178,000.00
28
20 $100,000.00
18 $90,000.00 $85,000.00
10
0 $-
Iteration 0 Iteration 1 Iteration 2 Iteration 3 Iteration 4 Pre-Release 1 2 3 4 5 6
0.00
0,000.00 $550,000.00
A Journey Through an Agile/Scrum Project Lifecycle Real World Agile for Teams - 3 day works
Thinking of Agile? Start Here Agile for Executives and Leaders - 1 Day
Agile Visual Modeling Techniques Agile for Product Owners - 2 Days
Agile Estimating and Planning Agile Portfolio Management - 2 days
Agile vs. Traditional Roles Agile Project Management - 2 or 3 days
More... Agile Transformation Strategy Planning -
Agile Requirements Gathering - 3 Days
Scrum 101 Videos Servant Leadership - Leading High Perfo
Effective Facilitation and Collaboration Sk
Scrum 101 – Part 1 | Scrum Basics
Scrum 101 – Part 2 | The Scrum Process
Scrum 101 – Part 3 | Scrum Values
Scrum 101 – Part 4 | Scrum Terms Review
g with Kanban
ransitioning to Agile
Acceptance Test Cases for Project xyz Acceptance Criteria
Acceptance Tests are core Agile requirements. I recommend that you document every business rule as a test case here in the format 'Verify that when <action occurs> <expected
result>. Attach (or link to) a spread sheet with input/output expected data for stories that are data/reporting related.
1.1 As a Customer I want to Login TC1 Verify that customer with valid user name and password can
so that I can access my account login successfully
1.1 Customer Login TC2 Verify that customer with invalid user name cannot login and
gets correct error message
1.1 Customer Login TC3 Verify that customer with invalid format for user name or
password cannot login and gets correct error message
1.1 Customer Login TC4 Verify that customer who forgets to input user name or password
gets correct error message
1.1 Customer Login TC5 Verity that different users in different roles can login and are
forwarded to appropriate landing page
Iteration Impediment Severity Affects Assigned to Who Opened Resolved Open Days Current State and Notes
(H, M, L) Story? for Follow-up? Date Date
0 Waiting for John an answer to xyz M 2.3 John 2/12/2008 2/17/2008 5 John emailed me back a reply and cc'd Amy (BA) who documented the
business rule new rules
0 0
0
0
0
1
1
1
Listing the team members here and their contact information is helpful plus their allocation and planned days off is very useful.
Using the iteration capacity and utilization planning is optional and could be used if the team finds it useful for them to plan their work. The best method for determining capacity is
looking at previous velocity then adjusting for vacation or holidays.
Email me if you have questions about what the data in this worksheet means. Sally@AgileTraining.com
Use the table below to map out each story into the sub-deliverables (tasks/milestones) through the course of your iteration so you can plan your
capacity and commitements better as a team. Color code the different type of work (req, desgin, dev, testing, uat..). This is best done on a physical
visible wall.
Column1 Column2 Column3 Column4 Column5 Column6 Column7 Column8 Column9 Column10 Column11
Iteration #: 5 (2 wks)
Stories Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
Update Design and Code Test TC1, TC2 UAT TC1,2,3
Req/UAT Doc - Deploy
TC1,2,3 - AJ - Shri
1.1 As a manager I Jen
want to .. So that.. Test TC1, TC2 UAT
Design and Code TC4-
6 - AJ Deploy - Shri TC4,5,6
Retrospe
Planning
Demo &
Review
Accept
ctive |
Sprint
Sprint
Sprint
Final
ance
and
Update Design and Code Automate xyz UAT xyz
Req/UAT Doc - Deploy - Lilly
xyz - Adam
Jen
1.2 As a supervisor I Code abc - Adam Test abc - Shri UAT abc
want to .. So that.. Deploy
Design Review
$0 $0 $0 $0 $0 $0
$0 $0 $0 $0 $0 $0
$0 $0 $0 $0 $0 $0
1 QA & 2 Dev
only 50% of
May
Aug Sep Oct Nov Dec Total
22 18 22 19 19 243
$0 $0 $0 $0 $0 $0
$0
$0
$0 $0 $0 $0 $0 $0
$0 $0 $0 $0 $0 $0
$0 $0 $0 $0 $0 $0
$0 $0 $0 $0 $0 $0
$22,880
12/30
12/31
task. Enter each day's remaining hrs at Hrs
1/1
1/2
1/3
1/4
1/5
1/6
Story (linked) Resources (linke TaskType Status Notes
right. Each column is sortable. Burndowns Est
automatically update.
Story Final UI Complexity Points2 Business Rules/Logic Complexity Points3 DB/Integration Points4 Testing Complexity Points5 Notes
Points Complexity
Iteration Iteration
RISK HOW IS IT ADDRESSED? Severity
Identified Addressed
Release
The team is new to Portlet Factory. Director has agreed to send team to High 2
Planning
Many of them don't know how to use it. training during iteration 2
We have never integrated with XYZ
system before. This is our first time High 0 1
sending that system a file from the Java Proof of Concept story identified in
side. Iteration 0. Scheduled for Iteration 1.
Iteration Level
No Severity I or II Defects
Release Level
SAR
Business Rules
Closure Report
Transition Report
Archive Project Artifacts