Batch 09

Author: MrHinsh

site/content/resources/blog/2024/2024-09-05-the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know/data.index.classifications.json

@@ -865,11 +865,14 @@
   },
   "Accountability": {
     "category": "Accountability",
-    "calculated_at": "2025-02-11T13:17:10",
-    "ai_confidence": 80,
+    "calculated_at": "2025-03-11T00:20:52",
+    "ai_confidence": 72.0,
+    "ai_mentions": 15,
+    "ai_alignment": 32,
+    "ai_depth": 28,
     "non_ai_confidence": 50,
-    "final_score": 77.0,
-    "reasoning": "The content discusses the core accountability of Scrum Masters in ensuring team effectiveness and highlights the importance of ownership in their role, making accountability a primary theme.",
+    "final_score": 70.0,
+    "reasoning": "The content discusses the accountability of Scrum Masters in ensuring team effectiveness, which aligns well with the principles of ownership and responsibility in Agile. It highlights the importance of understanding Scrum practices and the role of Scrum Masters in fostering team dynamics. However, while accountability is a significant theme, the content also critiques the competence of Scrum Masters, which may detract from a purely positive discussion on accountability. Overall, the content provides a detailed exploration of the responsibilities of Scrum Masters, making accountability a primary focus.",
     "level": "Secondary"
   },
   "MVP": {

site/content/resources/blog/2025/2025-01-03-definition-of-done-objective-vs-subjective/data.index.classifications.json

@@ -442,11 +442,14 @@
   },
   "Empirical Process Control": {
     "category": "Empirical Process Control",
-    "calculated_at": "2025-02-11T14:51:38",
-    "ai_confidence": 85,
+    "calculated_at": "2025-03-11T00:15:56",
+    "ai_confidence": 78.0,
+    "ai_mentions": 15.0,
+    "ai_alignment": 35.0,
+    "ai_depth": 28.0,
     "non_ai_confidence": 10,
-    "final_score": 78.0,
-    "reasoning": "The content primarily discusses the Definition of Done (DoD) in Scrum, emphasising the importance of objective measures and iterative improvement, which aligns closely with the principles of empirical process control.",
+    "final_score": 71.0,
+    "reasoning": "The content discusses the Definition of Done (DoD) in Scrum, which is a key aspect of empirical process control as it emphasises objective measures of quality and the importance of adapting to feedback. However, while it touches on transparency and the iterative nature of Scrum, it does not deeply explore the broader principles of empirical process control or provide extensive examples or case studies. The focus is more on the DoD itself rather than a comprehensive discussion of empirical process control as a whole.",
     "level": "Secondary"
   },
   "Product Validation": {

site/content/resources/blog/2025/2025-01-11-why-handoffs-are-killing-your-agility/data.index.classifications.json

@@ -274,11 +274,14 @@
   },
   "Agile Frameworks": {
     "category": "Agile Frameworks",
-    "calculated_at": "2025-02-11T14:45:56",
-    "ai_confidence": 85,
+    "calculated_at": "2025-03-11T00:15:53",
+    "ai_confidence": 72.0,
+    "ai_mentions": 15.0,
+    "ai_alignment": 35.0,
+    "ai_depth": 22.0,
     "non_ai_confidence": 10,
-    "final_score": 78.0,
-    "reasoning": "Content primarily discusses the negative impact of handoffs on agility and promotes Agile principles such as cross-functional teams and continuous delivery, aligning closely with Agile frameworks.",
+    "final_score": 66.0,
+    "reasoning": "The content discusses the negative impact of handoffs on agility and suggests practices to eliminate them, which aligns with Agile principles. However, it primarily focuses on the issue of handoffs rather than providing a comprehensive exploration of Agile frameworks themselves. While it mentions Agile concepts and practices, it does not delve deeply into specific frameworks like Scrum or Kanban, nor does it provide a comparative analysis or case studies, which limits its alignment with the category.",
     "level": "Secondary"
   },
   "Scaling Agility": {

site/content/resources/blog/2025/2025-01-30-the-scrum-master-is-accountable-for-delivery/data.index.classifications.json

@@ -712,11 +712,14 @@
   },
   "Lean Principles": {
     "category": "Lean Principles",
-    "calculated_at": "2025-02-17T08:53:19",
-    "ai_confidence": 65,
+    "calculated_at": "2025-03-11T00:15:23",
+    "ai_confidence": 67.0,
+    "ai_mentions": 15.0,
+    "ai_alignment": 35.0,
+    "ai_depth": 50.0,
     "non_ai_confidence": 0,
-    "final_score": 58.0,
-    "reasoning": "The content discusses the importance of delivery and effectiveness in Scrum, touching on concepts of value maximisation and continuous improvement, which align with Lean Principles. However, the primary focus is on Scrum roles and responsibilities rather than Lean methodologies specifically.",
+    "final_score": 60.0,
+    "reasoning": "The content discusses the role of the Scrum Master in ensuring effective delivery and continuous improvement, which aligns with Lean principles of maximising value and minimising waste. However, the primary focus is on Scrum practices rather than Lean itself, leading to a moderate confidence score.",
     "level": "Tertiary"
   },
   "Agile Transformation": {

site/content/resources/blog/2025/2025-02-03-delivery-as-the-ultimate-measure-of-progress/data.index.classifications.json

@@ -595,11 +595,14 @@
   },
   "Agile Strategy": {
     "category": "Agile Strategy",
-    "calculated_at": "2025-02-11T14:36:49",
-    "ai_confidence": 85,
+    "calculated_at": "2025-03-11T00:15:20",
+    "ai_confidence": 82.0,
+    "ai_mentions": 15.0,
+    "ai_alignment": 35.0,
+    "ai_depth": 32.0,
     "non_ai_confidence": 0,
-    "final_score": 76.0,
-    "reasoning": "The content primarily discusses the importance of delivery in Scrum, aligning with Agile principles and strategies for continuous value delivery, which are central to Agile Strategy.",
+    "final_score": 74.0,
+    "reasoning": "The content primarily discusses the importance of delivery within the Scrum framework, which is a key aspect of Agile methodologies. It highlights the need for Scrum Teams to focus on delivering value to users rather than merely completing tasks. While it touches on Agile principles, the discussion is more centred on technical practices and the execution of Scrum rather than a broader strategic alignment with Agile methodologies. Therefore, while it aligns with some core themes of Agile Strategy, it lacks depth in strategic planning and organisational vision, leading to a high confidence score but not a perfect one.",
     "level": "Secondary"
   },
   "Continuous Delivery": {

site/content/resources/blog/2025/2025-02-06-stop-promoting-branches/data.index.classifications.json

@@ -112,12 +112,15 @@
   },
   "Digital Transformation": {
     "category": "Digital Transformation",
-    "calculated_at": "2025-02-17T08:53:18",
-    "ai_confidence": 60,
+    "calculated_at": "2025-03-11T00:15:17",
+    "ai_confidence": 32.0,
+    "ai_mentions": 15.0,
+    "ai_alignment": 25.0,
+    "ai_depth": 40.0,
     "non_ai_confidence": 0,
-    "final_score": 54.0,
-    "reasoning": "The content discusses modern software delivery practices and the need for agility in development processes, which aligns with digital transformation themes. However, it primarily focuses on specific branching strategies rather than a broader strategic adoption of digital technologies.",
-    "level": "Tertiary"
+    "final_score": 29.0,
+    "reasoning": "The content discusses software delivery models and branching strategies, which indirectly relate to digital transformation by emphasising agility and continuous delivery. However, it lacks a direct focus on the strategic adoption of digital technologies for business transformation, making it more about operational practices than a comprehensive discussion on digital transformation.",
+    "level": "Quaternary"
   },
   "Working Software": {
     "category": "Working Software",

site/content/resources/blog/2025/2025-02-06-testing-in-production-maximises-quality-and-value/data.index.classifications.json

@@ -454,11 +454,14 @@
   },
   "Product Validation": {
     "category": "Product Validation",
-    "calculated_at": "2025-02-11T14:25:16",
-    "ai_confidence": 85,
+    "calculated_at": "2025-03-11T00:15:05",
+    "ai_confidence": 72.0,
+    "ai_mentions": 15.0,
+    "ai_alignment": 35.0,
+    "ai_depth": 22.0,
     "non_ai_confidence": 10,
-    "final_score": 78.0,
-    "reasoning": "The content primarily discusses methodologies for testing product ideas with real users through audience-based deployment, emphasising the importance of user feedback and iterative testing to maximise quality and value. It aligns well with key topics such as customer feedback loops and the production-first mindset, making product validation a central theme.",
+    "final_score": 66.0,
+    "reasoning": "The content discusses audience-based deployment and its benefits for gathering real user feedback, which aligns with the core themes of product validation. However, it primarily focuses on deployment strategies rather than explicitly validating product ideas through user engagement. While it touches on user feedback and telemetry, the depth of discussion on methodologies for validating product concepts is limited.",
     "level": "Secondary"
   },
   "Azure Boards": {

site/content/resources/blog/2025/2025-02-10-without-delivery-there-is-no-value/data.index.classifications.json

@@ -154,11 +154,14 @@
   },
   "Decision Making": {
     "category": "Decision Making",
-    "calculated_at": "2025-02-11T14:10:46",
-    "ai_confidence": 85,
+    "calculated_at": "2025-03-11T00:15:09",
+    "ai_confidence": 82.0,
+    "ai_mentions": 15,
+    "ai_alignment": 32,
+    "ai_depth": 36,
     "non_ai_confidence": 0,
-    "final_score": 76.0,
-    "reasoning": "The content primarily discusses the importance of delivery in validating assumptions and making informed decisions based on feedback, aligning closely with evidence-based decision-making principles.",
+    "final_score": 74.0,
+    "reasoning": "The content extensively discusses the importance of delivery in validating assumptions and making informed decisions based on empirical evidence. It highlights the role of frequent releases in decision-making processes, emphasising the need for feedback loops and adaptation based on real-world data. The mention of metrics like DORA and the Standish Group’s CHAOS Report supports the evidence-based approach to decision-making. The depth of discussion on the costs of delayed delivery and the risks associated with untested assumptions further aligns with the principles of structured decision-making.",
     "level": "Secondary"
   },
   "Self Organisation": {

site/content/resources/blog/2025/2025-02-17-no-such-thing-as-a-junior-scrum-master/data.index.classifications.json

@@ -1240,11 +1240,14 @@
   },
   "Value Delivery": {
     "category": "Value Delivery",
-    "calculated_at": "2025-02-17T08:53:18",
-    "ai_confidence": 85,
+    "calculated_at": "2025-03-11T00:15:02",
+    "ai_confidence": 78.0,
+    "ai_mentions": 60.0,
+    "ai_alignment": 85.0,
+    "ai_depth": 75.0,
     "non_ai_confidence": 10,
-    "final_score": 78.0,
-    "reasoning": "The content primarily discusses the role of Scrum Masters in facilitating effective Scrum practices, which directly impacts the delivery of value within Agile frameworks. It emphasises the importance of mastery and experience in ensuring that Scrum Teams can deliver high-quality products and drive continuous improvement, aligning closely with the principles of value delivery.",
+    "final_score": 71.0,
+    "reasoning": "The content discusses the critical role of Scrum Masters in delivering value within Scrum Teams, emphasising the need for mastery in technical, business, and organisational domains. It aligns well with the principles of iterative development and the importance of effective leadership in enhancing team performance and customer satisfaction. However, while it touches on value delivery, the primary focus is on the qualifications and roles of Scrum Masters rather than broader value delivery strategies.",
     "level": "Secondary"
   },
   "Technical Excellence": {

site/content/resources/guides/detecting-agile-bs/data.index.classifications.json

@@ -40,11 +40,14 @@
   },
   "Pragmatic Thinking": {
     "category": "Pragmatic Thinking",
-    "calculated_at": "2025-02-13T15:48:28",
-    "ai_confidence": 80,
+    "calculated_at": "2025-03-11T00:20:13",
+    "ai_confidence": 78.0,
+    "ai_mentions": 15,
+    "ai_alignment": 32,
+    "ai_depth": 28,
     "non_ai_confidence": 0,
-    "final_score": 72.0,
-    "reasoning": "The content primarily discusses practical strategies for identifying genuine Agile practices versus superficial implementations, emphasising real-world applications of Agile and DevSecOps principles. It includes specific questions and flags that help navigate complexities in software development, aligning closely with the themes of pragmatic thinking.",
+    "final_score": 70.0,
+    "reasoning": "The content discusses practical strategies for identifying genuine Agile practices versus superficial implementations, which aligns well with pragmatic thinking. It provides specific questions and criteria for evaluating Agile projects, demonstrating a focus on real-world applications and problem-solving in complex environments. The depth of discussion is substantial, covering various aspects of Agile and DevSecOps, but it does not delve deeply into case studies or evidence-based management practices, which slightly lowers the score.",
     "level": "Secondary"
   },
   "Market Share": {

site/content/resources/guides/evidence-based-management-guide-2020/data.index.classifications.json

@@ -1135,11 +1135,14 @@
   },
   "Decision Theory": {
     "category": "Decision Theory",
-    "calculated_at": "2025-02-13T15:38:42",
-    "ai_confidence": 80,
+    "calculated_at": "2025-03-11T00:19:57",
+    "ai_confidence": 87.0,
+    "ai_mentions": 15,
+    "ai_alignment": 35,
+    "ai_depth": 30,
     "non_ai_confidence": 0,
-    "final_score": 72.0,
-    "reasoning": "The content primarily discusses Evidence-Based Management (EBM) as a framework for improving decision-making under uncertainty, focusing on goal setting, measuring outcomes, and adapting strategies based on empirical evidence, which aligns closely with key topics in Decision Theory.",
+    "final_score": 78.0,
+    "reasoning": "The content extensively discusses Evidence-Based Management (EBM) as a framework for improving decision-making under uncertainty, which aligns closely with the principles of Decision Theory. It covers key aspects such as setting strategic goals, measuring current and unrealized value, and using empirical evidence to inform decisions. The depth of discussion on how organizations can adapt their goals based on feedback and experimentation further supports its relevance to Decision Theory.",
     "level": "Secondary"
   },
   "Technical Excellence": {

site/content/resources/guides/evidence-based-management-guide/data.index.classifications.json

@@ -1153,11 +1153,14 @@
   },
   "Transparency and Accountability": {
     "category": "Transparency and Accountability",
-    "calculated_at": "2025-02-12T14:05:14",
-    "ai_confidence": 70,
+    "calculated_at": "2025-03-11T00:20:09",
+    "ai_confidence": 78.0,
+    "ai_mentions": 15.0,
+    "ai_alignment": 35.0,
+    "ai_depth": 28.0,
     "non_ai_confidence": 10,
-    "final_score": 64.0,
-    "reasoning": "The content discusses the importance of transparency in defining measurable goals and encourages organizational alignment through shared information. However, the primary focus is on Evidence-Based Management and goal-setting rather than solely on transparency and accountability.",
+    "final_score": 71.0,
+    "reasoning": "The content discusses the importance of transparency in setting measurable goals and encourages sharing information to foster alignment within the organization. It also highlights the need for accountability through the use of evidence-based management practices. However, while these themes are present, they are not the primary focus of the content, which is more about the framework of Evidence-Based Management and its application in achieving goals.",
     "level": "Secondary"
   },
   "Practical Techniques and Tooling": {

site/content/resources/guides/evidence-based-portfolio-management/data.index.classifications.json

@@ -280,11 +280,14 @@
   },
   "Scaling Agility": {
     "category": "Scaling Agility",
-    "calculated_at": "2025-02-12T14:02:12",
-    "ai_confidence": 70,
+    "calculated_at": "2025-03-11T00:20:03",
+    "ai_confidence": 68.0,
+    "ai_mentions": 15.0,
+    "ai_alignment": 35.0,
+    "ai_depth": 18.0,
     "non_ai_confidence": 10,
-    "final_score": 64.0,
-    "reasoning": "The content discusses the need for agile principles to extend beyond individual teams to achieve true business agility, indicating a focus on scaling agility. However, it primarily addresses the challenges of traditional management practices rather than specific frameworks or strategies for scaling agility.",
+    "final_score": 62.0,
+    "reasoning": "The content discusses the need for agile principles to extend beyond individual teams, which aligns with the core theme of scaling agility. However, it lacks specific frameworks or detailed strategies for implementing these principles at an organisational level, resulting in a moderate confidence score.",
     "level": "Secondary"
   },
   "Team Collaboration": {

site/content/resources/guides/kanban-guide-for-scrum-teams/data.index.classifications.json

@@ -1312,11 +1312,14 @@
   },
   "Metrics and Learning": {
     "category": "Metrics and Learning",
-    "calculated_at": "2025-02-12T13:56:39",
-    "ai_confidence": 80,
+    "calculated_at": "2025-03-11T00:19:54",
+    "ai_confidence": 87.0,
+    "ai_mentions": 80.0,
+    "ai_alignment": 90.0,
+    "ai_depth": 85.0,
     "non_ai_confidence": 20,
-    "final_score": 74.0,
-    "reasoning": "The content primarily discusses the integration of Kanban practices with Scrum, focusing on flow metrics such as Work in Progress, Cycle Time, and Throughput, which are essential for evidence-based decision-making and continuous improvement in Agile environments.",
+    "final_score": 80.0,
+    "reasoning": "The content extensively discusses the role of metrics in the context of Kanban and Scrum, particularly focusing on flow metrics such as Work in Progress (WIP), Cycle Time, Work Item Age, and Throughput. It aligns well with the core themes of the 'Metrics and Learning' category by emphasising evidence-based decision-making and the iterative learning cycle through the use of these metrics. The depth of discussion is significant, covering various practices and their implications for continuous improvement within Scrum teams. Overall, the content is highly relevant to the category, making it a strong fit.",
     "level": "Secondary"
   },
   "Application Lifecycle Management": {

site/content/resources/guides/kanban-guide/data.index.classifications.json

@@ -250,11 +250,14 @@
   },
   "Strategy": {
     "category": "Strategy",
-    "calculated_at": "2025-02-12T13:52:52",
-    "ai_confidence": 80,
+    "calculated_at": "2025-03-11T00:20:19",
+    "ai_confidence": 78.0,
+    "ai_mentions": 15,
+    "ai_alignment": 32,
+    "ai_depth": 29,
     "non_ai_confidence": 50,
-    "final_score": 77.0,
-    "reasoning": "The content primarily discusses the Kanban strategy, its practices, and how it optimises value delivery, which aligns closely with strategic approaches within Agile frameworks.",
+    "final_score": 75.0,
+    "reasoning": "The content extensively discusses Kanban as a strategy for optimising value delivery and workflow management, aligning well with the Strategy category's focus on Agile methodologies. It provides detailed insights into Kanban practices, metrics, and continuous improvement, demonstrating a strong conceptual alignment with strategic approaches in Agile environments. The depth of discussion is significant, covering various aspects of Kanban, though it does not explicitly mention Agile or Scrum frameworks, which slightly lowers the confidence score.",
     "level": "Secondary"
   },
   "Ability to Innovate": {

site/content/resources/guides/manifesto-for-agile-software-development/data.index.classifications.json

@@ -346,11 +346,14 @@
   },
   "Software Development": {
     "category": "Software Development",
-    "calculated_at": "2025-02-12T13:48:57",
-    "ai_confidence": 90,
+    "calculated_at": "2025-03-11T00:20:16",
+    "ai_confidence": 92.0,
+    "ai_mentions": 20.0,
+    "ai_alignment": 40.0,
+    "ai_depth": 32.0,
     "non_ai_confidence": 20,
-    "final_score": 83.0,
-    "reasoning": "Content primarily discusses the Agile Manifesto, which is a foundational document in software development methodologies, particularly Agile practices.",
+    "final_score": 85.0,
+    "reasoning": "The content explicitly discusses the Agile Manifesto, which is a foundational document in software development methodologies, particularly Agile. It directly mentions key Agile principles that align closely with the core themes of the Software Development category, such as customer collaboration, responding to change, and delivering working software. The depth of discussion is substantial, as it outlines multiple principles that guide Agile practices, demonstrating a thorough understanding of the methodology. Overall, the content is highly relevant to software development, justifying a high confidence score.",
     "level": "Primary"
   },
   "Engineering Excellence": {