Quotes on Scrum and Agile Project Management
I am frequently amused when the same people who believe that it is not possible to get the requirements for a product correct up front, and therefore want to use Scrum for development, will in the next breath explain how they aren’t quite ready to start using Scrum because they haven’t worked out all of the details of their Scrum approach! This type of thinking is poorly aligned with fundamental Scrum principles.
In his book “Specification by Example – How successful teams deliver the right software”, Gojko Adzic had some interesting quotes about building the right product.
In his book “Succeeding with Agile”, Mike Cohn present nine questions that you should ask for a current or proposed team. Questions should be asked iteratively… until you answer “yes” to each.
Implementing Agile and Scrum in software development organization means a big change. In her book “The Great ScrumMaster“, the Agile coach Zuzana Šochová recommends an eight steps journey for a successful transformation to the Scrum approach.
One of the key element of Agile Software Development approaches like Scrum is to emphasize delivering quickly business value over having a long-term rigid plan. In his book “Project Myopia”, Allan Kelly discusses the issue of identifying and delivering value.
We all know that there are three roles in Scrum teams : product owner, scrum master, and the development team. Modern software development can sometimes require a high level of specializations that could be beyond the capabilities of the Scrum team members.
Velocity is one a key metrics used by Scrum teams to measure the rate at which an Agile team delivers value to the customer. In his book “Escape Velocity – Better Metrics for Agile Teams”, Doc Norton explains why velocity is not the ideal metric for Scrum teams.
Scrum Expert Copyright © 2009-2026 Martinig & Associates