^ [[The PM2-Agile Guide v3.0.1]] # 7 Artefacts Documenting the work planned and performed in the Agile layer is critical in increasing transparency and coordination between the different layers of the PM2 project organisation (i.e. between the directing, managing and performing Agile layers). Supporting PM2-Agile is a set of artefacts used to capture and document information regarding the management approach and Agile Project Core Team (A-PCT) activities, milestones, issues and progress reporting. These artefacts are grouped in three categories: Agile-specific artefacts, Coordination and Reporting artefacts, and IT governance artefacts (common to all IT projects, regardless of the management approach chosen). | Artefact type | Description | |:----------------------- |:----------- | | IT governance artefacts | Provide the information requested by the Organisation ́s IT Governance. They consist of the Business Case, Project Charter, <br> Architecture Overview, and Operational Model documents. | | Agile-specific artefacts | Capture information for planning specific Agile processes, activities, releases, iterations and other milestones. | | Coordination & reporting Artefacts | Capture the information needed to coordinate between overall project activities and those undertaken by the Agile Project <br> Core Team (A-PCT) giving the Project Manager (PM) visibility of the domain-specific activities, issues, milestones and progress. | Artefacts that support project work based on PM2-Agile. - Business Case and Project Charter - Architecture Overview - Operational Model - Development Handbook (==becomes part of the overall Project Handbook==) - Development Work Plan (==becomes part of the overall Project Work Plan==) - PM2-Agile Logs - Deployment Plan - Test Plans - Development Status Report (==becomes part of the Project Status Reports==) ![[7 PM2 and PM2-Agile (combined) Artefacts Landscape.png]] ## [[7.1 IT Governance Artefacts]] ## [[7.2 Agile-specific Artefacts]] ## [[7.3 Coordination & Reporting Artefacts]]