Seven common Sprint Burndown graph signatures
This first appeared on the ScrumAlliance.org website on October 30th. It is presented here in its original unedited form. Burndown graphs are commonly used in Scrum projects to give the team an understanding of the amount of work remaining for the Sprint (or iteration). In Ken’s own words: “As a team works together, it develop … Read more
Performing odd jobs with Selenium helper pages
Selenium [1] is a nice tool for testing browser based user interfaces. It’s simple to install and with the firefox IDE plugin, it’s even easier to use. But there are some tests that are just not accessible through a UI. Should you even test functionality that’s not immediately expressed, and if so how?
Technical debt, and the Death of Design: Part 2
This is the second article that I wrote for the Scrum Alliance [3]. It was orginally published on July 24 and can be found here. The article presented below is the original unedited version with all my grammar and spelling mistakes!
The Thai Restaurant Model (and its applicability to Software Development)
Personal note: I started this article about 9 months ago. Although it’s quite a fun article, I have become increasingly critical of the use of analogies to describe software development. My feeling is that analogies lead to assumption that may, or may not, be valid. So, rather than talk about building a bridge, a house … Read more
Controling the flow of daily meetings with a team mascot
When introducing Agile/Scrum practices to a new team it’s common for the team to have very chaotic or drawn out meetings. Often the daily scrum will degenerate into a long conversation over topics that are of little interest to the team. Long daily meetings are insidious for Agile teams. If the the team spends more … Read more
