Who is talking?


Top 10 Hot technologies

over 12 years ago | Lalita Chandel: My View

While browsing, I came across an interesting article which talks about 10 hot technologies for 2009 (ex Cloud Computing, Green IT.....etc )http://technology.inc.com/managing/articles/200812/technologies.htmlNice read !

Are your Scrum teams getting stories "done" done?

over 12 years ago | Biju Bhaskar: Thoughts on enterprise application development and more...

I have been attending lot of scrum meetings recently and I happened to attend a Sprint review meeting of a high performing team recently. The team claimed that they committed 17 story points and delivered all. However there was a caveat to that…. the stories were only 95% done … “some minor UI tweaks and some final testing are pending”. Usually this is a red flag for me…. there is a good chance for this team to start developing a bad habit, and end up with technical debt (or lower product quality). Sticking to “done” list religiously is key for a Scrum team’s success. They should not call a story done unless it is really done done. Let me try to explain why…A good analogy would be Toyota Production System. The concept of any employee being able to stop the line in a Toyota plant is a key part of Toyota’s quality strategy. In traditional manufacturing settings, management will pressure employees to keep the line running at all costs -- quantity over quality. If defects are being made, keep the line running and you'll sort them out at the end of the line (through inspection and repair). It's a failed quality strategy because it ultimately costs more and potentially leads to more customer dissatisfaction than if you had just stopped the line to immediately fix the problem and prevent more defects from being made. That also creates a behavior change among the employees that assures quality through out the system.Similarly Scrum teams should avoid calling a story done if it is not really done done. If it is okay in one sprint, it becomes okay in couple of sprints and slowly could become a habit and the team will end up with technical debt (or low quality application). I know it’s hard to not give credit to the team who has done 95% of the hard work. They may hate you for couple of sprints… but they will surely thank you at the end of the release for helping them become a high performing team. Thoughts?