4/30/2014 by Raju K
After getting introduced to Agile, and while working for the last five years on Agile projects, I have developed a strong and disturbed feeling toward the word "resources." Let me tell you up front and frankly that I am not against the Human Resources department. But the word "resource" troubles me a lot. . . .
4/30/2014 by Steven Ziselman
Change is inevitable. The journey from comfortable to new, however, is never easy. The journey from Waterfall to Agile is no less bumpy. . . .
4/29/2014 by Madhavi Ledalla
This article highlights the importance of one of the key ceremonies of the sprint, the retrospective. It then goes through some of the common challenges teams face while holding retrospectives. It also puts forth a few thoughts on how to make these reflections thought-provoking ones!
4/29/2014 by Ahmed Hammad
There is a difficulty tracking many Scrum teams in any typical organization. Although each Scrum team has its own work area with boards and charts, it is easier for managers to look at all teams and sprints in one place. . . .
4/28/2014 by Marmamula Prashanth Kumar
Agile/Scrum is the current buzzword for obvious reasons, such as its self-organized teams and its empowered, motivated individuals working toward a common goal. Miracles are bound to happen. But to realize the real benefits of Scrum, the transformation of the team should be complete in all aspects. . . .
4/25/2014 by Jai Singhal
This article discusses how Scrum is Lean and supports all seven Lean principles. . . .
4/24/2014 by Bassem Hamdi
The plan-driven model has been effective for projects in many industries. The world of software engineering, however, is relatively new . . . and when we attempted to apply this model to the world of software it was less successful. . . .
4/24/2014 by Rishi Devendra
In the sprint retrospective, the team discusses the just-concluded sprint and determines what could be changed that might make the next sprint more productive. The sprint review looks at what the team is building, whereas the retrospective looks at how they are building it.
4/23/2014 by Sherif El-Rabbat
During the transition of a company from the traditional method to Scrum, we faced a lot of problems in changing the culture and mind-set of the development team, due to their long-term dependence on command and control as used in the traditional way. The symptoms of this problem were clear in their attitude during meetings. . . .
4/22/2014 by Saugata Chatterjee,Rahul Gupte
A high-profile software development project supporting a critical business imperative had been sitting on the shelf for a few months. It was awaiting a new crew to take ownership and successfully sail it to its destination. . . .