Received business wisdom holds that clear lines of responsibility, and single points of accountability, are crucial to give Scrum team members clarity over their expectations; but doesn’t that sound a little too close to a mechanism for blaming people?
The goal of the book “Lean-Agile Software Development – Achieving Enterprise Agility” by Alan Shalloway, Guy Beaver and James R. Trott, is to propose a vision of Agile software development that goes behind the current practices, more specifically Scrum, to integrate the principles of Lean development.
Product metrics and key performance indicator(KPIs) have been getting increasingly more important and useful for Agile organizations that develop digital products. When done right, they can become an engine for product growth and inform great strategic and tactical decisions. When done wrong, they can lead to a huge amount of sunk resources and wasted time.
This article discusses the clarity of requirements for Agile software development and explains how you can use a four-step process for gathering them with the four levels of agile requirements.
Most teams I work with have three distinct roles; BA, Developer, and QA. Most teams I work with have three distinct phases of their work; gather requirements, build, verify. Even on agile teams, these separations exist.
Scrum offers minimal guidelines for Agile project management. In his book “The Scrum Field Guide”, Mitch Lacey provides Scrum practitioners with material that should help them improve their Scrum practices.
Are you ready to elevate your Scrum team’s retrospective game? Running retrospectives can be a breeze with the right tools and a solid framework in place. Enter EasyRetro – the platform that streamlines your retrospective process and turns it into a fun and productive Agile team activity.
Scrum Expert Copyright © 2009-2025 Martinig & Associates