Velocity is killing agility is the observation discussed by Jim Highsmith in this blog post. He explains that this metric is increasingly used for the wrong reasons: measuring productivity and focusing on volume delivery instead than on quality. He concludes saying that the importance given to velocity should be balanced with other metrics like feature value, feature delivery cycle time or quality.
The Scrum Expectation Line is defined by Zsolt Fabók as the line that follows the expectations of the Product Owner during each sprint. In this blog post, he discusses the difference between the team capacity to deliver and what the Product Owner wants in each Sprint and explains how his team deals with it.
Is the transition to Agile more difficult for late adopters? In this blog post that provides feedback about his attendance to the Conference on Lean Enterprise Software and Systems, Alan Shalloway explains that those taking on Agile are of a different mindset than those who made it initially successful. He also discusses Scrum-of-Scrums and preventing a “cargo cult” attitude towards agile practice.
Agile estimating and planning in a Scrum software development project will not prevent your boss from asking: “Will you make the date?” This video explains how to use Scrum and the “Cone of Uncertainty” to provide an answer like: “60% probability.”
This short video looks at some of the roles played in an Agile Team with a particular focus on Project Manager and Iteration Manager.
This article describes a Lean and Scalable Requirements Information Model that extends the basic team‐based agile requirements practices to the needs of the largest, lean‐thinking software enterprise. While fully scalable to all levels of the project, program and portfolio levels, the foundation of the model is a quintessentially lean and agile subset in support of the agile project teams that write and test all the code.
Upfront Modeling is fine, documents describing the intended architecture are fine, and so forth. But the architecture, and our learning about it, can improve. Speculative software architecture should be made concrete and not of concrete.
Scrum Expert Copyright © 2009-2026 Martinig & Associates