12/31/2013 by Justin Urbanski
It's not ideal, but sometimes it's reality: You look at your backlog and it's a mess. You don't know who's doing what and what is happening when. What should you do about it -- clean it up or start over? I recently observed this problem, and this is what we decided to do. . . .
12/30/2013 by Vijaya Devi
For those that try to move from traditional development models to Agile, one of the major challenges is forming self-organizing teams. How does such a team differ from the project teams in the traditional models? Are there any design principles or theoretical frameworks that can help us go about forming such teams?
12/27/2013 by Neil Potter
Scrum is a useful approach for managing software development projects. When performed correctly, it breaks work into manageable pieces and assesses technical risk. Some teams, however, run into trouble quickly because Scrum is blamed when it uncovers stinky issues. . . .
12/26/2013 by Brajesh Kumar
In a software company, it is common that the product owner role is given to the person who has previously worked as a programmer or who has peripheral knowledge about software. . . .
12/24/2013 by Haim Deutsch
When asked why William Ernest Henley's poem "Invictus" held such force for him, Nelson Mandela answered, "Because it gave us inspiration. To win you need inspiration." For me, this sentence had the effect of a slap on the face. . . .
12/23/2013 by Sudha Sivakumar
Retrospection is the most valuable and most important Scrum ceremony. Unfortunately, it is often neglected, and it can become a monotonous and boring ceremony. However, retrospectives can be made enjoyable. . . .
12/20/2013 by Manoj Khanna
In Agile, these eight identified wastes from Lean management are addressed throughout the life cycle of the product development. Let's look at them one by one. . . .
12/20/2013 by Ashish Sharma
Documentation is an important part of every system, Agile or otherwise, but comprehensive documentation as such does not ensure project success. In fact, it increases your chance of failure. However, the question remains: How much documentation is enough, and when should you write it?
12/19/2013 by Laura Klemme,Alistair Davidson
Software is difficult to get right. What you specify up front always seems to need to evolve as the understanding of a problem and users improves or as markets and competition change. . . .
12/19/2013 by Cristian Todor
I'd like to share my perspective on starting to believe that Scrum is the right thing to do in order to deliver high-quality products in a fast-paced environment. It happened some time ago, when I was still a developer. . . .