softest bullet
TRANSCRIPT
Soft BulleT
Neil [email protected]@g.a.neil.smith
Softest Bullet
Making change at large orgs is difficultChange normally comes from TOP downNormally underlying culture of getting things done despite things
Hey god how ARE THINGSHI NEIL HOW ARE YOUWe are talking today about effective change management techniques, I know you have some that are quite effectiveWELL I HAVE FOUND THAT billions of people love to be threatened into submission and obedienceGreat so do you have an example that I could use?THOu SHALT COMPLETE YOUR SPRINT IN TWO WEEKS OR you will go to hell
4
PEOPLE want to do their best
Despite the world of crazy they live in they prefer cray cray over change
You can REALLY ONLY move things baby step by baby step
So many attractive ways to improve come out of LEAN thinking
Often hear through the experts unless you have executive buy-in change is impossible
Controlling the WATERHOSE
Empowering and Improving Teams
Understanding Value
Things I have triedEnhancement StreamMap the value streamkanbanclean and tidymeasurementlearning and ownershipProjectsunclear requirementsurgent projects with fixed deadlines
LUCKILY PEOPLE HAD Actually DONE THIS we love what we create
But maybe it all reduces to Lean Coffee?
Having a place to start is great it doesnt have to be perfect Starting is the most important thingNext steps done in small measures
Work the value stream to get things doneCreate BOARDI luckily had one with WIP limits already (all violated)
LESSON We dont like to give up on task but we have to
ONHOLDX
LESSON UAT signoff is hard
LESSON Help your team respect their WIP limits
LESSON Your progress is even slower than you thought possible
LESSON As a team you will come up with ideas for improvement, as a team you need to implement them
19
Questions about running enhancements
20
Urgent but Unknown just in time requirementshow to handle working through clarifying requirementstraditional waterfall techniques = long timelineusing scrum with ba team working with or ahead of devs
LESSON Urgent small projects work great with Kanban
work with team to create known backlogmake best guess on timelinesthrow into simple kanbanmonitor throughput compare to original and communicate
22
Reporting
agggh microsoft projectplans can only be at more generic level, not at low level of detailuse kanban under that level and report on what is left using original high level guessesrisk and issuesput them into board to monitor mitigations
23
Questions about running smaller projects
24
Small change is possible