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/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.
4/16/2015 by PraveenKumar Prem
Without a shift-left test approach -- early and often -- developers and testers find it difficult or impossible to find defects until system parts are integrated in a system test. Why can't we reap the benefits of Agile?
4/15/2015 by Lisa Fineberg
Spring has sprung. Flowers are in bloom. Clocks have been adjusted to reflect Daylight Savings Time. All of these little indicators point to the undeniable fact that May the Fourth is just around the corner. . . .
4/14/2015 by Eduardo Hernández Rangel
Even a standard user story is sometimes difficult to obtain from the stakeholder, because they have a vague idea about what they want. In such cases, the "Five W's" can be useful for writing user stories with complete and coherent information.
4/13/2015 by Krishna Kumar
Have you ever assessed the way your team follows Agile/Scrum? We have. Beforehand I thought we were working to a higher standard of Agile/Scrum. But I felt the opposite after seeing the assessment results. . . .