Java Tech & Tools | Using a Pull System for Just-In-Time Development | John Stevenson

©LeanAgileMachineCreative Commons Licence

JIT Development with kanban

John StevensonLean Agile Machine

Who is John Stevenson

@JR0cket

Basics of kanban

Visualise your challenges

Additional goal

What is the problem...

Never enought time

Always more to do

Something urgent comes up

Missed opportunities

Work to do, bills to pay, kids to feed...

Window of opportunity for getting stuff done is limited

How many hours do you work a

week ?

How many hours are you productive

per week ?

What is Kanban ?

● A way to manage dependant events● Make your work visible● Limit your work in progress

Avoiding multi-tasking – its inefficient

● Pull system only work on a task once previous task is complete

● Help work to flow continuously and predictably deliver value

Software projects design

Kanban board - Wall of Facts

Value stream mapping

The (often wide) path to getting things done

Activities that get things done effectively

Let the board show issues...

V1.0.1, V1.0.2, V1.0.3, V1.0.4,

Build 1209Build 1221Build 1301

How did I build my Kanban

● Started simple with: Plan – Do – Done Used scrap of paper for initial design Built a simple board and started using it

● Evolved into Plan – Do – Check – Act Evaluated deficits in board and enhanced

● Used online Kanban So I dont need to cary a large whiteboard around Useful for distributed teams

Software development

Is something ready to work on?

● Identify completed work between seperate board lanes

● Spilt the study board lane into two First new lane is doing state Second lane is done / ready

Ready queue

Quick decisions

Having a ready lane show you what you could work on next

Prompts discussion as when something is ready to move from one stage / role to another

Start to see if there is a bottleneck if cards queue up in the ready column

Let the board run

So What is missing ?

● I have a Kanban board● I am breaking my tasks down into relatively

small chunks

● But I still have far too much to do...

Lets apply the WIP !!!

● To sudy effectively I need to focus● To focus I need to work on 1 thing

at once● To work on 1 thing at once I need:

Work In Progress Limits

How to decide what is right

Experiment !!

Map to resources

With one tester resource

1 tester, 6 devs pairing

Fast feedback across the board

Fast feedback

● Ltd WIP on Columns Board Goals

● Ltd WIP in column gives fast feeback between team roles

They know when there is a hold up Can discuss what the problem is Can try out things to see if it alivates the problem

Predictability

● Ltd WIP● Smaller batch sizes● Consistently sized tasks

Breaking down features, epics, stories

● Smallest responsible change

Let kanban help you be effective

● Work on only on one thing at once● Everyone responsible for priority changes

Even your manager

● If forced to switch, record and reset task to begining

Review ”task switching” overload

Pull system

What else can we do ?

Drop the Backlog

omnipresent sign of overload Useful for pushing back to the

management Bad for team moral

Tasks flow when team is in tune with value, opportunities are not drowned out

Defining the task card

● Set goal of task● Identify measure to check if goal reached

Code should pass all tests

● Identify resources needed to compete● Identify scope of work

refactor task into multiple cards if too big

Use both sided of the card

Classes of service

Experditing

● Visualisation for a high priority task Big red sticker Experditing lane Record other tasks being blocked

● Review why you get high priority task Consider it a constraint / bottleneck

Experditing lane

DevOps Goal keeper

Goalkeeper fields all issues

Rest of team allowed to

focus on a (bigger) tasks

Use visual indicator to show

who is the Goalie

Swap goalie regularly

Enhancing the board information

Blockers

Avatars / Calls for help

Pairing

Pairing does not have to be two

Different roles help share understanding of getting work done

Review your effectiveness

Effective daily standups

Avoiding status meetings● Details already there on the wall● Talk about something more useful● Opportunity to improve

What have I learnt yesterday ?

What do I hope to learn today ?

Kanban board - Wall of Facts

Understanding of Value

Understanding your company

Table stakes / foundations

Spoilers Differentiators

Accelerators

Benefits

Summary of Kanban

● Visualse work● Manage WIP● Engage with business

Shared ownership

● Encourage realistic priorities

● Helps you stay sane

● Show you are productive

● Deal with micro-management

Be as creative as needed

The first rule of kanban...

Thank you

Feedback & Refs

@JR0cket

JStevenson@atlassian.com

John@jr0cket.com

Please note: Very few bulletpoints were hurt during the making of this presentation

Lessons from Service Desk

● Variation of personal kanban Sticky notes at the side of the keyboard One priority at once Need business reason to change priorities

Record reason and number of times you had to revisit the task

Kanban design for study

Java Tech & Tools | Using a Pull System for Just-In-Time Development | John Stevenson

Technology

Stevenson | Die Schatzinselmedien.ubitweb.de/pdfzentrale/978/315/011/Leseprobe_l_97831501112… · Stevenson | Die Schatzinsel. Jubiläumsausgabe. Robert Louis Stevenson Die Schatzinsel

Kaitlynn stevenson behaviorism

Eric Stevenson Complaint

Pull Pull Pull - Weebly

The Commission found that Stevenson, by … 45834-9-II Unpublished Opinion.pdfThe Commission found that Stevenson, by refusing over ... called Stevenson Group Inc. Stevenson provides

Stewart & Stevenson

SMChap002 12e Stevenson

2008a Bpea Stevenson

11Stetler Stevenson

Aggregat planning stevenson

robert louis stevenson BED IN SUMMER By / robert louis stevenson

Java experiments for introductory cognitive psychology courses · Java experiments for introductory cognitive psychology courses ADAM K. STEVENSON, GREGORY FRANCIS, and HYUNGJUN KIM

MealsOnSteelArticle2011 Scott Stevenson

Java Tech & Tools | Continuous Delivery - the Writing is on the Wall | John Stevenson

Dev2/records.txt at master · Romiko/Dev2 · GitHub / Dev2. Code. Issues 0. Pull requests 0. Projects 0 Insights ... Angelle,Shearman,50: Asia,Stamp,65: Barbie,Stevenson,98: ... Adiana…

Don Stevenson

Stevenson Ranch Pack 499 Wednesday, Apr 19 Stevenson …files.constantcontact.com/be9591ae001/7e668b37-e4a2-4280-95e9-cb9e... · Stevenson Ranch Pack 499 Miercoles 19 de Abril Stevenson

Was sind „Reaktive Streams“? - java-forum-stuttgart.de · 2 Agenda Verarbeitungsparadigmen Pull- versus Push-Verarbeitung „Java 8“-Streams Concurrency-Model Grundprinzipien

HDR05 R1 Stevenson

Stevenson, r