From Nothing to Scragban – The Evolution of How We Work

View Github Repository Open presentation in a new window

rwoolley

See all presentation from rwoolley

From Nothing to Scragban – The Evolution of How We Work

0 0

revealjs_classify

On Github rwoolley / revealjs_classify

From Nothing to Scragban

The Evolution of How We Work

Created by Rob Woolley / @rdotwoolley

Slide Notes: A lightning talk about how we stole things from Scrum, Agile and Kanban to build out how we do what we do.

Platform Engineering Team

Also known as the LIVE team

We have two jobs:

Availability, Reliability, and Resilience of our platform Missing and Broken Feature by Human!

Slide Notes: Note the ARR and business unit ARR, Annual recurring rev, vs Availability, Reliability and Resilience. This is a culture hack, no one can say they are not worried about ARR aka the bottom line. Diff teams just see it differently.

First, there was ...

Slide Notes:

Then, there was BYOB...

Bribes Yelling Oppression Beatings Slide Notes:

Live Team Unite!

So we organized a daily standup to coordinate our efforts.

Slide Notes: working alone we were susceptible to bad things. As a team we were a force to be reckoned with and respected. First SCRUM element

What is that we do every day?

We began to classify and understand our day-to-day work

Slide Notes: You have to know what is going on day-to-day

We do 6 types of work everyday...

Or is that just the number of colors available in the standard 3x5 pack of index cards from Oxford?

Slide Notes: Great example of constraining your WIP

Then we started to Radiate

Never underestimate the power of a magnetic whiteboard.

Slide Notes: First Kanban ish element

Then we added a daily burndown

Where did we get to today?

Slide Notes: First An Agile ish element our sprints are 1 day. Start at 12:00am MST and wrap up at 11pm MST

Use your Tools!

This company uses Atlassian Products. We have hacked Jira to do our bidding...

  • Added Cultural Gravitas to Due Dates
  • Hacked Components
  • Build Out and Constantly Tweaks workflow

Slide Notes: Transparency!

Global Business, Global Team

Not everyone can see our sweet whiteboard...

Slide Notes: Put up a Side-by-side of Mylene and Rob's jira dashboards

Daily stats...

Slide Notes: Image of the jiraClient output https://s3.amazonaws.com/rdot-personal/presentation_content/classify_lightning/jiraClientStats.png

Radiate Smarter...

Slide Notes: Image of the vmars dashboard https://s3.amazonaws.com/rdot-personal/presentation_content/classify_lightning/LIve_dash_board.png

Retrospectives

We have one every two weeks, we look for holes and gaps in how we provide our service. We are continuously improving.

Slide Notes: Another thing we stole from Agile

MVB

We started to add process around work getting to this team. We needed a back pressure mechanism to ensure team stability and to make sure people engaged us responsibly.

Slide Notes: Picture of the approve button. https://s3.amazonaws.com/rdot-personal/presentation_content/classify_lightning/approve.png

How Much Can You Actually Do?

Most desired service from our team? Certainty

  • Due Dates are our primary communication mechanism
  • The capacity of the team on any given day is finite
  • Match our daily capacity to what we schedule for that day
  • Use the burndown to make sure we're on track for the day

Slide Notes:

When Can You Get It Done By?

There are two types of work:

Planned Unplanned

We must have the ability to handle both without burning the team out and getting the business to accept WIP limits.

What do you mean I can't have it all!?!?

Slide Notes: We do this with escalation vs scheduled work. What we are working on is always negotiable. The Capacity of the team is not.

The SCR in SCRAGBAN is for SCRUM

Standups Burndown Capacity Planning

Slide Notes: This is the primary mechanism for team happiness and BYOB eradication

The AG in SCRAGBAN is for AGILE

18 Hour Sprint. EVERY DAY The Queue is our backlog

The BAN is for KANBAN

WIP limits Capacity Planning Dope Kanban Board

Thanks!