Articles on Scrum and Agile Project Management
This article aims to bring to the table a consolidated Scrum Project Dashboard layout that could be easily maintained and updated by the Product Owner with day-to-day and well-known information provided by the team. He will be able to get stakeholder and management attention and support while providing an updated clear picture on the Project’s status.
This is an article about opposition to Scrum. Most of the challenges in Scrum adoption aren’t technical, but social. Because Scrum makes ineffectiveness obvious and control organic, some people will fight tooth and nail to stop the effort.
This article documents a team’s move to Agile using Team Foundation Server 2010, starting out with the Microsoft Solutions Framework Agile v5.0 process template and eventually switching to the Microsoft Visual Studio Scrum 1.0 template.
Scrum teams often use user stories for backlog items. Unfortunately, one of the most important aspects of a story – its extremely short length – has been subtly transformed over time and user stories have lost their original essence and potency.
In this article, Bachan Anand explains that beyond the mechanics, the daily Scrum stand-up meeting checks how is the team progressing toward fulfillment of the sprint commitment, identifies concerns immediately and provides an opportunity to discuss corrective action.
Martín Alaimo proposes to measure Scrum sprint progress with a continually updated ETC (estimate-to-complete) for each user story.
Thinking about Lean as a combination of science, management and learning provides Scrum practitioners to start with including Lean and Kanban practices into their Scrum practices. Explicit policies, managing work-in-progress, and creating visibility have a direct, measurable impact on a team’s velocity.
Copyright © 2009-2022 Martinig & Associates