8/12/2013 by Sunil Upadhye
Each quarter we need to go through a funding gate review, and management always wants to know why user story cost cannot match with resource cost. I believe there are a number of reasons, and here I provide them along with suggestions for management. , , ,
8/9/2013 by Francesco Attanasio
In my previous experience as a technical coordinator, before embracing Scrum, I didn't have to go into the face of conflict very often, because team members in conflict had to deal with their issues by escalating them to their managers. I've realized that what ScrumMasters need is a "conflict management workout": a number of simple practices to keep in mind when trying to navigate conflict effectively. . . .
8/8/2013 by Glen Wang
I have summed up my self-management experience, my understanding and practice of Agile values and principles, and the Unity of Knowing and Doing philosophy into three reflective or retrospective questions. . . .
8/8/2013 by Timothy Korson
Six members of a development team I was working with were discussing pair programming and debating whether it was right for them. My advice to the team was in line with my general philosophy about new ideas: One learns more by doing then by talking. So I suggested that we try it for a few sprints, and then review our experience. . . .
8/7/2013 by Warren Jones
As the key stakeholder within the Scrum framework, the product owner is an essential player in ensuring that a relevant and quality solution is delivered. Typically, the product owner role is performed by the product manager, who has the vision and understanding of the end-user requirements to be able to effectively direct the team. If you find yourself working on a project with an "absent" product owner, or with a weak or ineffective product owner, then it is time to speak up.
8/7/2013 by Nitin Mittal
Burn-downs charts are among the most common sprint tracking mechanisms used by Agile practitioners. Though their application and usage varies, plotting burn-down using effort remaining is the most effective and efficient way of using burn-down charts. This article looks at . . .
8/6/2013 by Jorge Hernán Abad Londoño
Recuerdo como le he dicho a mis estudiantes de pregrado y posgrado mi reencarnación anterior, sí cuando fui/soy ingeniero civil, y que luego poco a poco desde los programas para cálculo estructural y matrices inversas, la realización de supermacros en visual basic para excel y la construcción de software para sistemas de información geográfica hizo que llegara al mundo que estaba destinado, el de los sistemas y más precisamente el del software. . . .
8/6/2013 by Srinath Chandrasekharan
In the last few years, Agile, and especially Scrum, has moved from the periphery of software development to the mainstream. Many organizations have already started to adopt Agile for all of their projects. Many of those who haven’t have plans to do so in the future. In this scenario, it is obvious to look at the challenges of scaling . . .
8/5/2013 by Carlos Silva
This has been a discussion in a LinkedIn CSPO group that I would like to share with other people. Simple article, but strong message. The question was, "Why not push the retrospective to the following sprint?"
8/2/2013 by Mirko Kleiner
Smaller and mid-size companies usually don't have their own R&D department. On the other hand, companies that are delivery driven often have "spare time," e.g., time in between projects that needs to be filled with valuable tasks. . . .