Quality begins with “A” – A for beginning….

“𝗤𝘂𝗮𝗹𝗶𝘁𝘆 𝗳𝗶𝗿𝘀𝘁” – have you ever started a project with this slogan? Quality is one of the most important parameters of projects, especially in the IT sector.

However, quality is also difficult to measure because there are many influencing factors. Even if some developers are satisfied with “it works for me”, quality is a comprehensive term with many definitions (right up to ISO/IEC 25010:2011 – which nobody likes to read…).

But one thing is now certain:

𝗤𝘂𝗮𝗹𝗶𝘁𝗮̈𝘁 𝗯𝗲𝗴𝗶𝗻𝗻𝘁 𝗮𝗺 𝗔𝗻𝗳𝗮𝗻𝗴.

This is because eliminating quality defects in IT projects becomes exponentially more expensive the later they are discovered.

– to correct a quality defect in a A͟n͟f͟o͟r͟d͟e͟r͟u͟n͟g͟s͟b͟e͟s͟c͟h͟r͟e͟i͟b͟u͟n͟g͟, is usually only a matter of a few minutes within the Word document in which the requirement is described (very, very cheap).

– rectifying a quality defect w͟ä͟h͟r͟e͟n͟d͟ ͟d͟e͟r͟ ͟E͟n͟t͟w͟i͟c͟k͟l͟u͟n͟g͟ is significantly more expensive. Source codes and documentation (including those that have already been accepted) have to be changed and new tests carried out.

– A quality defect that you discover at a͟u͟s͟g͟e͟l͟i͟e͟f͟e͟r͟t͟e͟n͟ ͟S͟o͟f͟t͟w͟a͟r͟e͟ can only be “caught” again with immense effort.

– and if you have to v͟o͟r͟ ͟G͟e͟r͟i͟c͟h͟t͟ ͟z͟i͟e͟h͟e͟n͟ because of a quality problem, then in addition to rectifying the defect you will also have to pay legal fees, compensation claims, expert opinions and much more.

Project managers and IT managers know this (in theory), but for reasons of time and budget, quality is usually only addressed when there are problems and it is almost too late. Then it gets really expensive.

𝗡𝗮𝗰𝗵𝗵𝗮𝗹𝘁𝗶𝗴𝗲 𝗤𝘂𝗮𝗹𝗶𝘁𝗮̈𝘁 𝗯𝗲𝗴𝗶𝗻𝗻𝘁 𝗱𝗮𝗵𝗲𝗿 𝗴𝗮𝗻𝘇 𝗮𝗺 𝗔𝗻𝗳𝗮𝗻𝗴! During project set-up, when recording and describing requirements, when creating a specification sheet! This saves time, money and nerves!

P.S.: no matter what phase you are in. Feel free to contact me! From requirements engineering to expert reports at Streitz Hoppen & Partner – IT experts – Quality first!