I'm frequently asked whether I got tips for how to start an agile adoption. A lot of people are looking for the ten step magic recipe that will magically transform their organization to an agile organization. I tend to reply with the 'bad' news first: Every
Everyone knows it! Nokia is *not* doing well. The new Windows strategy is not popular with the (geeky) public or Nokia employees. Recently, a couple of blog posts and comments have been posted about Scrum, Nokia and "The Nokia Test". I don't want to criticize the
Project management is done differently in Scrum Project management work still exists when adopting Scrum. Traditionally, project manager plays key role for project management work, and it is done in a centralized manner. While in Scrum, project management work is done in a distributed manner, split among Scrum roles -
The last month, I've come across this issue several time, to my surprise (because it hasn't come up in the years before). If you are wrapping tests around legacy code and the legacy code has a C-style assert in the production code, then what do you
Review posted on amazon.com: I was looking forward to David Anderson's book. While I wasn't enthusiastic about his previous book: Agile Management, I liked his new work and the balanced view on change he is promoting. It all made me curious. I've not
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