Summary

The text compares the process of writing to the empirical process of software development in Scrum, emphasizing the importance of transparency, inspection, and adaptation.

Abstract

The article draws parallels between writing and the empirical process of Scrum, highlighting the need for transparency in sharing ideas, the courage required for inspection through feedback, and the adaptive approach to refining one's work. It suggests that writing, like Scrum, is an iterative process that involves putting forth ideas, making them visible for scrutiny, and using feedback to improve. The author encourages writers to embrace empiricism by being open to feedback, continuously improving their work, and taking pride in their craft, akin to the principles of Scrum. The process is described as a creative and intellectual journey that requires transparency, the willingness to listen and adapt, and the ability to find joy in the act of writing and learning.

Opinions

The author believes that writing and software development are similar in their empirical nature, both requiring transparency, inspection, and adaptation.
Empiricism is seen as the core of Scrum, necessitating that teams and organizations evolve and improve their understanding to navigate complex problems.
Feedback is considered crucial for understanding one's position and deciding on necessary changes, whether in writing or software development.
The author suggests that sharing a common language and definition of 'Done' is essential for clarity and progress in collaborative writing endeavors.
Inspection is valued, but it should not disrupt the workflow or become overly burdensome.
Adaptation involves evaluating feedback positively, even when it seems negative, and making timely adjustments to one's work.
The author emphasizes the importance of personal satisfaction with one's work, as it influences the willingness to publish and share ideas with others.
Writers are encouraged to experiment and publish frequently, using feedback as a tool for growth and improvement within the empirical framework of Scrum.
The author invites readers to engage with the Serious Scrum community on Slack for collaboration and to share their thoughts on the subject.

Writing involves Transparency, Inspection and Adaptation

Write, share, listen for feedback, then do it again

The process of building software is a creative pursuit, just like writing. You have to put ideas together, and then make them transparent for others to inspect. Feedback on your work can be brutal. You may need to rethink your ideas, or even start again from scratch. How you choose to react to that feedback is really up to you, but what we’re talking about in both cases is an empirical process.

Empiricism is the beating heart of Scrum. Teams and organisations are complex and adaptive, just like the problems with which they must grapple.

As Scrum Teams, we need to continually evolve and improve our situational awareness, so that we can accurately understand how we’re doing, and decide whether or not we need to change course.

In other words, we need transparency, inspection and adaptation.

Writing as an Empirical Process.

Imagine a situation where you’re considering writing an article for Serious Scrum. Let’s see whether it makes sense to think of that as an empirical process.

‘Empiricism asserts that knowledge comes from experience and making decisions based on what is known.’

We can only write what we know. We might have a burning idea to shatter a myth, or expose a fallacy. It’s just something that has to be said…

After we share a draft, we may get reactions, or we may hear tumbleweeds in response. People may make connections with our writing and prompt us to read something related, or we may get no reaction at all...

However, at the time we start to write, we can only move forward with what we know in that moment. The thing we write or prepare is nothing more than a snapshot of our knowledge at that moment. Feedback helps us to understand where we are, either with our writing skill or our understanding of the topic… So far, this seems to fit.

(N.B. All quotes below are from the Scrum Guide)

Transparency

‘A common language’

Imagine we are thinking about medium posts on the topic of Scrum or related Agile approaches. We’ve all read those, right? We have an idea of what one of those could look like.

As readers of these posts, and as professional practitioners in that area, we share a lot of language in common.

‘share a common definition of Done’

Done in this case means that we’ll have an article on a topic, that helps build understanding of a particular subject. Hey, you know what? Serious Scrum writers have a Definition of Done. That’s kind of helpful actually :)

Inspection

‘detect undesirable variances’

Sharing drafts allows others to inspect what we’ve written. It can take courage to share our work, and it can take courage and openness to give honest feedback on the quality or content of a draft. Hey, these are scrum values!

The same applies to sharing published posts. It can be scary! But guess what, there is a community out there ready and willing to give that feedback. Are you ready to hear it?

‘inspection should not be so frequent that inspection gets in the way of the work’

Asking for people to review articles and drafts can get in the way of their work. Reviewing and commenting should be a collaborative exercise, and should not be demanded or expected.

Adaptation

‘If an inspector determines that one or more aspects of a process deviate outside acceptable limits’

Here’s the thing: if someone gives you feedback on something you’ve written, you have final edit, so you can choose to include it or ignore it. You might find though that if you ignore feedback, it will be slower to arrive the next time.

Best to evaluate all feedback as positive, even when the source appears suspiciously troll-ish :)

‘An adjustment must be made as soon as possible to minimize further deviation.’

Watch out for mistakes. Try to correct them. I’m always trying to be less verbose.

Writers have an intimate knowledge of the process of empiricism. Anyone creative who has ever put their work out there for others to inspect will recognise the feelings and emotions to accompany that activity. It takes courage and openness.

However, as a writer, the ability to inspect your own gut reaction to the thing you are publishing is critical. Are you happy with it? In the end, this is what matters. Feedback will inform your reaction, and it might inform your next steps, but being happy with what you write will always temper the anxiety to publish in the first place. Getting there is the battle really!

Also, the ability to use and incorporate feedback as a writer is really important. Writers are in a privileged position to experiment quickly if they wish, and publishing has never been easier.

I encourage you to give it a try. Writing is an intimate way to understand empiricism, which is the beating heart of Scrum, and a great way to situate your learning, and identify areas for personal improvement.

What’s not to like?

Hope you enjoyed this post. Please do clap, comment, follow, share or respond! You can also find me on Twitter here.

Do you want to publish in Serious Scrum? Connect with us on Slack to make it happen!

We run a Serious Scrum channel on Slack. You’re all invited. Feel free to reach out and connect with us on Slack to share your thoughts.