new use the lotus blossom technique to build 64 … · 2016. 9. 27. · copyright 2016....

Copyright 2016. Collaborative Leadership Team. 1

IIBA Professional Development Day - September 20, 2016

Dean Gabbert - Collaborative Leadership Team

USE THE LOTUS BLOSSOM TECHNIQUETO BUILD 64 BACKLOG ITEMS

IN 90 MINUTES OR LESS


Dean GabbertAgile Coach & Trainer with Collaborative Leadership Team

• 20+ Years in Information Technology, Sales & Marketing

• Certified ScrumMaster (CSM)

• Certified Scrum Product Owner (CSPO)

• ICAgile Certified Coach & Facilitator

• Married with 2 Boys & 2 Dogs

INTRO


INTRO


Jeff Sutherland

Yasuo Matsumura

I’m not a smart man, but I know what good Scrum is.


BACKGROUND & NEED

Product Backlog DefinitionThe Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

A Product Backlog is never complete. The earliest development of it only lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. As long as a product exists, its Product Backlog also exists.

The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have the attributes of a description, order, estimate and value.

Scrum Guide - July 2016 www.scrumguides.org


BACKGROUND & NEED

Ready Backlog is a Universal Challenge

• Product Owner is the most difficult role in Scrum

• Hard for team members to see the “whole”

• Product Owner and Team tend to avoid the big up front planning meetings before starting the work

• A picture is worth a 1000 words

• New Teams - hesitant to provide input - safety has not been established

• Failure to Launch - waiting on perfect

• Very difficult to have a dynamic, rich conversation staring at a computer generated backlog list or a spreadsheet


WHY I LIKE THIS TECHNIQUE

• Low Risk

• Easy

• Involves the whole team

• Can work with remote team members

• HIGHLY Visible

• Fun

FAST!!!


SETUP & SUPPLIES

• Who Should Attend? Entire team, Product Owner, ScrumMaster (facilitator) & key stakeholders if appropriate/helpful

• Pre-configured White Board Space or Flip Chart Paper or Gaming Mat?

• Sharpies (Don’t use regular pens)

• Blue Painters Tape

• Post-it Notes - Super Sticky (very important)

• 8 distinct colors in both a 4x4 and 3x3 size

• Regular Post-it note yellow - 3x3

• Snacks & Beverages

• Open floor space or large conference room - people will be moving around

• Timing Device

Communicate, Communicate, Communicate!


TIMING & FACILITATION

Book at least 2 hours for the event*

Have the supplies ready to go

Pre-populate the board with the Main Product Focus in the middle and the 8

themes/categories placeholders

Intro - 5 Min

Agree/Confirm Product Focus - 5 Min


TIMING & FACILITATIONBuild the 8 Themes or Categories - 16 Min

1

6

7

5 4

3

28

Start Here

1 23456

78


TIMING & FACILITATIONExpand Each Theme - One at a time - 48 Min


TIMING & FACILITATION

Final Timing

Intro - 5 Min

Agree/Confirm Product Focus - 5 Min

Build 8 Themes/Categories - 16 Min

Expand 8 Themes/Categories (6 min each) - 48 Min

Transfer Time Between Categories - 8 Min

View The Board/Mat & Add Any Final Thoughts - 8 Min

Total - 90 Min


NEXT STEPS

• Share it with other people/stakeholders/teams to get feedback.

• Determine best category/theme to start with. Highest value.

• Create a definition of done for that overall category/theme and the backlog items associated with it.

• Start Sprinting!!!!

• Product Owner - try to stay at least one or two sprints ahead of the team with ready backlog.

• Remember - the product backlog is evolving, is never complete and is constantly changing. You will never be able to “do it all.”

You Have 64 Backlog Items, Now What?


WHAT ELSE?

• Slicing a really big backlog item into smaller items.

• Creating a definition of done for complex products.

• Drafting a team working agreement.

• Creating or organizing new teams and team members.

• Original intent - developing new product or service ideas.

• Plan a vacation.

• Create an outline for your IIBA talk.

• ??

Other Areas You Could Use This Technique

Copyright 2016. Collaborative Leadership Team.

THANK YOU!

[email protected]

MOBILE: 612-750-9805

@DEANGABBERT

new use the lotus blossom technique to build 64 … · 2016. 9. 27. · copyright 2016....

Documents