Skip to main content

The second impediment, or why should you care about engineering practices?

Sometimes I think, Switzerland is land of product owners. Thanks to our strong economy, there is much more development to do than have capacity for. So we off-shore and near-shore quite a bit. And technical topics seem to produce a yawn among managers and product owners. "Not really my problem," they seem to be saying. I'd like you to challenge that assumption!

I don't often change the main messages of my Scrum courses. For years, I have been talking about "Inspect and Adapt", "Multitasking is Evil" and "Spillover is Evil." Recently I have added a new message:

Bugs are Evil.

Why this change? While researching for my Scrum Gathering Workshop on Code Dojo's, I found a paper by Alistair Cockburn from XP Sardinia. He wrote, In 1000 hours (i.e. in one month), a team can write 50'000 lines of code. And they will send 3'500 bugs to quality assurance.

Doing the math based on industry standard assumptions, I found that that team will create 12'000 hours of effort for themselves, quality assurance, operations, and customer support. 1 year of waste produced for no good reason!

Is this really true? Well, at my last Scrum Master course, I met someone whose teams spend roughly 2/3rds of their time fixing bugs, much of them in emergency mode. Technical debt is a real danger! Imagine if you were paying 2/3rd of your income to pay the rent and plug holes in the ceiling of your apartment! That product is on the verge of bankruptcy!

Technical topics often generate a yawn among product owners and managers. But it's your money and your team's capacity which is being wasted!

So I'd like to encourage you to pay attention to engineering practices. Bugs are evil! Remember that and make sure everyone in your organization knows it too. As a leader, you are best positioned to ask the question, how can have fewer bugs?"

P.S. This is the topic for Monday's Scrum Breakfast Club, "Why should you care about engineering practices?" Check out the event, and come to my Manager and Product Owner friendly introduction to Pair Programming and Test Driven Development.

Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…