Should We Change Scrum?

TL; DR: Can We Or Should We Change Scrum?

Can we or should we change Scrum, or is it a sacrilege to tweak the ‘immutable’ framework to accommodate our teams’ and organizations’ needs?

Not so fast; don’t just dismiss augmenting Scrum as leaving the path, contributing to the numerous Scrumbut mutations, giving Scrum a bad name. However, in our rapidly evolving business landscape, sticking rigidly to traditional Scrum by the book could be a straightjacket stifling innovation, user focus, and adaptability.

From ensuring cultural compatibility to facing technical debt challenges and emerging technologies, discover ten compelling reasons why augmenting Scrum isn’t just okay—it’s necessary for modern teams.

Read on to discover when and how to adapt Scrum responsibly without diluting its essence.

Should We Change Scrum? Age-of-Product.com
Continue reading Should We Change Scrum?

Lost in Communication and Collaboration — Scrum Anti-Patterns Taxonomy (2)

TL; DR: Lost in Communication and Collaboration

Lost in Communication and Collaboration addresses two categories from the Scrum anti-patterns taxonomy that are closely aligned: ineffective collaboration at the stakeholder level, often resulting in an unsuited reporting system based on misaligned metrics.

Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the organization’s long-term sustainability.

This is the second of three articles analyzing the 183 anti-patterns from the upcoming Scrum Anti-Patterns Guide book. The third article will address failures and breakdowns in planning, process, collaboration, and alignment within the Scrum framework.

Lost in Communication and Collaboration — Scrum Anti-Patterns Taxonomy (2) — Age-of-Product.com
Continue reading Lost in Communication and Collaboration — Scrum Anti-Patterns Taxonomy (2)

Wild West to the Agile Manifesto — Jim Highsmith at the 52. Hands-on Agile Meetup

TL; DR: Hands-on Agile #52: Jim Highsmith & the Agile Manifesto

On August 17, 2023, we had the opportunity to interview Jim Highsmith about his path to agile product development: From Wild West to the co-authoring the Agile Manifesto.

Wild West to the Agile Manifesto — Jim Highsmith at the 52. Hands-on Agile — Age-of-Product.com

📺 Watch the video now: Jim Highsmith & the Agile Manifesto — Hands-on Agile 52.

Continue reading Wild West to the Agile Manifesto — Jim Highsmith at the 52. Hands-on Agile Meetup

Resistance to Agile Transformations: Reasons and How To Overcome Them

TL; DR: Resistance to Agile Transformations

Stakeholders often revert to resistance to agile transformations due to fears about job security, perceived loss of control, comfort with established practices, and misconceptions about Agile.

However, we can help: Agile practitioners can ease the change process by employing techniques such as empathetic listening, co-creating the change process, introducing incremental changes, offering targeted education, and showcasing internal success stories. Addressing resistance with understanding and respect is pivotal to a successful agile transformation.

Resistance to Agile Transformations: Reasons and How To Overcome Them — Age-of-Product.com
Continue reading Resistance to Agile Transformations: Reasons and How To Overcome Them

SAFe® — Despised, Yet Successful?

TL; DR: SAFe® — Despised, Yet Successful?

Many in the Agile community consider the Scaled Agile Framework designed by Dean Leffingwell and Drew Jemilo as unagile, violating the Agile Manifesto and the Scrum Guide. “True agilists” would never employ SAFe® to help transition corporations to agility. SAFe® is an abomination of all essential principles of “agility.” They despise it.

Nevertheless, SAFe® has proven not only to be resilient but thriving. SAFe® has a growing market share in the corporate world and is now the agile framework of choice for many large organizations.

How come? Learn more about nine reasons for this development.

PS: I have no affiliation with SAFe® whatsoever and consider it harmful. Yet there are lessons to learn.

SAFe® — Despised, Yet Successful? — Age-of-Product.com
Continue reading SAFe® — Despised, Yet Successful?

The Peril of Adhering to Legacy Systems, Processes, and Practices — Scrum Anti-Patterns Taxonomy (1)

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. The excessive control by stakeholders and the management level stifles creativity and adaptability, disrupting planning and hindering a Scrum team’s growth. Moreover, these categories from the Scrum anti-patterns taxonomy often emphasize an unbalanced focus on short-term gains, neglecting long-term strategy, value creation, and the essential alignment among all stakeholders to succeed in uncertainty.

Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the long-term sustainability of the organization.

This is the first of three articles analyzing the 183 anti-patterns from the upcoming Scrum Anti-Patterns Guide book. The following article will address communication and collaboration issues at the team and organizational levels.

Adherence to Legacy Systems, Processes, and Practices — Scrum Anti-Patterns Taxonomy (1) — Age-of-Product.com
Continue reading The Peril of Adhering to Legacy Systems, Processes, and Practices — Scrum Anti-Patterns Taxonomy (1)