|Written by Sudheer Raju | Wednesday, 08 February 2012|
A common question that a Scrum coach would face while transitioning an organization into Agile is “Why story points?” While this question appears very trivial, people seem to ask this question very seriously. Before we attempt to answer the question let’s have a quick look at what the story points are?
Over 10 years and I see some posts being written, quite interesting saying we have understood agile and we are moving towards aggressive adoption, some stating that it's become routine, boring and probably agile is on the decline. I liked a post in particular from Planbox blog what appeared to me as a declining agility Vs. evolving agility.
|Written by Sudheer Raju | Thursday, 19 January 2012|
Summary Review: AgileWrap is a simple, easy to use application lifecycle management tool with just about required features to manage agile projects. The design of the product core is a grid that very effectively handles every aspect of application lifecycle and finds itself to keep it simple than embed complex customization or integrations.
The daily standup meeting or scrum meeting presents the team with a regular opportunity to synchronize development activities with the iteration plan and to check and reflect on the progress of the team’s commitments towards the iteration goal. As a forum for communication and feedback, the team members co-ordinate their work and make a commitment to the team about what they aim to achieve in the day. They also identify any difficulties and obstacles to progress. The meeting is not intended to generate solutions nor remove obstacles.
|Written by Vin D'Amico | Wednesday, 04 January 2012|
|Written by Sudheer Raju | Tuesday, 03 January 2012|
|Written by Sudheer Raju | Saturday, 31 December 2011|
You Kanbanized your development process and setup a perfect workflow. You see the flow and feel its power. You even measure cycle time and want to reduce it. But it is not as easy as expected. Some problems in your development process are hard to find and are revealed on team level.
One of the first hurdle that any projects comes across is ability to gel as a team to deliver projects. Specifically when the teams are adopting agile where the key focus is around people and teams. The shift in ways of working from traditional to lean methods puts the teams at great discomfort to start with and often determines if you are able to adopt to agile or not.
All people working in an agile environment should reflect on the principles behind the agile manifesto from time to time. What do these principles really mean? What impact do they have for my daily business? Does my habit follow these principles? There's a nice exercise for agile teams to summarize each of the principles down to 3 or 4 words. An agile team needs to have a shared understanding of the principles and what they imply for the team's behaviour.