The One Thing Non-Engineers Should Do to Manage Engineers' Work Quality

This article was automatically translated from Japanese by AI. Read the original Japanese version →

Table of Contents

Here is what non-engineers should do to manage the quality of engineers' work.

Preface

Unusually for this blog, this post is aimed at non-engineers. For example, I'm thinking of planners or managers who assign or outsource work to engineers.
That said, I think engineers should know this too, because demonstrating work quality to the requester is essential for both sides to move development forward with peace of mind.
In the rest of this post, I'll refer to the non-engineer side as the requester—assuming someone who basically cannot read code at all.

Break Work Down from the Requester's Perspective

Anyone can break work down into smaller pieces. However, there is one critical rule to follow here: break it down into units whose completion the requester can actually verify. For example, "setting up the database" is not a valid unit of work, because a non-engineer requester cannot verify the result. Even if it's bare-bones, make building an input form and displaying the submitted result a single combined unit. Always plan task breakdowns together with how the requester will verify them.

Pros

Breaking down work this way has several benefits.
First, progress becomes visible to the requester's own eyes. Never take an engineer's self-reported progress at face value.
Second, the requester can check quality early on. If you have something runnable ready early, even the requester can catch bugs. Testing often gets batched toward the end of development, but ask them to keep the product bug-free even mid-way through. That also lets you take action early if a particular developer keeps introducing lots of bugs. Being able to make that call sooner rather than later is a huge advantage.

Cons

Of course, there is a downside: a unit whose completion the requester can verify doesn't align with the unit in which an engineer can work most efficiently.
However, that is a necessary cost when working with engineers you haven't built a relationship of trust with yet. Accept it.
It also takes effort on the requester's part to review things, but that's work you ought to be doing anyway. Anyone who could have checked the intermediate progress and neglected to do so has no right to complain about the final result.

Summary

The breakdown technique described above pulls out just one piece of what's known as story points, an approach more commonly used in Agile development.
You might also feel that if there's mutual trust between the engineer and the requester, you wouldn't need techniques like this. Well, I don't work in an environment where I can afford that luxury, so techniques like this are necessary. ¯\_(ツ)_/¯