Below is a draft of an article I've been working on. Any comments are welcome! ------------------------------------------------- Specialization in Scrum is a hot topic for already many years. It pops up at every Scrum course I do. It is an important topic and is relevant for a new team
Definition of Done is the agreement between Product Owner and team. As ultimate goal, team is delivering potentially shippable product increment every sprint, thus, your Definition of Done shall be equal to what's required to make your product increment potentially shippable. However, your current Done may be only
In Scrum, there are release commitment and sprint commitment. Though we use the word of commitment all the time, it is often not clear what it means. Let's first look at the commitment we make towards customers. This happens at release level. In some situation, we need to
Last weeks, I've been able to spend time with my good friend Lasse Koskela. He was in Singapore for three weeks to work together on a new "Scrum Developer" training. During the creation of the training, we came across the "repair manifesto" which inspired
An error message I just don't want to forget. Today, I got this error message in some code: error: invalid preprocessing directive #eror (do read it carefully)
Feature teams are an important part of scaling Agile and Scrum to large products. Me and Craig have written extensively about feature teams in our two books. Till now, the 'best' description about feature teams was probably the Feature Team chapter of the Scaling Lean & Agile book.
A friend of mine, Sami Lilja, send me a photo of his son studying how to scale Agile and Lean development (below). Sami recently started a new company called Kollabora. Hope he has much success with that, perhaps his son will be the youngest scaling agile & lean expert in
I've added mocking support to the CppUTest C/C++ unit testing framework. Id like to clarify why I've added it, why I've added it the way it is and how you can use it. Why mocking? I won't cover why mocking and
Hmm... its been a while since I posted here. I'll try to re-start this a bit. We also moved the blog to the new odd-e server, which clarifies the new look. The location should be the same though. Earlier this year, I was doing a keynote talk at
Yesterday, I was browsing some of the mailing lists and bumped into some posts about "fractal processes." This wasn't the first time I heard about them, people talk about them in the context of Extreme Programming and Scrum and more modern methods such as Kanban all
I wrote an Amazon review of a new book called "Birth of Lean". You can find the amazon entry here I copied the review on this blog. Think its worth reading for people interested in Lean: -------------------- The Birth of Lean is a collection of six interviews with
An interesting post
Last weeks I've been working on some legacy code. Most of it has been refactoring, but we rewrote a couple of modules to we test-drove these... of course. The TDD cycle is so slow that it made me realize a technique I'm using... but wasn'
Craig and me changed the "top 10 organizational impediments" in an article and published it on ScrumAlliance. We added two points of ourselves. You can find it here.
In Bangalore, on my way back to Singapore. It is another late night flight. I hate them and consider the new Bangalore airports to be perhaps one of the least interesting airports in the world. Still an hour before my flight leave, hope I can stay awake. Last weeks I&
Michael Feathers came up with an excellent list of must-read papers from programmers (he is bored, his head it too heavy). You can find it here: http://michaelfeathers.tumblr.com/post/81489281/10-papers-every-programmer-should-read-at-least-twice There were some papers I didn't know, but also some papers I'd think