CategoriesAgile Automated Testing build quality in checkstyle configuration continuous integration create knowledge defer commitment Definition of Done deliver fast development dynamic languages eliminate waste Functional Programming groovy hudson Lean Multi-Paradigm-Programming NoSQL optimize the whole pair programming programming style respect people Scala SCRUM Scrum master sprint planning tdd test-driven-development testing Uncategorized UnitTests User Story value stream welcome
Error: Twitter did not respond. Please wait a few minutes and refresh this page.
Daily Archives: November 8, 2011
Sprint plannings in Scrum sometimes take long; even when you have all the Stories ready for sprint and estimated. Reason being the team still need to break down stories to tasks, and the Scrum master needs to calculate the capacity and compare the total hours of broken down tasks to the capacity available in order to find out whether the team are committing well, under committing or over committing in order to further negotiate the commitment with the Product Owner if required.
All of this are basics and well accepted, but does it make sense to make the team to break down all the stories right at the beginning of the Sprint – during the planning? Most of the Continue reading