I heard an analogy recently from one of my developers that processes are like walls: you want to work on your code, but there is a wall that prevents you; once you remove the wall, you can get to work faster. However, I deeply disagree with this analogy.
As an Agile Coach and Scrum Master, I value People and Interactions over Processes and Tools. However, it is very clear to me that process and tools can aid software development. For example:
- Scrum (if implemented correctly (and I agree that that's a big 'if')) can increase the speed at which the dev team delivers value to the end user;
- Pair programming, although it will slow you down a little (very little), it does generate higher quality code, a shared sense of code ownership (increased Bus Factor), and a faster leveling up of devs;
- Noisli: When I'm in deep-work mode, this app gets me in the flow so much faster;
- Retrospectives - the ultimate tool for a team to solve their own problems, for developers to build their dream work environment!
I could keep going on and on about this.
So what are your opinions on this? Are processes a wall for you? Or are they helpful? Can we bridge the gap between devs that think processes are walls and devs that don't?