Tag Archives: visualize workflow

Visit at Cluj Napoca

My old friend Victor invited me to Cluj Napoca, Romania to talk about software development in practice. There were three talks in the morning at his company evoline and a fourth talk late afternoon at the local meetup group.

We started the day with an introduction to Kanban, because the audience knew about Agile, but Kanban was something new, and additionally we needed it for the maintenance-related presentation:

After a short break we continued with a longer talk about maintenance and how to use Agile, Lean, Kanban and leadership techniques in order to stabilise a maintenance situation:

The last presentation was about how to use Agile techniques without saying Agile:

My talk at the meetup became a bit longer than I expected, but we had – at least I felt like that – a great discussion how the software development process evolved at Digital Natives – my current company – and, uniquely, we talked about what we were doing right and where we failed:

I promised a list of books worth reading. So here are they in a recommended reading order:

  1. Taiichi Ohno – Toyota Production System
  2. Henrik Kniberg – Lean from the Trenches
  3. Daniel H. Pink – Drive
  4. 37 signals – Rework
  5. David J. Anderson – Kanban

Even though it was a long journey and an even longer day, I enjoyed it very much. The audiences were great, and I got some very usable feedback on the style and content of the presentation (I’d like to specially thank Dragos, Cătălin and Victor for the detailed and more personal feedback), so I can improve my future talks. My next talk will be at my former employer Ericsson, and I’m going to talk about leadership and measurements.

Thank you folks for the possibility, it was my pleasure!

VN:F [1.9.17_1161]
Rating: 9.5/10 (2 votes cast)

When Expand and Collapse Got Beaten

Today’s post is an instructive story about mixing various good patterns and ideas. They are very useful separately, but when one uses them together, they may lead to problems which nobody wants to deal with at all.

We found several different defects in a certain feature, and in order to reduce handover costs I collapsed them together to make an “umbrella defect” (defect1+defect2+…defectN) and put it into our Queue. When my colleague started to work on it, I was quite happy with the result: less handover costs less context switching and more focus on a faulty feature. It was really nice until our deployment day came. Or Kanban board and version tree looked like this:

The mentioned umbrella defect appears as ‘UD‘ on the Kanban board, and it covers ‘UD1.1‘ and ‘UD1.2‘. Based on our Kanban board, there is no impediment to the deployment, but right before the deployment we realized that not everything we wanted to deploy had been tested since we were using one-track. One-track means that we don’t have branches, labels or tags, we just have the trunk where we have our latest version. One-track is an excellent thing, but it seems that it doesn’t work well with collapsing.

Read more »

VN:F [1.9.17_1161]
Rating: 0.0/10 (0 votes cast)

Our Detective’s Blackboard

My colleague Attila and I had an interesting discussion several days ago:

- Zsolt, I feel that sometimes we are missing the big picture.
- That’s not cool, and it may explain the high number of work items moved back.
- Maybe, but can we do planning together again? I miss it.
- Sure we can, but no regular planning meetings, right?
- Of course not.

As my friend @keksz_i pointed out, regular planning meetings aren’t that effective and I’m also not a great fan of them: talking to the product owner is a brilliant idea, but the traditional task breakdown is just a tremendous waste of time. After our discussion, it was clear to us that we had to bring the planning back, but we needed something new, something effective. So we came up with the following detective’s blackboard for our next feature:

It is drawn on a large piece of paper and hangs on the wall right next to our Kanban board. It has all the information we need in order to do our work: the big picture, how our user interfaces will look like and how they will communicate with other parts of the application. Additionally, we also have work items, prioritisation, test plan and estimation.

Read more »

VN:F [1.9.17_1161]
Rating: 0.0/10 (0 votes cast)

Brown Bag Lunch Talk: Measure and Manage Flow

This Tuesday, I had my first brown bag lunch talk at prezi, where I talked about measuring and managing the flow. Here are my slides:

VN:F [1.9.17_1161]
Rating: 10.0/10 (1 vote cast)

Meetup: Kanban in 5 Minutes

Yesterday evening I gave a 5 minute long lightning talk at Bp New Tech Meetup about Kanban focusing on the measure and manage flow principle.

Here are my slides:

Thanks for coming and listening to my talk!

P.S: since five minutes aren’t enough for presenting the whole principle, I’m going to write a post about it soon.

VN:F [1.9.17_1161]
Rating: 10.0/10 (1 vote cast)