Art work by firstname.lastname@example.org
My hat off to everyone involved!
Today I wanted to attend as many experience reports as possible but I made some exceptions.
Here are the sessions I attended today and some short snippets from the session. I was a bit distracted as I had my own talk in the afternoon
Szilveszter Farkas, Kalman Kemenczy
This was an interesting talk about how Prezi moved from a small team of developers with no real process and how the moved through Scrum to Kanban. Some of the reasons for moving to Kanban:
- Having problems meeting Sprint goals
- Production problems was making it hard to plan and commit
- Estimation was not very effective
Don’t be a Kanban slave
Don’t be a slave to your current visualization and process.Prezi treat Deployed and Launched as two separate thinks. The use feature switches to turn features on and off.
We measure everything
Prezi use dashboards with real time data and diagrams are annotated with things like when something is released/Launched. Application framework has simple hooks that makes it very easy to add new measurements.Prezi use a/b testing to drive part of its planning.Over all a great presentation.
This talk was about how E-Net turned to Kanban to be able to run multiple projects in parallel and putting the focus on getting things done. They even included all their administration process of the projects on the Kanban board. Exit criteria for a project was invoice sent.
The initiative to move to Kanban was a top down decision but the implementation involved everyone in the company. Everyone got the Kanban training.
People had personal WIP limits: 3 for planed work and 1 joker for other work
They had recorded a time laps video that was great.
This was a very interesting talk but I was distracted with my up coming talk, sorry Katherine
The part I think I picked up was:
Start with what you got, collect and bring measurements to the forefront and feed it back for improvements
You can’t just use hard facts and data and think people will make the “right” decisions. You need to take into account how people will react to that data and what their agenda is. If you can create an environment where people will treat hard facts, data and the different agendas and treat this just as the situation is right now. Use peoples natural curiosity to examine and draw conclusion from the full landscape of information.
The talk was interesting but there was way to much text on the slides so from time to time you got overwhelmed and got lost.
Nothing real new was presented that I haven’t heard from David before. But he where giving some more details in some cases. I was really looking forward to hear something new. Guess that was presented at Lean & Kanban 2011 Benelux
Predictability in software development requires good configuration management and deployment capability
Understand how work works. Collect process data before you make commitments
This was of cause my presentation and you can find the slides here
I was a little bit out of it as this was right after my talk but the talk did not have a main thread. The visuals in the presentation was adding more confusion than clarity. To bad as I thing Yuval is a great thought leader in the Kanban community.
The thing I really liked was the notion of Kanban being like a fractal. You can zoom in and out more or less as much you need.
You can find the presentation here
This was the second best talk of the day, just behind Kent Becks closing keynote. This was a very talk about Classes of Service and how to use them to level demand and handling risks.
Mixing up different kind of work for a team will make them more comfortable
Limit WIP – Leave choice upstream. Creating business flexibility and capability to respond to market changes
To much project WIP? Use the “A3 / Alignment” approach. Write a A3 for every project
Great visuals and great content.
This was the highlight of the day. Very good presentation of the different forces that will affect the way you work and how you organize your process based on the release cadence.
Over time we will see hourly, daily and weekly deployment cycles be much more common
The gala dinner was probably the best conference dinner I have ever had. Thank you Atlassian for the dinner and the free license. Also an inspiring talk about breaking your limits by extreme runner Norman Bücher