Why (having and following a) Process Matters?!

## Why?

A _humorous_ GIF explaining why working in a _team_ of software developers ***can*** be frustrating:
[](https://twitter.com/iamdevloper/status/789234931599835136)
https://twitter.com/iamdevloper/status/789234931599835136

The point is that when you are _alone_ you _feel_ like you can make progress _quickly_.
And when you work in a _large_ team in a "_big_" company
it can feel like trying to lift a freight train using a crowbar... 😭

The _reason_ working in large teams _often_ is so _painful_ is that:
+ either there is no process
+ or the process is poorly defined and nobody follows it
+ or you have a handful of "senior" people who don't think the process/steps apply to them...
+ or there are simply too many steps to get anything done so people just give up or short cut them!
+ or people rebel against "the system" and end up building something "_amazing_" that it turns out nobody wants because no stakeholder was consulted prior to build or the business has not "bought into" the idea...

Point is, when the steps in the process gets followed _everyone_ knows what is going on.
We have worked in places with ***literally*** dozens of steps just to _create_ a "_User Story_" in **Jira**! 😧
We have attempted to streamline our "_process_" down to the _minimum_ number of steps.
If you can spot an area for simplification, we would ***love*** to hear about it!! thanks! ❤️

relates to #44