Sprint Planning

1

Sprint Planning is a kick off meeting not the final requirements meeting• Have an Agenda for Sprint Planning and stick to it

• 2-3 hours for 2 week Sprint• During Sprint Planning

• The best estimate include acceptance criteria, cutting down on ambiguity resulting in the correct work being done the first time.

• Sprint Planning to be done right after Sprint Retrospective• Result: Put into practice what was just learned in the Sprint

Retrospective

Recommendations for Next Sprint – Sprint Planning

2

New User Story Format

4

Recommendation New User Story FormatUSER STORY As a doctor, I can search in the employee dB

so that I can find specific a specific employee

BUSINESS RULE Search only returns the names of the employees that work for or report to the requesting doctor

ASSUMPTION OR PRE-CONDITION

A doctor already exists with corresponding direct reports

DATA Doctors name .and. employees name

ACTION Doctor navigates to the employees search page, employees name field

INPUTERRORS

Doctor enters the employees name “John Adams”Doctor see a search result that includes “John Smith”

PERSONA Who is the User Story for?

ACCEPTANCE CRITERIA Doctor see a search result that only includes “John Adams”

DEFINITION OF “DONE” The team agrees on, a list of acceptance criteria which must be met before a “user story" is considered "done“

4

• User Story• As a doctor I want to add patient information in order to create a

new patient file.• Business Rule

• The following information must be entered in the record of each patient: • Patient: • Name• Address• date of birth and

• The business rule helps QA and the Team understand what “must be entered” “enforced” or the rule that must be met.

• The user story is intended to start a discussion, not be a comprehensive list of the requirements. The rule helps the team during story time.

Recommendation for New User Story Format

6

Acceptance Criteria tips …• Confirmation of requirement • Conditions of satisfaction • Good way of gathering Acceptance Criteria is asking questions such

as ‘What if … ?’, ‘Where …?’, ‘When …?’, ‘How …?’.

• Sometimes when we go thru these we realize that we have to refined or split the story into smaller stories.

Recommendation for New User Story Format

7

Definition of Done?• An explicit and concrete definition of done may seem small but

it can be the most critical checkpoint of an agile project. Without a consistent meaning of done, velocity cannot be estimated or measured.

• We are not finished with a feature until it meets the DoD(below a basic definition of done) Code Complete Unit tests written and executed Integration tested Performance tested Documented

Recommendation for New User Story Format

8

1Al Diaz, MBA, PMP, CBA, CSPO, CSM, Scaled Agile (SAFe 4.0)LinkedIn: www.linkedin.com/in/aldiazmba

Scrum Product Owner

Mon Tue Wed Thu FriKick Off Meeting – Describe Product Vision Daily Stand Up Daily Stand Up Daily Stand Up Daily Stand Up

ID Product Characteristics Writing User Stories User Interviews and

observation

Story Time, deep dive with teams to answer questions

Sizing and Release Planning

Communicate Products Value Prop or USP

Story Mapping Competitive Analysis USP / SWOT / PEST / or Porter

Breakout sessions with designer, architect and developers RE: Interviews

Prep for Retrospective

Sprint Planning ActivitiesWork on the Pricing Model Working with Competing

ProductsOutline the Products ability to address the customers problem

Story Time, deep dive with teams to answer questions

Review Analytics (IF ANY) on Product usage

Product Backlog Grooming

Senior Management Competitive Analysis and Usage Presentation

Prepare report for Sr Mgmt. on Competitive Analysis, Customer Interviews and Competing Products

Sales Competing Products Presentation, work w/ Sales on competitive battle cards (US vs. THEM)

Assist with Collateral (check, edit, advice)

Team Customer Interview Presentation

A week in the life of a Product OwnerFill in the missing activities