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.
12/9/2014 by Krishna Sagar B V
When it comes to personal improvement, we impulsively and subconsciously follow the process to change and to improve; but when it comes to teams, we struggle to put it all together. . . . It takes a good ScrumMaster and a collaborative team to conduct effective retrospectives.
12/8/2014 by Ebin Poovathany
I read this quote again today: "First they ignore you, then they laugh at you, then they fight you, then you win." . . . This statement has impacted me very deeply.
12/8/2014 by Bobby Mathew
With the advent of Agile/Scrum methods in project execution, many of the . . . key skills that a project manager was singularly proud of have gradually become less crucial.
12/4/2014 by Sameer Chudaman Patil
Here are some guidelines I would like to recommend for when you are ordering your backlog.
12/3/2014 by Athresh Krishnappa
Traditional approaches to offshore development are based on plan-driven methods with big-bang deliveries. Now, in the new age of Agile development practices, this needs to be adjusted to support faster delivery cycles and enable a highly collaborative environment for multi-site, multi-vendor development teams -- a big challenge.
11/24/2014 by Ravishankar N
While executing Agile projects, many Scrum teams use a "hardening sprint." . . . This article maintains that a hardening sprint is not a good idea and highlights why.
11/21/2014 by Vikas Gupta,Pallavi Kelapure
This paper suggests different approaches to speed up ERP implementations and support based on scope of work, standard package fit, and organization readiness.
11/20/2014 by Meghana Niranjan Parwate
Agile test automation is the application of the Agile development principles to test automation. Accordingly, there are some principles of Agile test automation. . . .
11/20/2014 by Deepak Joshi
Any business requirement that needs to be formulated in user stories can be best justified if the writer knows the user roles for which the requirement will be mapped. To identify users, user role modeling is important.
11/19/2014 by Karthik Ananth
Often, we need one person to be "weird" to protect the team. I believe it's the duty of the ScrumMaster to be weird in order to save the team from distractions and to educate everybody on various aspects of the system. I would like to discuss a few of these "weird" but important tasks that a ScrumMaster should perform.