February 2019 M T W T F S S « May 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
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.
Category Archives: Definition of Done
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
software engineering, java, j2ee, jboss, mysql email marketing, blacklisting, smtp, rmi, jms, crm, friends, travel, munich, specification, review, coding, esp, project management, gantt chart, matchmaking, tracking, pixels, company event, travelling, hibernate, spring, tomcat, invoker, redundancy, scalability, data complexity, performance, partitioning, sharding, activemq, broker, soap, http call, queue, strategy, social networks, facebook, lean, agile, architecture, scrum, scrum alliance, agile manifesto, sprint, continuous integration, hudson, static code analysis, transparency, communication, iteration, definition of done, spm, srm, user story, failure, success, confidence level, pair programming, retrospectives, groovy, grails, nosql, mongodb, rest, jersey, value stream, london, development management Continue reading
What is a Definition of Done?
Definition of Done is a crucial element of a successful scrum software development. When defined and followed, makes sure that when someone says that a task is done. There is an explicit understanding what it means.
For completeness and integrity you would have 3 different definitions of done: for a User Story (a feature), for a Sprint and for a Release. This is also in line with the SCRUM Alliance recommendation.
A User Story Definition of Done
So, let’s pick the User Story DoD, and elaborate more. The User Story DoD’s Continue reading
“The outcome of the execution of E-type software entails a degree of uncertainty, the outcome of execution cannot be absolutely predicted”, or more fully, “Even if the outcome of past execution of an E-type program has previously been admissible, the … Continue reading