Skip to main content

Meetings

Along with Roles and Artifacts, Meetings are a composite component of Process Script. Any team can assign roles and write up documents with artifact titles. Regular meetings are where Roles are engaged interactively. Regular, attentive attendance are a must. Meetings are where Artifacts are put into practice and kept up to date. The output of one session is always the input of a later session. As such, a regular schedule, i.e. Cadence, must be implemented which produces the required input and output of a Process Meeting.

Process Meetings​

The Meetings specified by Process Script are:

• Cadence Planning
• The Stand-Up
• Requirements Refinement
• Cadence Retrospective
• Cadence Showcase

📄️ Planning

The purpose of Planning is to define the upcoming Cadence Goal and outline the associated deliverables. This involves establishing clear objectives for the next iteration or work cycle, ensuring that the team understands what needs to be achieved and what specific outputs are expected. By setting a well-defined Cadence Goal, the Delivery Team can focus their efforts on high-priority tasks, align their work with strategic objectives, and measure their progress effectively throughout the Cadence. Additionally, specifying deliverables ensures that all team members are aware of their responsibilities and the tangible outcomes they need to produce, thereby promoting accountability and facilitating smooth workflow management.

📄️ The Stand-Up

The Stand-Up is essential for providing regular progress updates on the Cadence Goal, ensuring that all team members are aligned and informed about what has been accomplished and what is planned for the day. It facilitates open communication during the implementation phase, allowing team members to discuss any challenges they are facing. By exposing progress blockers early, the Stand-Up enables the team to collaboratively address issues and make adjustments as needed, helping to maintain momentum and keep the Cadence on track.

📄️ Requirements Refinement

The purpose of Refinement of Requirements, or simply Refinement, is to translate product-centric requirements into implementation-ready development specifications. This process ensures that high-level product needs are clearly defined and broken down into actionable and precise tasks for the Delivery Team. By converting broad requirements into specific, manageable specifications, refinement helps streamline the development process and aligns the team’s efforts with the Product Owner’s descriptions.

📄️ Retrospective

Retrospective involves recording a journal of Cadence Goal and Deliverables at a regular cadence. This regular review and metrics collection allows for the collection of sentiments and statistical analysis. This documentation captures key insights, successes, and challenges encountered during the Cadence, providing a comprehensive record for evaluating performance and identifying areas for improvement. By maintaining this journal, the team can track progress over time, analyze trends, and make informed decisions to enhance future delivery cycles.