Unfortunately, I won’t be able to present at DevGeekWeek. But I do have a slide deck I’ve prepared for it. It was supposed to be presented at the Application Life-cycle Managemenet (ALM) track. And since, we’re dealing with experimentation, let’s use the deck for an experiment: Would you like to attend a webinar about this? Let me know
At Agile Israel conference, I was recruited to a “Hit The Experts” panel on engineering practices. Ok, I didn’t put too much of a fight. Most of the questions were not of the engineering nature, though. One of the questions went like this: We’ve adapted the Spotify model, and now there’s no specialization, expectations from
I usually make fun of the “become a scrum master in 3 days”. I mean, what can you learn in 3 days? Glad you asked. Once a year or so, I get a chance of going through an exercise with my army unit. These few days are plentiful of agile post material. I’ll try to cram
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
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?”