Blogs on Scrum and Agile Project Management
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.
In this blog post, Mike Treadway explains the technique of using story points for story estimation during agile planning sessions.
In his blog post “New to agile? Remember how to say ‘No’”, Bob Hartmann reminds us that the “no” word should be used much more often at every level of the organization where agile is being embraced.
In this blog post, Lisa Crispin describes how a team at Energized Work put in practice the Agile principle of collaboration.
In the episode 170 of the Software Engineering Radio, Bas Vodde explains how to apply agile principles to large and distributed development organizations. Bas shares his experiences on working in, consulting and coaching companies to adopt Scrum for large scale software development.
Scrum Expert Copyright © 2009-2024 Martinig & Associates