A few years back I’ve read The Goal. It was quite late in my agile life, so it wasn’t that eye opener everybody was talking about. It made sense, because I could compare my experience with software projects with the process of learning described in the book. Still, the book was about manufacturing. So I
Category Archives: agile
When I was at Agile Eastern Europe, I was interviewed by Ben Linders of InfoQ. This part is about “Agile product management and planning”. Also check out the first part on “Managing expectations in agile”.
Are your daily meetings effective? When you ask what people want from daily meetings, the answer is that they’d be short. Or Shorter. These answers usually come from people who suffer from long meetings and many other meetings in general. They want to just get back to their work. However, focusing on the length of
I was in a client meeting for presenting the new states of Product Backlog Items (PBIs) in Microsoft TFS. When I received the invitation for the meeting, I was excited and curious . Excited because the team I was working with, finally had enough with the pre-built states. Curious because – why is there only
In one month, I’m returning to Belgium Testing Days. It’s going to be a full week of work and learning. If last time is an indication, it’s going to be awesome, organized impeccably and a good place to learn about software development and testing. That’s for everyone, of course. Now, if you want to stick
Pawel’s post about Shu-Ha-Ri fallacy, came about the time I was reading the chapter about it in Lyssa Adkins’ book “Coaching Agile Teams”. And at that time I was thinking about learning and understanding. Coincidence? I think not. Shu-Ha-Ri is describes the progress in how we do practices: From doing, to understanding, to modifying them.
When we bought our house, we designated one of the rooms as “ the computer room”. It was kind of small office, with a couple of book shelves. Then, with the children, we’ve added more cupboards and shelves and computers. It was no longer the computer room, it was a storage room. “Where is X?”
Once upon a time there was a pool. It was in a club, and the club people loved the pool. This pool had 6 lanes. Each lane was wide enough for 2 persons to swim in parallel. Because the pool was popular, sometimes in certain hours, there were more than 12 people, and then people
If business analysis is where we come up with ideas, then product development process is the factory that makes the vision real. What did we take from agile and how is it different today from 15 years ago? The magic word of today is SCALE. And the king of Scale is SAFe. I’ve already written
Burn-down charts are awesome. They are part of agile’s set feedback loops. Take a look at a burn-down chart, and it will tell you if you’re on track or not. Here’s a simple example: Note that I haven’t used a unit on the Y axis. It can be story points or hours, or whatever unicorn