Note the title does not say that you need to use standards or processes. This is because each of us already use any of the established processes for everyday tasks. Although you probably already have some tried and tested procedure, you are required to have ask ourselves:
The first question draws attention to itself on the quality of the process itself. Do they reach their goal? Depending on the purpose you may ask this question: to provide and whether they stimulate the necessary level of cooperation? Do they contribute to an adequate interaction between the team of developers and customers? Whether they support the best of use of technical standards? Do they help to achieve quality goals?
Often people are not well known processes, which themselves and use it. For example, processes may interfere with the interaction of people, improvement of technical skill or simply do not meet the needs of the team. The man who says "I’ve never met a process that would have been to my liking," probably used a lot of good processes, but was simply ignorant of them.
Nevertheless, the visible quality processes contribute to a smoother flow of things. They stimulate the increase in skill, allowing the flexibility to adapt to the unique needs of each project. In other words, they respond to the needs of projects.
The second question draws attention to the quality of following the established processes. If you are performing their tasks improperly and inconsistently, ignoring the agreement, then no benefit from even a good process you do not get. Which means that the consistent use of quality assurance processes? This is when everyone clearly knows how to follow them, knows when and how to do it, and strictly comply with them. Naturally, such behavior is expected from the team …