Three Common Developer Blunders in 5:05 Minutes—Making Your Scrum Work #14

TL; DR: Common Developer Blunders — When Your Scrum Team Lacks Alignment

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. While it is common to first look outside our team for impediments, such as dysfunctional processes or other systemic issues, I would advise starting with the Scrum team’s way of collaboration: Are we aligned on the why, what, and how? Otherwise, the three following Developer blunders may diminish the team effectiveness.

📺 Join me and explore the consequences of these Scrum Developer blunders and what you can do about them in a little more than five minutes.

Three Common Developer Blunders in 5:05 Minutes—Making Your Scrum Work #14 — Age-of-Product.com

Update: I am running a poll on LinkedIn—join the voting: “What common ways have you observed how Developers diminish the value creation of their own work?”

Continue reading Three Common Developer Blunders in 5:05 Minutes—Making Your Scrum Work #14

The Developers Code Fallacy — Making Your Scrum Work #9

TL; DR: The Developers Code Fallacy — They Should Talk to Customers, Too, Though

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. The Developers Code Fallacy starts with the idea that Developers are rare and expensive and should focus on creating code. Business analysts or customer care agents can talk to customers instead. However, in practice, it has a diminishing effect on a Scrum team’s productivity and creativity. It is a sign for an organization still profoundly stuck in industrial paradigm thinking.

Join me and explore the reasons and the consequences of this Scrum anti-pattern in 110 seconds.

The Developers Code Fallacy — Making Your Scrum Work #9 — Age-of-Product.com
Continue reading The Developers Code Fallacy — Making Your Scrum Work #9

20 Questions from New Scrum Master to the Developers

TL; DR: 20 Questions from New Scrum Master to the Development Team

From Scrum Master to Development Team members, this set of questions addresses the foundations of a Scrum Team capability to build valuable products: technical excellence and what it takes to achieve this proficiency level. The questions have been modeled after some basic principles that high performing teams have in common—from keeping technical debt at bay to collaboratively creating a Product Backlog.

Download a printable template for your convenience.

20 Questions from New Scrum Master to the Development Team — Age-of-Product.com
Continue reading 20 Questions from New Scrum Master to the Developers

Download the 20 Questions from New Scrum Master to the Development Team Questionnaire

Welcome to the 20 Questions from Scrum Master to the Development Team Download Page

From Scrum Master to Development Team members, this set of questions addresses the foundations of a Scrum Team capability to build valuable products: technical excellence and what it takes to achieve this proficiency level. The questions have been modeled after some basic principles that high performing teams have in common. Download a printable template for your convenience.

20 Questions from New Scrum Master to the Development Team — Age-of-Product.com
Continue reading Download the 20 Questions from New Scrum Master to the Development Team Questionnaire

Scrum’s Nature: It Is a Tool; It Is Not About Love or Hate

TL; DR: Scrum’s Nature: It Is a Tool; It Is Not About Love or Hate

Regularly, we find articles from developers detailing why ‘Agile’ in general and Scrum’s nature, in particular, deserve our collective disdain.

What has always struck me in this discussion is its emotionality. Scrum is a tool, useful to accomplish one primary task: delivering value to customers of emergent products in complex environments while mitigating an organization’s exposure to risk at the same time. So, if Scrum is not working in an organization, maybe it is because Scrum is applied to the wrong cause in the first place. Or, that its application has been mechanical, driven by folks who don’t know what they are doing. (Seriously, how hard can Scrum be if the manual comprises of 18 pages, right?)

The question then is: Why would I “hate” a tool unsuited for the intended purpose or applied incompetently? Would I hate a hammer for not being capable of accurately driving a screw into a wooden beam? Probably not, as the hammer wasn’t designed for that purpose, and neither sheer will-power nor stamping with your feet will change the fact.

Scrum’s Nature: It Is a Tool; It Is Not About Love or Hate — Age-of-Product.com
Continue reading Scrum’s Nature: It Is a Tool; It Is Not About Love or Hate

Development Team Anti-Patterns

TL; DR: Development Team Anti-Patterns

After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. Learn more about what to look out for if you want to support your fellow teammates.

Development Team Anti-Patterns — Age-of-Product.com
Continue reading Development Team Anti-Patterns