On the 18th of May, 2010, the very new tumbler-glass project by Studio Pragmatists uploaded Tumbler 0.2.1 to Maven. Having recently written about JBehave I found myself really liking the concept of behavior driven development. So I decided to write a similar article about Tumbler. If you want the project code its available in my [...]
I wanted to explore the possibility of using JBehave to formalise scrums definition of done. The idea being to encapsulate a definition of done as a JBehave scenario. So in true scrum style I decided to timebox 4 hours of work dedicated to JBehave. From a scrum point of view BDD can be used to [...]
I have been reading chapter 12 of Succeeding with agile by Mike Cohn. The chapter title is Leading a Self-Organising Team. I have been reading it in the following context: Strive for technical excellence and Improving technical practices is not optional. Why is it that improving technical excellence is sometimes neglected on a project? Why [...]
Probably one of the most common mistakes in Software Development is to allow Estimates to become Commitments. This article looks at story point estimation in scrum, and how velocity is a better tool for monitoring progress through to delivery. If your interested in the arguments that can be presented to the business for velocity metrics over estimation for setting delivery dates, read on.
As you achieve more experience with the scrum process, you come to realise that there is very little if anything you can afford to leave out. If your conducting scrum and considering leaving out a practice, its worth considering what is to be gained and lost. So continuing with the scrum and agile theme this year I plan review some of the scrum practices highlighting the benefits and some of the errors that are made. The first of these focuses on the Sprint Review and within that in particular the Software Demo.