improved the clarity on the quality maturity model (#48)

docs/quality-maturity-model/01-overview.md

@@ -34,9 +34,10 @@ The model is an essential tool that offers guidance for achieving our ultimate g
 
 ![Example radar chart](/img/quality-maturity-model/radar-chart.png)
 
-Think of our software quality maturity model as a **multi-faceted radar chart**. Each facet, or dimension, represents a critical area of team's capability to build quality software at speed. Each dimension is divided into five levels, ranging from 1 to 5, with level 1 being the basic understanding and level 5 signifying mastery.
+Think of our software quality maturity model as a **multi-faceted radar chart**. Each facet, or dimension, represents a critical area of team's capability to build quality software at speed. 
+Each dimension is divided into five levels, ranging from 1 to 5, with level 1 being the basic understanding and level 5 signifying mastery.
 
-By understanding where each project currently stands on each dimension, it is possible to identify specific areas of improvement, plan actionable improvements, and track progress over time.
+Evaluating projects across multiple dimensions enables us to identify improvement opportunities, implement solutions, and monitor their impact.
 
 In terms of levels within each dimension, it's important to understand the nuanced distinctions that guide a project's maturity journey:
 

docs/quality-maturity-model/02-objectives.md

@@ -1,21 +1,18 @@
-# Objectives
+# Objectives and Benefits
 
-## Establish a baseline for engineering maturity
+## Objectives
 
-The **initial review** provides a **snapshot** of the organization/project’s current quality engineering maturity, enabling introspection and fostering discussions on how to improve.
+- **Establish a baseline for capability maturity**: The **initial review** provides a **snapshot** of the project’s current capability maturity, enabling introspection and fostering discussions on how to improve.
+- **Identify strengths and areas for improvement**: Understanding the capability maturity helps to pinpoint **strengths and weaknesses**, rewarding effective practices and addressing areas needing improvement, leading to **continuous, measurable, and evidence-based progress**.
+- **Promote a culture of continuous improvement**: Adopting the quality maturity model enables projects to set goals, assess effectiveness, and adapt proactively, embedding quality in every development stage to enhance operational efficiency, customer satisfaction, and reduce defects and rework costs.
+- **Embed quality-centric practices**: Enhance software development capabilities across the project by embedding quality-centric practices into the cultural and operational framework.
+- **Chart a course for where you aspire to be**: Let's not just measure where we are, but chart a course for where we aspire to be!
 
-## Identify strengths and areas for improvement
 
-Understanding the software quality maturity helps to pinpoint **strengths and weaknesses**, rewarding effective practices and addressing areas needing improvement, leading to **continuous, measurable, and evidence-based progress**.
+## Benefits
 
-## Promote a culture of continuous improvement
-
-Adopting the quality maturity model enables organizations/projects to set goals, assess effectiveness, and adapt proactively, embedding quality in every development stage to enhance operational efficiency, customer satisfaction, and reduce defects and rework costs.
-
-## Embed quality-centric practices
-
-Enhance software development capabilities across the organization/project by embedding quality-centric practices into the cultural and operational framework.
-
-## Chart a course for where you aspire to be
-
-Let's not just measure where IO is, but chart a course for where it aspires to be!
+- **Operational Efficiency**: Streamlined workflows, reduced rework, minimized waste, fewer defects, and faster delivery cycles.
+- **Strategic Clarity and Focus**: The model offers a structured framework that breaks down complex development processes into measurable maturity levels. This provides you with a clear picture of where your team stands, what their strengths are, and which areas need improvement. It helps you prioritize efforts strategically based on data rather than gut feelings. This clarity is essential for aligning teams on shared goals and ensuring resources are directed where they matter most.
+- **Risk Mitigation**: The model helps you identify early-stage risks – like quality gaps, inefficient processes, or collaboration breakdowns – before they manifest into costly product defects or delays. This proactive risk management approach allows teams to focus on preventing issues, rather than fixing them post-launch, which can significantly improve product reliability and reduce time wasted on firefighting.
+- **Clear Roadmap for Continuous Improvement**: The step-by-step nature of the model makes it easy to see what’s next. No guesswork – just a clear, actionable path to progress.
+- **Expert Guidance**: Instead of navigating through trial and error, the model is guided by experts with extensive experience across various SDLCs, ensuring the recommendations are both practical and impactful.

docs/quality-maturity-model/03-how-it-works.md

@@ -8,32 +8,23 @@
 
 Assess, reflect, act!
 
-1.  Assess where you stand on each dimension (initial review).
-1.  Reflect on your current practices (periodic review).
-1.  Act upon the feedback, laying a clear path toward the next level (continuous improvement).
+1. Assess where you stand on each dimension (initial review).
+2. Reflect on your current practices (periodic reviews).
+3. Act upon the feedback, laying a clear path toward the next level (continuous improvement).
 
 :::
 
--   **Initial review**: conducted by program mentors with project leaders and dimension owners to establish a baseline understanding of current practices and identify areas for improvements.
--   **Ongoing reviews**: regular reviews and updates to track progress, guided by a radar chart visualization representing various quality dimensions and maturity levels.
+## Timeline
 
-## Initial review
+Below is a timeline that outlines how our projects interact throughout the engagement process.
 
-Conducted by a program mentor with project leaders and dimension owners to establish a baseline understanding of current practices and identify improvement areas.
+1. **Introduction (30 minutes)**: A program mentor is assigned to the project. They begin by meeting with project leadership to introduce the model, explain its benefits, and answer any initial questions.
+2. **Dimension Owners Selection**:  Project leadership identifies and assigns "Dimension Owners." These are individuals with expertise in the 14 key areas. They will be responsible for assessing their respective areas.
+3. **Preparation & Evidence Gathering (30 minutes per dimension)**: The mentor guides each Dimension Owner through a brief preparatory task. This involves understanding the maturity level descriptions, gathering relevant evidence (e.g., process documentation, metrics), and preparing to discuss their findings.
+4. **Evidence Review Meetings (60 minutes per dimension)**:  The mentor holds focused meetings with each Dimension Owner. Together, they review the evidence, agree on the current maturity level for each dimension, and identify key opportunities for improvement.
+5. **Review Report & Findings**: The mentor compiles the results into a comprehensive report. This report details the maturity level for each dimension and provides actionable recommendations and priorities tailored to project specific needs.
 
-### Initial review process
+## Continuous Growth, Not One-Time Change
 
--   **Program mentors**: mentor assigned to the project.
--   **Introduction and training**: 30-minute intro session to understand the model and process.
--   **Dimension ownership**: project leaders appoint dimension review owners for each dimension.
--   **Evidence review**: mentors conduct 30-minute meetings with dimension owners to review evidence, determine current levels, and identify potential improvements.
--   **Summary report**: mentors compile and fine-tune a report based on the peer-review, which is then shared with project leadership and the wider organization.
-
-## Key roles
-
--   **Program mentor**: facilitate the review process, ensuring consistent application and alignment with organizational goals.
--   **Project leaders and dimension owners**: engage actively in the review process, implement improvements, and champion quality within their teams and projects.
-
-## Time investment
-
-A complete review requires 6 to 16 man-hours (~1h per dimension), primarily involving the project leadership roles.
+The model is built around continuous improvement, meaning you’ll always have a clear direction for growth. The goal isn’t to overwhelm the team with 
+drastic changes but to help them steadily improve with small, impactful adjustments over time. It’s an ongoing journey that grows alongside the team’s capabilities.

docs/quality-maturity-model/resources/faqs.md

@@ -10,40 +10,14 @@ The model emphasizes continuous improvement, ownership, and quality integration
 
 ## What does applying the quality maturity model imply, and how does it work in practice?
 
-:::info
-
 Applying the quality maturity model involves a non-prescriptive, peer-reviewed process at project level against high-level industry standards and common sense, without enforcing any measures or practices.
 
 **Each project is expected to independently establish and track progress metrics**, focusing on continuous improvement and consistently delivering user value.
 
-The **initial review offers a snapshot** of the company's quality engineering maturity. It's an opportunity for introspection, allowing projects and the organization as a whole to start productive discussions on improvement.
+The **initial review offers a snapshot** of the project's cpability maturity. It's an opportunity for introspection, allowing teams to start productive discussions on improvement.
 
 This is not about enforcement. Rather, it's about **empowering** each project to chart its own path toward better software delivery.
 
-:::
-
-The initial review is the **baseline**. It's a snapshot that helps to understand the current state in the quality engineering maturity landscape. This is where introspection meets action, enabling productive discussions for improvement.
-
-The application of this model involves **a structured review process**, the involvement of various key roles, and the creation of personalized action plans for improvement based on the unique needs and goals of each project. Here's how it works:
-
-### Initial review
-
--   Involves an evidence-based, peer-reviewed process that compares current practices and outcomes at the project level with a high-level set of domain practices covering the entire SDLC.
--   **Roles involved**: various key roles participate in the review process, ensuring a comprehensive and accountable approach.
--   **Baseline and tracking**: after the initial review, the model establishes a baseline for each project. projects then autonomously track and measure progress, focusing on continuous improvement and delivering value to their users.
-
-### Outcomes and recommendations
-
--   **Visibility and insights**: covering the entire SDLC, the model provides clear insights into strengths, weaknesses, and opportunities, both at the project and organizational levels.
--   **Customized recommendations**: rather than being prescriptive, the model suggests potential improvements. These are collaboratively formulated by project leaders, dimension owners, and program mentors, grounded in industry proven practices and methods, and common sense.
--   **Culture of improvement**: this model stresses cultural and behavioral changes for continuous improvement. The model aims for strategic, proactive problem-solving and encourages projects to focus on self-improvement.
--   **Autonomy and alignment**: after the initial review, projects autonomously track and measure progress with a focus on continuous improvement and delivering value to their users.
--   **Customized approach**: the model is designed to fit into the specific culture and workflow of the organization. It encourages the creation of customized action plans based on the specific strengths and weaknesses identified at each level. This personalized approach is key to ensuring that the model is effectively integrated and utilized within the organization​.
--   **Tracking progression and decision-making**: utilizing the model allows projects to track their progression across various dimensions. Achieving a higher level of maturity empowers them to leverage data and metrics for insightful **data and evidence-based decision-making processes**. The success indicators at the earlier stages include:
-    -   increased customer satisfaction
-    -   reduced product defects
-    -   improved operational efficiency, and
-    -   minimized costs associated with reworks​.
 
 ## How much time does the initial review take?
 
@@ -67,20 +41,6 @@ Through a **comprehensive dashboard**, presenting a radar chart of the current s
 
 The radar chart, alongside summary reviews, offers a transparent view of areas of excellence and areas for growth.
 
-## How is success or business value quantified through the implementation of the quality maturity model?
-
-:::info
-
-The results provided by the quality maturity model help increase the **transparency** and **confidence** on the project’s strategy, approaches, current status, and risks. It offers all stakeholders clarity of the product vision, what success looks like, and how success is measured inside the project.
-
-:::
-
-Utilizing the quality maturity model, projects can track their progression across various dimensions and levels. It's essential to note that achieving **level 4** across these dimensions empowers IO's projects to leverage **data and metrics** for insightful decision-making, subsequently measuring the **tangible business value** of diverse initiatives.
-
-Before this stage, success indicators are rooted in the execution of intentional quality strategies. During this crucial period, both the strategic approach to quality and the benchmarks set by the quality maturity model serve as the projects' compass, setting the fastest path to success. They guide the company toward a **data- and evidence-based decision-making process**.
-
-Until that pinnacle is reached, the yardstick for measuring success through quality strategies will primarily be increased customer satisfaction, diminished product defects, elevated operational efficiency, and minimized costs associated with reworks.
-
 ## Why should the initial review process involve various key roles instead of being exclusively conducted by the software engineers in test?
 
 In addressing the question of why the initial quality maturity review should involve various key roles beyond just software engineers in test, it's crucial to understand that _while quality is everyone's responsibility, it can paradoxically become no one's responsibility if not properly managed_. This is where the concept of _accountability_ becomes vital.
@@ -168,19 +128,3 @@ IO's model encourages projects to focus on self-improvement rather than competit
 IO's model not only integrates quality-centric practices within a cultural and operational framework to enhance software development practices across various projects in the organization. It also actively involves key actors from different roles within each project, alongside the **program manager**. This inclusive approach ensures that the project has immediate access to the entire spectrum of knowledge available in the organization.
 
 **This model champions a holistic, well-rounded strategy for growth and continuous improvement**. It is visually represented and strategically crafted to foster significant advancements in software quality, leveraging the collective expertise and collaboration of all involved parties.
-
-## What is the mentors group?
-
-The mentors group, getting inspiration from Cardano's Constitutional Committee approach, consists of independent experts in quality engineering and quality maturity model, ensuring consistent application of the model across all projects.
-
-The mentors group includes all program mentors. This group collectively decides when to grant a specific level to a project and when to approve a new mentor. The aim is the **consistent** application of the model across projects, ensuring there's no room for perceived subjectivity.
-
-### How to become a program mentor?
-
-Becoming a program mentor requires deep knowledge of quality engineering, quality strategy, and the quality maturity model, and then request an existing mentor to be included in the group.
-
-### What are the attributes of a program mentor?
-
-The program mentor, belonging to the Quality Control Initiative (QCI) group, collaborates with squads and projects, providing assistance to help them progress through the ladder/model.
-
-For squads and projects, the program mentor will serve as their point of contact within the larger community of software quality engineering experts.

docs/quality-strategy/01-intro-quality-strategy.md

@@ -42,7 +42,7 @@ Now, with your destination in mind, here's how a Quality Strategy paves the way
 6.  **Reflect and learn:** The journey doesn't end when you reach your destination. Gather feedback from your passengers (users), reflect on what went well and what could be improved, and use that knowledge to make your next software adventure even better. Every road trip teaches you something new!
 
 
-To help you chart your course, we offer a **[Quality Strategy Template](https://input-output-hk.github.io/quality-engineering/docs/quality-strategy/resources/quality-strategy-template/)**. 
+To help you chart your course, we created a **[Quality Strategy Template](https://input-output-hk.github.io/quality-engineering/docs/quality-strategy/resources/quality-strategy-template/)**. 
 It's a blank canvas, a starting point for you to fill in with your own specific goals, processes, and quality checks. It's your unique story to tell, your personalized roadmap to success.
 
 So, before you start your next software adventure, ask yourself: **What's my Quality Strategy? Where am I going, and how will I get there? How will we build quality software efficiently and effectively?**

src/pages/index.tsx

@@ -8,7 +8,7 @@ const features = [
 	{
 		title: 'Quality Maturity Model',
 		description:
-			'Our peer-review, evidence-based tool to support projects deliver high-quality products effectively and efficiently.',
+			'Our peer-review and evidence-based tool to support projects deliver high-quality products effectively and efficiently.',
 		image: './img/qmm-icon.png',
 		href: '/docs/quality-maturity-model/overview',
 	},