
The People's Scrum: Agile Ideas for Revolutionary Transformation

change. Often organizations treat a Transformation (with a capital T) as a project with a start date and an end date, applying an old way of thinking to new ways of working. Imposing Agile is not agile, nor is treating it as a deterministic project. In addition, humans have an evolutionary bias to be averse to loss. Collectively, all of this can ge
... See moreJonathan Smart • Sooner Safer Happier: Antipatterns and Patterns for Business Agility
Autonomous teams should work toward assigned customer value outcomes, rather than being assigned tasks. What to work on is, generally, given to the team through the prioritization of initiatives in the LVT and the backlog. The team, which should include a product person, collaboratively prioritizes what it will work on during the next iteration to
... See moreDavid Robinson • EDGE: Value-Driven Digital Transformation
This agile value also seeks to abolish the spectre of up-front planning, but with a special emphasis on keeping the dialogue between the development team and the customer as open and fluid as possible.
Chris Sims • The Elements of Scrum
Implementing Scrum is revolutionary because the implementation of Scrum requires the creation of new roles (such as Product Owner and Scrum Master), new team structures, new artifacts, new events, and new behaviors. It is unadaptable. The official Scrum Guide states: “Scrum’s roles, events, artifacts, and rules are immutable and although implementi
... See more