Agile Scrum Quotes & Sayings

With agile retrospectives the team drives their own actions! — Ben Linders

Without a good facilitator, a retrospective most likely will be a disaster. — Luis Goncalves

Interestingly, Agile's scrum-team approach has its own way of aggregating some execution risk. For example, in a traditional "single task owner" approach, the risk of execution is not aggregated at all, leaving that task owner to add a lot of task-level buffer to self-insure and deliver on his commitment. In contrast, a 5-person scrum team aggregates the risk that any single individual will make slow progress, as the other four team members can often make up the deficit.

But why aggregate only up to the scrum-team level? Taking a lesson from the insurance industry, the more that risk can be aggregated, the easier it is to manage. Applied to projects, this will nearly always mean that it's better to aggregate risk at the project level. As a result, an Agile project can improve speed by avoiding sprint-level commitments. — Michael Hannan

Summary of Scrum vs Kanban

Similarities:
- Both are Lean and Agile
- Both use pull scheduling
- Both limit WIP
- Both use transperency to drive process improvement
- Both focus on delivering releasable software and often
- Both are based on self-organizing teams
- Both require breaking the work into pieces.
- In both, the release plan is continuously optimized based on empirical data (velocity/lead time) — Henrik Kniberg

The goal of retrospectives is help teams to continuously improve their way of working. — Ben Linders

Most literature on the subject of agile methodology... is written from the viewpoint of software developers and programmers, and tends to place its main emphasis on programming techniques and agile project management - testing is usually only mentioned in the guise of unit testing and its associated tools. ...However, unit tests alone are not sufficient and broader-based testing is critical to the success of agile development processes. — Tilo Linz

Rituals bring people together, allowing them to focus on what is important and to acknowledge significant events or accomplishments. — Luis Goncalves

Agile retrospectives give the power to the team, where it belongs! — Ben Linders

Getting feasible actions out of a retrospective and getting them done helps teams to learn and improve. — Ben Linders

We need to uncover better ways to improve and retrospectives can provide the solution. — Ben Linders

A ScrumMaster who takes teams beyond getting agile practices up and running into their deliberate and joyful pursuit of high performance is an agile coach. — Lyssa Adkins

Before starting a retrospective, you need to think about which exercises would be most suitable. — Ben Linders

Agile Manifesto." It declared the following values: people over processes; products that actually work over documenting what that product is supposed to do; collaborating with customers over negotiating with them; and responding to change over following a plan. Scrum is the framework I built to put those values into practice. There is no methodology. — Jeff Sutherland

To focus on the visible at the expense of the essential is irresponsible. — Bertrand Meyer

The Scrum idea of a separated Scrum Master is good for Scrum, but not appropriate for most projects. Good development requires not just talkers but doers. — Bertrand Meyer