Discussion about this post

User's avatar
Andre Leroux's avatar

Quality Engineering goes beyond meeting stakeholders requirements & expectations. Quality Software goes beyond understanding what our customers want; how teams collaborates; and good processes & practices.

Quality software includes maintainability, flexibility, interoperability, all these "invisible" requirements that make Software development much more easy; make any troubleshooting and updating a walk in the park. These criteria's might be under good "Processes & Practices", but not all teams have the same definition of what is good practices.

An application might meet all Customer's requirements and might please everyone; but if it's a pain for development to work in the software and if they struggle each time they touch it, then we don't have good quality software.

I've seen it many times when customers are happy, sales are going up, everyone is congradulating themselves, and then I raise my hand and say "the software is sh...t". Developpers are afraid to touch it. Fixing bugs takes weeks of regression (or pre-prod testing). We are stable in production, but quality of the software is not there.

Expand full comment
2 more comments...

No posts