Scrum The Art Of Doing Twice The Work In Half The Timeepub 🎁 Validated

In "Scrum: The Art of Doing Twice the Work in Half the Time," Jeff Sutherland introduces the Scrum framework as a high-productivity alternative to traditional, rigid project management, emphasizing iterative cycles and self-organizing teams. Key principles include using "sprints" to deliver work, embracing empiricism through inspection and adaptation, and eliminating waste to improve team efficiency. Read a detailed summary of these concepts at Readingraphics

Scaling Scrum

  • Frameworks: Nexus, LeSS (Large-Scale Scrum), and Scrum@Scale offer patterns for coordinating multiple Scrum teams.
  • Key Considerations: Maintain empiricism at scale, preserve team autonomy, ensure integrated backlog and shared Definition of Done, and invest in cross-team communication and architecture alignment.

Scrum: Art of Doing Twice the Work | PDF | Publishing - Scribd scrum the art of doing twice the work in half the timeepub

A significant portion of the book focuses on human behavior. Sutherland highlights the "multitasking myth," explaining that context switching can cost up to 40% of a person’s productive time. Scrum encourages "flow" by focusing on one task at a time. Furthermore, Sutherland emphasizes that "the team is the unit of delivery." He argues that small, autonomous teams outproduce large, hierarchical departments because they communicate faster and feel a greater sense of collective ownership. Delivering Value In "Scrum: The Art of Doing Twice the

Sprint Retrospective (45 minutes): The secret sauce. The team asks: What went well? What went wrong? What will we change? Sutherland argues that teams that skip the retrospective plateau; teams that do it improve 10% every Sprint. Scrum: Art of Doing Twice the Work |

  1. Sprint Planning: the team sets goals and selects tasks to complete during the upcoming Sprint.
  2. Daily Scrum: a brief meeting where team members share their progress, plans, and any obstacles.
  3. Sprint Review: the team demonstrates the work completed during the Sprint and receives feedback from stakeholders.
  4. Sprint Retrospective: the team reflects on their process and identifies opportunities for improvement.

Sutherland presents Scrum not just as a process, but as a philosophy for maximizing "flow" and eliminating waste. Readingraphics

Detailed long-term plans (Waterfall) fail because they can't adapt to change. 2 The Origins of Scrum

Part 4: Key Principles for "Half the Time"

To achieve the productivity gains promised in the title, you must adhere to these specific philosophies: