Most of the Scrum teams use a task board to visualize their activity and progress with task cards. In these two blog posts, Keith Clinton, the author of Agile Game Development with Scrum, discusses the concept of feature boards and feature cards.
The Cumulative Flow Diagram (CFD) provides typical information about status of your Scrum project: how much work is done, ongoing and in backlog, what is the pace of progress, etc. In this blog post, Pawel Brodzinski explains that you can also use the Cumulative Flow Diagram to detect the issues that a Scrum team might face.
How can you share information about a Scrum project between the team members or assess its status? This article by Kulawat Wongsaroj proposes eight visualizations techniques to share information on a Scrum project. All these techniques try to summarize the large and complex set of data of a Agile project in different dimensions. They exist to help the ScrumMaster, the other team members and the other various stakeholders like managers to get a better understanding of the project.
Matthew Evans shares with us an Excel spreadsheet that allows to record and visualize informations about your Scrum sprint. One sheet allows to manage the sprint data with the estimated and actual work for each story. A project page consolidate the sprints data at a project level. Visit the “Agile scrum project management spreadsheet” page to get the spreadsheet.
This article explains that it is important to end doomed projects before they become “too big to fail”. This article isn’t about the personal benefits of failure, but is rather about Agile software development. It’s about how failure, recognizing it and doing something about it, is a critical element of any Agile initiative.
In this blog post, Ken Pugh compares the usage of Kanban board and Scrum tracking boards to track progress of agile projects. He concludes that Scrum-style boards and Kanban-style boards can provide the same information, but in different ways.
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.