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.
1/4/2016 by Sayi Sarat Chandra Parvatam
Before we understand why we need to make a shift in the project-orientation paradigm, let us consider the preexisting Waterfall model, reasons for its existence, and the problems with applying it.
12/30/2015 by Amit Kulkarni
I have lead many projects in Scrum and dynamic systems development management in Europe and have observed some common mistakes managers make in writing a fixed-price Scrum contract.
12/29/2015 by Jimmie Flores
To guarantee the success of a project, it's essential that everyone involved — from the development team to the customer, and everyone in between — is in the loop at all times.
12/28/2015 by Reuben Salisbury
Let's face it, sprint planning is occasionally boring. Yet it's important that the team remain motivated and engaged. In this post, we'll look at how group presentations can help.
12/28/2015 by Boon Nern Tan
A Scrum ecosystem is typically made up of three main roles that interact as a community. If one role is missing, the absence might cause the ecosystem to become unbalanced or even corrupt.
12/24/2015 by Vishal Venkatesan
Agile is widely practiced widely, but the focus is still at the team level. Challenges include scaling, handoffs, and innovation. We successfully used Spotify's framework to address these and other sticking points.
12/24/2015 by Sayi Sarat Chandra Parvatam
Whether you are referring to the Waterfall or the Agile method, it is all about teamwork. Regardless of which model you adopt, the ultimate goal is to get the best output from the team.
12/23/2015 by Philipp Flenker
I recently asked this seemingly simple question at a gathering: What do developers gain when teams self-organize? To my amazement, I did not get one satisfying answer.
12/23/2015 by AMLENDU CHOUDHARY
One of my regular challenges is how to estimate a user story by using the number of days or hours necessary to complete the work.