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.
4/30/2015 by K Pawan Kumar
To get developers and testers on the same page, it's imperative that an appropriate "handshake" is done between developer and tester at the beginning of the project, and it should continue throughout the sprints.
4/29/2015 by Rajat Bhalla
Let's look in depth at the steps of a sprint planning meeting, what makes them fruitful, and the Five Commandments for successful sprint planning.
4/28/2015 by Bruno Silva
During an Agile transformation, fear may make failure come true -- an organization may begin to doubt and discredit the changes.
4/27/2015 by Ankush Sabharwal
Why do we size stories in Agile? Here's a look at why, and how to use relative sizing.
4/24/2015 by PraveenKumar Prem
One of the keys to successful Agile software projects is considering testing at the beginning. And one way of achieving this shift-left approach is to use behavior-driven development (BDD).
4/23/2015 by Sriramasundararajan Rajagopalan
The zeal for "zero quality error" competes with maintaining profitability on product development and project management initiatives, when organizations are attempting to do more with less.
4/22/2015 by Ravishankar R
Let's take one of the accepted (if not explicitly stated) Agile values and see how the developer in an Agile environment supports it. . . .
4/21/2015 by Anand Vyas
In traditional project management models, we know projects revolve around the triangle of scope, cost, and time. How do we use this in Scrum?
4/20/2015 by Sumit Sharma
Is your team facing difficulty in forecasting when projects will be completed? Are there large numbers of unestimated user stories in the product backlog? Does the planning meeting last several hours and is it full of confrontation?
4/17/2015 by Vikas Jain
One of the fundamental Agile values is, "We value responding to change over following a plan," which has sometimes been misinterpreted to mean that we don’t need to plan an Agile project. Nothing could be further from the truth.