Skip to content

Instantly share code, notes, and snippets.

@sobri909

sobri909/process_changes.md

Last active March 16, 2018 10:14
Show Gist options
  • Save sobri909/90f41437f52a33b726f7 to your computer and use it in GitHub Desktop.
Save sobri909/90f41437f52a33b726f7 to your computer and use it in GitHub Desktop.
Download ZIP
On Changing Processes
Raw
process_changes.md

On Changing Processes

  1. All else being equal, a simpler system is preferable to a more complex system.
  2. Complexity, structure, process, and size should only be added after a problem is identified.
  3. Such additions should attempt to solve the identified problem only. Avoid scope creep.
  4. If the problem can be solved by reducing rather than adding complexity, that solution is preferable.

A project or team should only have the structure, complexity, processes, and size necessary to solve identified problems, and no more. Start with the simplest form, and add to it only when necessary.

Questions to ask when evaluating process changes

  1. Does the change solve an identified problem?
  2. Does the change increase or reduce the complexity of the system?
  3. Will the change have negative side effects - will it create new problems?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment