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.
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.
This book is a little bit different in the project management category. Its goal is to present an open framework and not a prescriptive model. Many project managers prefer to apply existing recipes for their project, but if you are ready to step out of your comfort zone, you will find in this books many ingredients to create your own recipe to manage software development projects.
In this blog post, Mike Treadway explains the technique of using story points for story estimation during agile planning sessions.
Scrum Expert Copyright © 2009-2026 Martinig & Associates