Digging through some old writing, I found this list from 2008 describing qualities of a “good development process:”
- emerges over time. It is unique to your product and team.
- is well known and explicit.
- supports creative work while removing busy work.
- is ambient, simple, and usable.
- undergoes constant scrutiny and tweaking.
I think this list holds up pretty well. Whatever process you find yourself using is only ever a snapshot in time. A sample or snapshot is a healthy way to think process - your workflow is jointly created by your team to respond to your team’s needs.
This point of view stands in opposition to cargo cult adoptions of complex “agility at scale” methodologies.