A thought behind
Why quality engineering CoE @INVINCIX
Pressuring challenges with strong constraints
Accelerated changes, disruptive innovations, and a globalized competition in a BANI (‘Brittle', ‘Anxious', ‘Nonlinear' and ‘Incomprehensible’) world are key traits of the so-called “digital transformation”. In that context where best practices are easily replicated, competitive advantages through operational excellence are at best, temporary.
Organizations are therefore facing numerous digital challenges to survive:
- Continuously deliver value to remain competitive.
- Make investments and choices with low predictability.
- Deliver successful experiences to “users” we don’t directly interact with.
- Deliver abstract increments fast, and adapt them through experiments.
- Streamline end-to-end complex and interdependent processes.
Siloed initiatives end to end up as waste
Siloed endeavours risk scattering resources without delivering commensurate gains, underscoring the critical importance of a focused, holistic approach to achieve substantial and enduring business improvement, ensuring that resources are utilized efficiently and wastage is minimized.
Short-term speed results in business failure
This model fails to survive in an competitive, unpredictable and complex digital environment where sustainable software speed is the only competitive advantage that can keep a continuous flow of value delivery.
Digital business speed is mandatory
Many organizations have the only choice to go digital to survive, but face many problems when trying to deliver software with always more speed: increased lead-time, rework, and recurring problems complex to understand where it is not only a matter or adopting DevOps, Agile, or a specific tooling.
INVINCIX CoE principle
Quality engineering is not quality assurance
“Quality engineering” can make us think that the goal is to engineer quality into the software delivery process with more testing automation and integration within the pipeline. While these improvements are needed, they are clearly not sufficient to address non-technical topics such as organization or collaboration.
Software production results from the collaboration of interdependent parts of its system composed by people, processes, and technology. The injection of quality can therefore not be limited to the software delivery pipeline and must cover the entire areas altogether composing the software production system.
Quality engineering applies total quality management to software production through a systemic approach that builds quality at speed capabilities for sustainable business speed.
INVINCIX QE CoE Boundaries
“Proof of concept” to “Global Platform”
INVINCIX QE CoE
Distinctive Framework –Access / Accelerate / Architect in a vicious cycle
The paradigm shift of Quality Engineering relies on the following principles:
Business depends on software Quality and Speed.
Quality embraces the entire software production system.
Speed is sustainable only through built-in quality.
INVINCIX QE CoE
Distinctive Framework – KPIs – QS / MAMOS / O2
Access
Identify quality and speed pains
2 Pains Types
Quality pain
Speed pain
Architect
Resolve structurally with MAMOS
5 System Areas
Methods
Architecture
Management
Organisation
Skills
Accelerate
Quality engineering for quality at speed
2 Delivery Types
Outcomes
Outputs
INVINCIX QE CoE Principle
QS “Quality Vs. Speed” Battle made interesting
Quality Pains are more subjective but can more easily talk to multiple stakeholders that are not necessarily familiar with the internals of software production. They can have different forms from dependency on one person, or lack of usability.
Quality at Speed Pains The first two critical dimensions are Quality Pains and Speed Pains. Quality Pains encompass challenges related to the different facets of software production quality, while Speed Pains address the hurdles of achieving rapid and efficient software delivery at different levels of the organization.
Speed Pains are more easily supported by metrics and numbers being more factual. The challenge in that case relies more on consolidating and framing correctly the value in perspective and compared to others.
INVINCIX QE CoE Principle
QS problem solved using MAMOS
At the heart of INVINCIX QE is the MAMOS software production system that encapsulates the key principles and practices for building Quality at Speed capabilities, ensuring alignment and coherence across various aspects of software development through three levels.
INVINCIX CoE begins with
Setting up the MAMOS context with customer
Methods
- Focus
- Plan
- Design
- Specify
- Implement
- Deliver
- Deploy
- Operate
- Learn
- Improve
Architecture
- Urbanization
- Make or Buy
- Modularity
- Integration
- Security
- Self-Service
- Observability
- Resilience
- Experiments
- Flexibility
Management
- Vision
- Alignment
- Choices
- Collaboration
- Empowerment
- Performance
- Risks
- Fail Fast
- Measurement
- Development
Organization
- Design Choices
- Commitment
- Structure
- Communication
- Leadership
- Management
- Engagement
- Planning
- Organizational Learning
- Organizational Culture
Skills
- Expertise Mapping
- Strategic Partnerships
- Remote Enablement