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.
10/24/2012 by Christophe Le Coent
A common perception when working in Agile is, "Welcome changes over following a plan." In the Agile Manifesto, however, the phrases "Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage" still mean you need a plan to begin with.How can we express the product backlog so that we can easily provide enough planning information to management without compromising on Agile principles?
10/22/2012 by Juan Banda
To the foreign eye, a PMP is in one corner, and in the opposite corner we have an Agile project manager. This seems to be so because each advocates a different vision of how to run a project, and even a different conception about what a project really is. The PMBok Guide has been the source for years in project management, but in the last decade Agile has gained more popularity and now seems ready to challenge the champion for the belt.But is it really true that this two are opposed, or it would be possible to find common ground? Don't miss this fight, which doesn't promise knockouts but instead may go the distance.
10/3/2012 by Elinor Slomba
Couldn't make it to Scrum Gathering Barcelona 2012? Read about what CSM Elinor Buxton Slomba has to say about attending our sold-out event.
9/21/2012 by Brent Reid
Traditionally, most systems used to track defects and work items on a development or maintenance program include the concept of priority. James O. Coplien addresses the topic of priority in his 2011 article "It's Ordered — Not Prioritized!"I agree with Mr. Coplien that the product backlog should be ordered, not prioritized — and here I present slightly different reasoning to support the same conclusion.
9/18/2012 by Victor Szalvay
Technical debt describes the cumulative consequences of cutting corners in software development, but it escapes the attention of many project managers as they focus on scope and schedule. That’s a mistake because it impacts both. Here are questions to help you ascertain the real state of technical affairs.
9/13/2012 by Paul Pazderski
Transitioning toward Scrum practices isn't easy for every team. I've used a visual image that I call the Scrum team scorecard to help. It's a one-page "snapshot" of the level of transformation of a project team into a Scrum team. An independent o...
9/13/2012 by Michele Sliger
There’s going to be a lot more talk about Agile now that the Project Management Institute has introduced a new certification program for Agile Project Practitioners. Let’s clear up some initial confusion and look at what Agile is and is not, and why you should care.
9/11/2012 by Skip Angel
Organizations and teams must come to understand why they need agile before choosing a methodology or tool to implement it. A mandate alone will not work. It is the overarching goals, values and principles of Agile that must ultimately guide teams in the adoption and adaptation of its practices.
9/10/2012 by Rahul Jain
In the software industry, professionals hold different views on processes. Some say processes are bureaucratic and rigid, making their lives difficult. "Why in the world does a simple software installation have to go through X number of approvals when I have such an urgent task at hand?" Others (mostly members of organizational process groups) relentlessly endorse standardized processes and talk about how the organization could be benefited by the data collected from following those processes. Project teams, though, are often unconvinced, since what the data says and what the customer says can differ.
9/7/2012 by Brian Barr
Projects, projects, projects! You know you don't like them, but do you know why? Is there a better approach? In this article, I'll outline why we've chosen to be project oriented in the past and why pulling "the Big Lever" toward release orientation is so important in making the move toward Agile solution delivery a real success.