FOCUS! A Core Scrum Value By Ron Quartel 05/05/2015 Introduction - - PowerPoint PPT Presentation

05/05/2015

FOCUS! – A Core Scrum Value

By Ron Quartel

<Footer Content: Presentation Title, Partner Name, Other> 2

Introduction

<Footer Content: Presentation Title, Partner Name, Other> 3

Who Am I?

<Footer Content: Presentation Title, Partner Name, Other> 4

Inventor of new agile Methodology

FAST Agile

Creator of

Backlog Optimizer http://backlogoptimizer.com/

@agileAgitator

http://www.linkedin.com/in/rquartel http://blog.agileagitator.com

Ron Quartel

Agile Coach, Development Manager, Lean Entrepreneur

What I’m going to talk about

Why do I want to talk about FOCUS?

6

7

Overview

8

As a Scrum Master, I want to help my team be more focused So that they are more efficient at delivering working software

Scrum Values

C F O R C

9

Eliminate Waste (Lean)

<Footer Content: Presentation Title, Partner Name, Other> 10

»Poor Practices »Time Wasting »Distractions

<Footer Content: Presentation Title, Partner Name, Other> 11

Four uses of time (including three types of work)

<Footer Content: Presentation Title, Partner Name, Other> 12

<Footer Content: Presentation Title, Partner Name, Other> 13

Predefined Work

Predefined Work

• Core hours
• Work/Pairing sessions + other (emails, expense reports, research)
• Breaks and exercise (Fatigue is the antonym of focus)
• Pomodoro technique
• Colocation
• Office layout
• Cleanliness / Tidyness
• Diet
• Pair programming / Mob programming

< 14

Pair Programming

• Two brains are better than one
• Can’t read facebook when you are paired

Pair programming

<> 16

Mob Programming

17

18

The work of Planning Work

Meetings – where time and your soul come to die

How do you make meetings more efficient?

• No laptops
• DoD / Acceptance Criteria
• Get in, get out
• Off topic? Ask the room for consensus to change DoD / acceptance criteria or parking lot for Part II
• Timing of meetings. Follow an existing break in work flow e.g. immediately after standup, lunch, or a

natural break so team members can maintain focus

• Get out of unnecessary meetings (Optional = NO)
• Keep your delivery team out of meetings as much as possible
• Come to consensus quick!

19

Scrum Events Backlog Refinement (Grooming)

• Estimating is tiring – keep this meeting short and within the timebox
• Timing of this (and any meeting)
• Planning Poker – should be able to plan in five minutes, if not come back to it later

Daily Scrum (Stand up meeting)

• 15 minutes + Parking Lots (optional)

Sprint Review

• No stakeholders – no meeting
• Make demo slick and fast – designed to gain feedback

<Footer Content: Presentation Title, Partner Name, Other> 20

<Footer Content: Presentation Title, Partner Name, Other> 21

Work as it appears

Work as it appears (Unplanned Work)

• Production Issues (Fire Drilled Procedure)
• Broken build (example for fire drilled procedure)
• Bugs – stop making them (Extreme Programming)
• Valid business interruptions / needs (Handle outside dev time)

<Footer Content: Presentation Title, Partner Name, Other> 22

<Footer Content: Presentation Title, Partner Name, Other> 23

Distractions

Environment

Co-locate and sit together (maximize communication real time) Open office (but not open floor – unnecessary noise) Clean and tidy Remove phones Pairing station + Personal space (XP office layout) Healthy (air, natural light, comfortable seating) Larger monitors (code on the screen is more productive) Fast pairing machines and slow personal machines Build / Continuous Integration Server in room Physical Sprint Board in room

24

Working Agreements

Agree not to allow distractions…

• During dev / pairing time - answer cell phone only if urgent
• Go to the bathroom (USA) / restroom (Canada) / toilet (rest of the world) before a dev session
• No looking at your phone during a pairing session

<Footer Content: Presentation Title, Partner Name, Other> 25

<Footer Content: Presentation Title, Partner Name, Other> 26

Thank you!