In this blog post, George Dinwiddie explains how to use the first iteration in a Scrum project to deliver some working software and not just building a backlog and setting up infrastructure for the next iterations that will deliver increments of functionality.
Martín Alaimo proposes to measure Scrum sprint progress with a continually updated ETC (estimate-to-complete) for each user story.
This is a funny but realistic time-lapse video of a scrumboard and burndown chart taken during a 9 day sprint.
This video shows a discussion on how agile techniques rebuild trust between IT and business at the 10 Years of the Agile Manifesto conference.
Each Scrum Sprint should produce two results: 1) A product or service which is an increment of functionality closer to delivery and 2) a better, happier, more productive team. Peter Stevens explains that the retrospective is the primary opportunity for achieving the second result.
This post presents a structured and hierarchical product backlog board that considers non-functional requirements and display high priority items that are ready to code.
A simple tutorial on how to create a Scrum Burndown Chart with Google Docs for free.