Doc Norton
Doc is a software delivery professional working to make the world of software development a better place. His experience covers a wide range of development topics. Doc declares expertise in no single language or methodology and is immediately suspicious of anyone who declares such expertise.
A frequent and well-rated international speaker, Doc is passionate about helping others become better developers, working with teams to improve delivery, and building great organizations. In his role at OnBelay, Doc is provided opportunities to realize his passion every day.
You can learn more about Doc's presentations or feel free to peruse around and read his latest articles on agile, leadership, and culture.
If you want Doc to come speak at your event, let him know.
Featured Articles
Simple Things
When I say simple, I don’t necessarily mean easy. And I certainly do not mean crude in form or incomplete. Simple indicates something that does not have superfluous parts or multiple responsibilities, is easy to understand, is as independent from the rest of the solution as possible, and meets a need as is.
Simple may not address all use cases, but it does address some use cases.
Over the past several years, as I’ve been helping teams and organizations improve their ability to deliver software products that are desirable, viable, and feasible, I have been experimenting with a Behavior Framework that has proven to be rather effective. And I’d like to share it with you in hopes that you find it useful and that you provide me feedback on your experiences with it.
My plan is to write a series of blog posts all related to the behaviors framework. Some of them will be about a specific behavior. Some of them will be about tools or techniques that help teams express one or more of the behaviors. Some of them will be my own experiences. And some will be damn near complete fiction.
In this excerpt from Escape Velocity, we take a more in-depth look at Velocity and try to answer (at least in part) the question, “What Is Velocity”?
This article focuses on using Chain of Command as a means of reducing cyclomatic complexity in our code. Along the way, we also create better adherence to SRP.
The Experiment Canvas is a simple means of planning, tracking, and responding to your experiments.
The seventh behavior, “Release ridiculously often,” is usually met with nods from half of the crowd and raised eyebrows from the other half. The nodders want to know why it isn’t higher on the list and the eyebrow-raisers want to know the definition of “ridiculously often”.
Composition refers to the way in which something is put together. Composition is a key element in many of the things humans create. Whether it be a musical piece, a painting, a garden, or a building, the way we assemble the core components — the composition of them — has a significant impact on the overall experience.
If you are not familiar with Liberating Structures, I suggest you take a look at them. I use a few of them now and then as circumstances warrant. In future articles, I will discuss some of the others, but today’s installation is dedicated to the Liberating Structure I most often use — 1–2–4-All.
The Experiment Canvas is a simple means of planning, tracking, and responding to your experiments.