## 4.3 Coordination and Reporting Agile practices have developed specific terms, rituals, formats and metrics to communicate efficiently and coordinate team efforts. However, an Agile Project Core Team (A-PCT) does not work in isolation. There might be other non-Agile teams in the project accompanied by various groups of stakeholders with specific informational needs and preferences. PM2-Agile addresses these needs by adjusting the types of information, formats, granularity, language and frequency of communication accordingly. The coordination between the A-PCT and other groups of stakeholders can be on different themes. The following themes are relevant for most types of IT projects. - **Planning** - The A-PCT has to provide a Release plan that is easy to understand and integrates with the overall project work plan. In addition, some content from the iteration plans can also be used outside the A-PCT. - **Reporting** - The specific progress metrics and the frequency of reporting of the A-PCT should be aligned with the accepted metrics for the other teams and stakeholders (e.g. from management layers). - **Architecture** - Architecture artefacts should be created following organisation standards so that impact assessment, reusability, interoperability and other types of analysis can be executed without additional overheads. - **Deployment and Transition** - The Project Core Team (PCT) and the Agile Project Core Team (A-PCT) should work with the IT operations team. Transparency enables collaboration which supports the integration of processes, such as Software Configuration Management. - **Risk** - The A-PCTs may capture both technical and other projects risks following the PM2 Risk Management Process and using the recommended artefacts (e.g. Risk Log). The **external coordination** between the A-PCT and other project layers and stakeholders is facilitated through regular project meetings and reports. External communication events include: - Project follow-up meetings - Project Status Reports - Demos and Deliverables Acceptance events Issues may occur in external coordination relating to the type and granularity of the planning and reporting unit. There should be three main groups of reporting and planning. - Delivery units (e.g. work packages, deliveries). - Functional units (e.g. use cases, business processes, capabilities, features). - Work units (e.g. work items like user stories, enabler stories, bugs). Wherever possible and applicable, these units should be linked to each other. For example, the smaller work items (stories) should be related and grouped into a functional unit (e.g., a feature). Consequently, a group of Features (functional units) should be linked to a specific delivery unit (for instance, a Delivery). This traceability will allow more effective external coordination by providing the stakeholders with a clear vision of current project execution and delivery. Internal coordination within an A-PCT is supported by open, frequent, efficient and face-to-face communication. The figure below shows several Internal communication ceremonies that include: - Daily Stand-up - Iteration Planning - Iteration Review - Iteration Retrospective ![[4.3 Communication.png]]