Why (having and following a) Process Matters?!

[nelsonic]

Why?

A humorous GIF explaining why working in a team of software developers can be frustrating: 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

[iteles]

Much needed clarification, I find myself explaining this all the time :+1: