This article provides an overview on the derivation and application of user stories, which are the primary concept that represent the user requirements in agile software development approaches like Scrum. Its goal is to describe the user story in detail, because it contains the key agile practices that help align solutions directly to the user’s specific needs, assuring quality at the same time.
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 video discusses of Big Visible Charts (also named BVCs or Information Radiators) as a practice to improve the status visibility of agile projects.
A team of volunteers put together this video to highlight the less desirable behaviors that can sometimes make their way into a daily Scrum Stand-up meeting.
This article suggests that it would be wise to think, very candidly, whether Agile is really something that your company can achieve. The less transparency is tolerated in a company, the less traction Agile will get. Another key prerequisite for being Agile is having the ability to have adult conversations.
In this blog post, Kristen Bornemann shares her thought about getting quick results from iteration in the context of the independent game developers. There is a fine line between making quick iteration a focus and getting bogged down in process.
Roy Osherove shares in this video how you can you manage a person who is always late to a stand-up meeting.
Scrum Expert Copyright © 2009-2024 Martinig & Associates