- Carlos optimizing locally
John Little: Little's Law
- Cycle time = WIP / Throughput
- CT: how long it takes one item to go through the system
- WIP: how many items are in the system at any time
- TH: how many items are produced per unit of time
- Question: prioritized, but best way to make money is predictability
- Lesson: the more money you score on the first day, the better
- Tip: optimize the bottleneck for test
Things that plague IT ops
- best practice: put pink sticky on it to show blocked tasks: stop the line and swarm@chadloder: RT @RealGeneKim: OH: "Tried using OpenOffice for 1 year. It was like using Trabant of office apps. Awful."
- variable task size
add blocker is business requirement: blocked vs. swarm: (add to novel?)
Example 2: managing dependency risk
- moving Waiting For to bottom
- Ian Carroll:
Example 3: tracking your blocked tickets on other people's kanban boards: attend their standups, but on their kanban board
Example 4: showing risk of dependencies
- Pattern: when every person has their own swim lanes: indicates intense IT ops specialization emergent property
- once is an anomaly, 2nd time is a coincidence, 3rd time is a pattern
- local optimization vs. optimizing the whole: take responsibilty for self, but not the whole
- 5 were specialists, 2 were generalists (turned into floaters)
- To Checklist: what happens when specialists leave? what was their demand? What work are they doing?
Pattern: "The Goalie: fields small interrupts, rotates weekly, expands knowledge base, gains flexibility in team"
- Creating goalies reduces specialization, increases generalists, increases flexibility. Nice.
- Brent never documented everything: critical tasks, too busy to meet, fingers flying too fast
- Put up flag on people's desks: "I'm the interrupt person"
Variable task size
- Transaction cost vs. value
- Is overhead of creating ticket greater than the value of completing ticket
- "I don't want to spend 15m creating ticket for 5m task"
- maybe use different size sticky notes
- David did work with neuroscientists: looked at brain plasticity
- if less than 30 min, just do it
- dependencies, only Brent can do it, visibility of small tasks in reporting
- Flow for today
- Allocate 2 hours: 1-3pm, just for tiny tasks: do as many ask we can
- Password resets: lots of work, but it often drives improvement and automation, because doing it sucks
What's the piont
- show the risk
- show the types of risk
- track work to get visibility
- OH: "I have brief moments of clarity, surrounded by huge chasms of sheer panic"
- "CEO inconsistent, no one knows what's to do"
- "Can't argue with number of magnets (resources)"
- "Love smiley face with each engagement"
- OH: "Every task in our org needs these 2 engrs; if all $$ disappeared from bank, it'd still escalate to them" Haha
Betsy's board (?)
- 4 month deployment cycles
- Transaction cost: touch time
- Mike Burrow's: resource of product portfolio management
- Developers buried in marketing: one is a Java developer with title of "Intl Program Manager!"