Skip to main content

Validation Checkpoints for Scrum of Scrums

Here’s a structured list of Validation Checkpoints for Scrum of Scrums (SoS) to ensure it delivers value and aligns with scaled agile best practices:

 Validation Checkpoints for Scrum of Scrums

  1. Progress Alignment

  • Are all teams aligned with the Sprint Goals?

  • What is the action plan for Spill over stories?

  • Is progress mapped against Epic/Release milestones?

  • Are team velocities stable, and any major deviations explained?

  1. Dependencies

  • Are cross-team dependencies and external dependencies are identified clearly?

  • Are dependency owners assigned and tracked?

  • Are upcoming dependencies planned (not last-minute surprises)?

  1. Blockers & Risks

  • Are there any blockers beyond team control?

  • Are escalations being addressed at the right level (Scrum Master vs Program)?

  • Are risks logged, assessed, and mitigated?

  1. Quality & Defects

  • Are defect trends (open/closed rate, severity) under control?

  • Is regression/integration testing on track?

  1. Delivery Readiness

  • Is the integration plan between teams clear and realistic?

  • Is the demo to Product team (end of sprint) prepared?

  • Any concerns with meeting release dates or milestones?

  1. Collaboration & Communication

  • Are teams sharing knowledge?

  • Are issues parked for deep-dive offline discussions?

  • Is there transparency in reporting blockers?

  1. Process Tracking

  • Perform thorough impact analysis before implementing code changes.

  • Developers to validate functional logic with SMEs before implementation

  • Leverage peer reviews more rigorously, especially for critical/shared components

  • Ensure developers write and execute unit tests

  • Reduce the Bug Sub Task % in the upcoming release.

  • Reduce the Bug Reopened % in the upcoming release.

  • Follow coding best practices and use static code analysis tools

  • Is Retrospective conducted for last sprints, Is RCA identified for the blockers and lessons are implemented?

  1. Action Tracking

  • Were last SoS action items closed?

  • Are new actions assigned, and time-bound?

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more