Inputs Users

Basic Product Iteration 1 Testing I1

Feedback from Iteration 1 Iteration 2 Testing I2
Feedback from Iteration 2 Iteration 3

Iteration 10
Agile
Feedback quicker and faster
Response will be faster
Can change often
Shorter delivery times
Reduced Costs
Waterfall
Late Feedback
Response to Feedback
Cannot change often
Long development cycle/time
Higher costs
 Scrum Team

Sprint 1 ws
ws Sprint 2 ws+ws1=ws2

ws2 Sprint 3 ws2+ws3=ws4

Sprint n
 Scrum
Roles Events Artifacts
Product Owner Sprint (1 month max) Product Backlog

Developers (Cross-
functional Dev Team - QA,
BA, Dev, Arch, Supp, Desg,
Domains, Tools) Sprint Planning Sprint Backlog
Scrum Master Daily Scrum (15 mins) Working Software
Sprint Review
Sprint Retrospective
Product Backlog Refinement (ongoing activity)
Definition of Ready
Definition of Done

What do we inspect?
Sprint Planning Product Backlog
Part 1: WHAT? & WHY? Progress and Items
Part 2: HOW?

Daily Scrum Sprint Backlog

Progress

Sprint Review Working

Software/Increment
developed in the
current Sprint, Sprint
Backlog & its progress

Sprint Retrospective People & Process;

what went right or
wrong?

Sprint Product Backlog

Progress and Items,
Working
Software/Increments
so far
 Duration
Inputs Outputs Participants
(timebox)
Previous Sprint's Working Spring Goals, Sprint Backlog, Scrum Team 8 hours for 1
Increment, Product Backlog, DoR + DoD should be revisited month Sprint
Product Goals or agreed upon or lesser

Sprint Backlog Refined Sprint Backlog Developers 15 mins

(mandatory), SM and
PO are optional
Sprint Backlog, Working Feedback from the Key Scrum Team, Key 6 hours for 1
Software/Increments Stakeholders, Refined Product Stakeholders month Sprint
developered in the current Sprint Backlog; Working or lesser
Software/Increment

Action Items from last Sprint New action items (if any) Scrum Team 4 hours for 1
Retro to track the progress month Sprint
or lesser

Previous Sprint's Working
Increment, Product Backlog,
Product Goals
Feedback from the Key Scrum Team 1 month or
Stakeholders, Refined Product lesser
Backlog; Key Sprint Retro Action
Items; Working Product
Increment or Software
1 Product = 1 Product Backlog = 1 Product Owner
1 Scrum Master = 1 Scrum Team (at times, 2 teams if not LeSS or SAFe)
Developers = Max upto 10 members
 Initiative

Product Backlog Epic

User Story 1 User Story

User Story 2 Tasks
User Story 3 Subtasks

User Story n

Initiative
 Net Banking App
Ex: Login Module
Product/Initiative Face Recognition Access 13

Module Username/Password 8 Username/Password

Functionality, Feature OTP based access

Sub-features, technical tasks Finger print access
Forgot Password
New User Registration
Help/Support
FAQs
Remember Me Checkbox
Change Password
Virtual Keyboard
Login via FB/Google, etc
CAPTCHA

Epic1
Epic 2

US1
US2

Epic n
As a banking customer, I would want to login to this application by entering
username and password so that I am able login to the app and carry out my
netbanking activities.

Description/Acceptance Criteria:
(Add the details)
1. Password should be hidden.
2. Password should be alphanumeric.

Estimation: 5 days / 8 Story Points

Priority: High
READY

Task 1
Task 2
Estimations Ex.
Days 5, 6
Hours 8, 10
Story Points 1, 2, 3, 5, 8, 11
T Shirt Size XS, S, M, L, XL

SPs
XS < 10
S < 20 & > 10
M 20 to 50
L 50 to 80 or 90
XL 100+
 Planning Poker
Developers
1 1
2 2
3 3
5 4
8 5
13 6
7
8
9
10
Poker 1 Poker 2
8 8 Story Points (Relative Estimations)
8 8 Complexity
3 8 Skill Set
8 8 Efforts/Coordinations
8 8 No. of unknowns
10 8
5 8
8 8
8 8
10 8
8
 Total SP consumed Velocity (pace/speed) SP consumed
Sprint 1 30 30 Sprint 1 US1 10
Sprint 2 30 30 US2 5
Sprint 3 40 35 US3 5
Sprint 4 30 32.5 US4 10
Sprint 5 40 36.25
Sprint 6
Team 1 36.25

Team 2 55
 Release Backlog (Release Plan)
Sprint User Stories (PBI)
1 10
2 15
3 10
4 5
5 10
6 10
e Backlog (Release Plan)
Release (to the Live/Prod)

2
3
Shock Acceptance
Anger Negotiation

Adoption