are you ready to get to "done"?

Are You “Ready” to Get to “Done”? A Tool for Getting Backlog Items Completed

9 June 2017 Ellen Gottesdiener www.ebgconsulting.com

www.DiscoverToDeliver.com

© 2017 by EBG Consulting, Inc.

https://www.ebgconsulting.com/

© EBG Consulting, 2017 | @ellengott www.ebgconsulting.com | www.DiscoverToDeliver.com

2

@ellengott

Ellen Gottesdiener

#ready

#pCampBoston


3

Ellen Gottesdiener CEO, CPF, CSM, CSPO | Agile Product Management & Coach Ellen is a pioneer in the collaborative convergence of agile + requirements + product management. She helps product and development communities produce valuable outcomes and happy teams.

twitter: @ellengott blog: ebgconsulting.com/blog linkedIn: ellengottesdiener tips newsletter: www.ebgconsulting.com

EBG is a global leader in agile product requirements, backlog management, agile business analysis, and collaborative practices for technology products. EBG helps organizations amplify discovery to accelerate delivery.

https://www.linkedin.com/in/ellengottesdiener/

https://www.ebgconsulting.com/blog/

https://www.ebgconsulting.com/agile-resources/agile-newsletter/

https://twitter.com/ellengott


5

discover deliver


6


7

‘ready’ and ‘done’

what’s the big deal?


8

Product Backlog items that will occupy the Development Team for the upcoming Sprint are refined so that any one item can reasonably be “Done” within the Sprint time-box.

Source: Scrum Guide, 2016 (bolded added by Ellen)

“done” and “ready”

Product Backlog items that can be “Done” by the Development Team within one Sprint are deemed “Ready” for selection in a Sprint Planning.

Product Backlog items usually acquire this degree of transparency through the above described refining activities.


9

ready donerefine


10

Conditions that indicate that a

backlog item is completed,

accepted, and potentially shippable

“done”


11

Backlog item (e.g., a user story) has been developed, tested, demo’ed AND meets all required acceptance tests

Product Owner ‘accepts’ it

Item can be delivered to customer

‘done’ sample

Documentation | release notes approved

Code deployed to x server

No level x defects

Acceptance, integration tested


12

NOT ready

traveling stories


13

NOT ready

poor estimates & planning


14

NOT ready

wrong product


15

What: review, revise, detail, estimate, order backlog items

Who: PO/PM and Dev Team

When: Ongoing. Scrum Team decides how & when

How Much Time: ~ 10% of Development Team capacity

Outcome: “Ready” backlog items

Source: Scrum Guide, 2016

refinement


16

Conditions that indicate that a backlog

item is eligible to pull into a sprint

“ready”


17

Optimize collaboration

Prevent waste (of rework, unfinished work, delays)

Can double (or more) team’s velocity*

Enable getting to “done”

Enable smooth flow

* JCarsten Ruseng Jakobsen & Jeff Sutherland, SCRUM and CMMI - Going from Good to Great

Increases team domain knowledge

‘ready’ benefits


18

As a concert goer I want to use dining discounts

so I can enhance my concert experience

ready?


19

Valuable Actionable FeasibleValue is clearly articulated Aligned to Sprint goal …

Story has 7 Product Dimensions with enabling specs (e.g., wire frames) Acceptance criteria are clear, unambiguous, testable Stories organized to minimize dependencies Free from external dependencies …

Team has skills, experience, resources to develop, test, & demo story Story is estimated and sized to fit Sprint …

sample

Watch Jeff Sutherland on “Ready Ready” https://www.youtube.com/watch?v=XkhJDbaW0j0

‘ready’ for development


20

functional

nonfunctional

7 product dimensions


21

holistic


22

ActionAs a Super Fan concert goer

concert-related dining discounts I need to search for

so I can enhance my concert experience

User

Control

DataOnly members can search for dining discounts

Only “active” dining discounts can be searched

Search query and result

Interface

Environment

iOS, Chrome v50

Quality Attribute

Available 95% of time

ready

story w 7Ds


23

quality attributes


24

“ready” exercise

email Ellen: [email protected] if you’d like the exercise


25

ready done

‘ready’ to get to ’done’

refine


26

for planning for development

Release

Sprint

‘ready’ gradients


27

Releaseready

Sprintready ready done

refine

ready for planning, ready for dev


28

Release planning Goal and objectives specified, aligned with vision and roadmap Release theme identified, aligned with product vision Primary customer or persona identified…

sampleSprint planning

Goal specified Interdependencies identified, addressed Stories are valuable, feasible, actionable Stories ordered to minimize dependencies…

‘ready’ for planning


29

‘ready’ (and ‘done’)

really are a BIG deal!

www.ebgconsulting.com Events, course outlines, services, resources Tips newsletter: http://bit.ly/ebgNews

www.ebgconsulting.com/blog

www.DiscoverToDeliver.com DtoD resources, Discovery Board, Visual Language for download

Twitter @ellengott | LinkedIn linkedIn

YouTube EBGConsulting

SlideShare ellengott

stay connected!

https://www.linkedin.com/in/ellengottesdiener/

https://www.ebgconsulting.com/blog/

https://www.ebgconsulting.com/agile-resources/agile-newsletter/

https://twitter.com/ellengott

https://www.slideshare.net/ellengott

https://www.youtube.com/user/EBGConsulting


31

email [email protected]

thanks!

twitter @ellengotthttp://www.discovertodeliver.com/resource.phpresources

Are You “Ready” to Get to “Done”? A Tool for Getting Backlog Items Completed

are you ready to get to "done"?

Technology