Skip to main content

Posts

Showing posts from 2014

Challenge best practice?

Idea of best practices is a seductive but dangerous trap. … The great danger in “best practices” is that the practice can get disconnected from its intent and its context and may acquire a ritual significance that is unrelated to its original purpose.

They also inhibit a “challenge everything” culture and continuous improvement—a pillar of lean thinking. Why would people challenge ‘best’?

Agile: Common sense or misconception?

In our many discussions  we hear the advice that we should use our common sense to tackle the problems, But how good is our common sense? Are we willing to change? Recently i had a discussion with a colleague on an agile practice. This person was not so willing to change because  the common sense dictate  otherwise.  In this fast moving world and always change constraints change is inevitable, most of time we will have to challenge and change the age old common sense to bring the continuous change/improvement.


Taiichi Ohno, the father of the Toyota Production System, said, “[...] misconceptions easily turn into common sense. When that happens, the debate can become endless. Or, each side tried to be more outspoken than the other and things do not move ahead at all. That is why there was a time when I was constantly telling people to take a step outside of common sense and think by ‘going beyond common sense.’ Within common sense, there are things that we think are correct because of …

Why do we need definition of start (begin)? How is it different from Definition of Done?

We all know about definition of done. It defines a set of conditions which should be satisfied by the feature team during the sprint execution for each Product Backlog Item worked by them. Unless all the conditions are met, the PBI’s won’t be marked as done. This can be called as the exit criteria for each PBI or user story.
Usually apart from the team & PO, the organization and other stakeholders also play a big part in creating them. A well-defined Definition of Done ensures that all the PBI delivered meets the standards and if required can be deployed. As team maturity improves this definition also evolves.
For every exit criteria there should be an entry criteria. I have seen many lazy Product Owners (& scrum Teams) who don’t do a proper job of backlog grooming.  Because of this there will be lot of ambiguity about the upcoming PBI’s. There will be constant churn producing a lot of waste.  Sprint planning will end up in failure because team won’t know how to create tasks…