Remove Process Remove SCRUM Remove Sustainability Remove Technical Review
article thumbnail

Definition of Done: Business Agility Abhors Technical Shoddiness

Scrum.org

TL; DR: The Definition of Done: Business Agility & Technical Excellence Most of the time, stakeholders are not interested in how we solve their problems as long as we ethically play by the rules. Learn more about twelve success principles of employing such a Definition of Done as a Scrum team to help your organization become agile. ??

article thumbnail

Scrum Team Failure — Scrum Anti-Patterns Taxonomy (3)

Scrum.org

TL; DR: Scrum Team Failure This post on Scrum team failure addresses three categories from the Scrum anti-patterns taxonomy that are closely aligned: Planning and process breakdown, conflict avoidance and miscommunication, and inattention to quality and commitment, often resulting in a Scrum team performing significantly below its potential.

SCRUM 190
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

New Features vs. Technical Debt: A Product Owner's Dilemma

Scrum.org

The Product Owner is the bridge between corporate strategy and the Scrum Team. The Product Owner must balance the demands of users against the need to ensure that the product remains up to date from a technical perspective. What is technical debt? Evaluate user requests and technical debt against this strategy.

article thumbnail

The Peril of Adhering to Legacy Systems, Processes, and Practices

Scrum.org

TL; DR: Adherence to Legacy Systems, Processes, and Practices Administrative overreach and micromanagement in Scrum mainly arise from clinging to legacy systems and traditional (management) practices, leading to rigidity and misapplication of Agile principles. Get notified when the Scrum Anti-Patterns Guide book is available !

Process 149
article thumbnail

The Scrum Trap: How Unfit Practices Will Harm Return on Investment

Scrum.org

TL, DR: The Scrum Trap Scrum is a purposefully incomplete framework. And then there are others — the Scrum trap. Let’s look at what practices and tools for collaboration and team building are not helpful when used with Scrum. ? Preorder the Scrum Anti-Patterns Guide book now for delivery in January 2024! ?️

SCRUM 150
article thumbnail

Escaping the Feature Factory

Scrum.org

In many large organizations, Scrum teams fall into the ‘feature factory’ trap, focusing more on churning out features than creating real value. Preorder the Scrum Anti-Patterns Guide book now for delivery in January 2024! It’s too bad that this shift undermines Agile principles and hampers long-term success and innovation.

article thumbnail

Top 10 Project Management Methodologies – An Overview

ProjectManager.com

The name is apt, as the waterfall methodology is a process in which the phases of the project flow downward. When implementing the agile methodology , project planning and work management are adaptive, evolutionary in development, seeking early delivery and are always open to change if that leads to process improvement.