Habit: Naming as a Process

A Habit in these Change Series:
Fundamentals Workshop, Validated Software Mender I (VSM-I)

Our promise once you successfully implement Naming as a Process:

  • you will be able to trust the names in your team’s code
  • you will spend less time coming up with names
  • you will waste less time hunting for experts on code you don’t understand
  • you will have less code to read and understand for each story

Apply team registration code
Subscribe your team to this habit using one of your organization’s pre-purchased registration codes (see how this works).

What Changes

Those results come from changing these key behaviors.

Shift: Make an Honest Name

Apply a pattern to create an honest name without having to understand the code.

Shift: Use Obvious Nonsense

Reduce cognitive overload in the naming process.

Shift: Expand the Known

Build on the honest name with more information from the code.

Shift: Narrow the Unknown

Build on the honest name by noting what the code does not do.

Get Started!