Read about the experiences and ideas of Agile colleagues around the world, and share your own thoughts here. You can also visit
, which features blogs by experts in the fields of Scrum, Agile, and the broader business world.
6/29/2012 by Lee Thomas
I started in the IT industry back in the early 1990s, working for Ford Company in the U.K. Since then I've observed with interest the trends in the skill set required to be successful in our industry.
Looking back, I realize I was extremely fortu...
6/27/2012 by Andreea TOMOIAGA
Software projects always take place in an organizational context, and their objectives are in line with organizational goals. Similarly, the sprints that build a project's road map need to have goals that are in line with those of the projects.
6/26/2012 by Christophe Le Coent
We can all agree that shared responsibilities are important on a project, but we should also have clear accountability. Someone must ultimately be answerable for the correct and thorough completion of the deliverable, and that should be a unique i...
6/26/2012 by JITENDRA SINGH GOSAIN
Daily stand-up meetings play an important role in the success of Scrum process-based projects. Most of us know this, and we know how they "should" be conducted. Yet, time and again, I see these meetings go astray. Here I hope to review the problem...
6/1/2012 by Mahfoud AMIOUR
In Scrum, each sprint produces an increment, which is a partial and potentially releasable product. To be releasable, the increment must meet all acceptance criteria and pass different categories of tests. Consequently, each sprint should consider all testing activities required for a releasable product. Unfortunately, during my work on different projects, I have observed that many teams focus only on a subset of testing activities during the sprint.
5/23/2012 by Davide Noaro
Sometimes, when testing user stories in Scrum, there's a final Waterfall interaction to deal with. The scenario I present here is based on this situation: a Scrum process with an interaction of sequential phases at the end of the process to (re)test the whole developed functionality. These sequential phases are mandatory for our organization, which follows a Waterfall process for the releases of the product. So, for the moment at least, we have to deal with this — and my experience is that we aren't alone.
5/21/2012 by Albert Arul Prakash Rajendran
Note: This article is based on a Scrum Alliance Google groups thread called "How to apply scrum in a mixed feature development and SLA-bou[n]d bug fixing team." I have compiled most of the solutions that were provided in the thread. Not all parts ...
5/18/2012 by Uday Shete
However exhaustive and meticulous your current employee appraisal process is, chances are you aren't pleased with the outcome. The primary objective of a performance appraisal is performance improvement, starting with the individual and rolling up...
5/16/2012 by Utpal Vaishnav
Typically, when an organization starts using Scrum, the person chosen to play the role of ScrumMaster comes from some sort of managerial background. The organization expects that the manager, the so-called "Master," will get the Scrum project deli...
5/14/2012 by JITENDRA SINGH GOSAIN
Agile processes are gaining in popularity, which means many project managers are following them for the first time. Based on my own experience, I've developed a sort of primer for PMs starting out on Agile projects. The key points are as follows: