I would say each developer also has their own process, which may be more or less or different than the organizational process. I find that good devs have a goo

I would say each developer also has their own process, which may be more or less or different than the organizational process. I find that good devs have a good personal process. I think being an expert sometimes means you know which rules should be followed, and which rules can be bent for certain circumstances, possibly even producing a better result. Novice programmers may not know all the consequences of their actions, so it is better for them to follow a strong rigorous process. Good results is also subjective. Does good results mean fast? Or that you can look at the code while not having to clean the vomit off your keyboard? Bug count? Getting it right the first time? Good UX? Knowing what you're going for and what counts is where the process should be pointing, but sometimes they are just rules for rules sake.