^ [[3 PM2-Agile – Overview]]
# 3.5 PM2-Agile Artefacts and Documentation
Agile does not mean ‘no documentation’, but rather just enough. ‘**Enough**’ is defined by both the **needs of project** and by the the corporate requirements for **transparency, traceability, and control**.
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 layers).
Project documentation (as a **source of information and knowledge**) becomes increasingly **relevant and useful outside the boundaries of the project** for decisions at the cross-/multi-project (or ‘programme and portfolio’) levels. Therefore, Agile teams need to produce **documentation that is enterprise-aware** (in terms of its content, structure and language), and simultaneously standardised within the organisation and aligned with PM2 documentation requirements.
A set of artefacts support the use of PM2-Agile. These artefacts are used to capture and document information regarding the **management approach**, specific **(development) activities, milestones, issues and progress reporting**.
These artefacts are grouped into **three categories**: IT governance artefacts (which are common to all IT projects, regardless of the management approach chosen), Agile (development) specific artefacts and Coordination & Reporting artefacts.
| Artefact Type | Description |
|:-------------------------------------- |:----------- |
| IT Governance Artefacts | Provide the information requested by the Organisation’s IT Governance. These consist of the Business Case, Project Charter, Architecture Overview, and Operational Model documents. |
| Agile (development) Specific Artefacts | Capture information regarding the planning of specific <br> (development) processes, activities, releases, iterations <br> and other milestones. |
| Coordination & Reporting Artefacts | Capture the information needed to coordinate the overall <br> project activities with those undertaken by the Agile <br> Project Core Team (A-PCT), and to ensure that the Project Manager has visibility of the domain- specific activities, issues, milestones and progress. |
The following **artefacts 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 Reports==).
![[3.5 PM2-Agile (combined) Artefacts Landscape.png]]
Note that as per the IT Governance (see section 7-Artefacts), the following documents are **mandatory** for **projects that include information systems as part of the solution**.
- Business Case.
- Project Charter.
- Architecture Overview.
- Operational Model.
Depending on the Organisation’s structure, the IT Governance **may request additional artefacts** to the ones mentioned above.
Next: [[3.6 Tailoring & Customisation]]