^ [[3 PM2-Agile – Overview]] ## 3.6 Tailoring & Customisation PM2-Agile should not be seen as a one-size-fits-all approach. Rather, it should be **tailored to address the specific business and project conditions** and constraints and allowed to evolve as the project teams learn and discover more (regarding the environment and the solution) through each iteration, release or project. Tailoring refers to changing specific parts of the methodology, such as **process steps**, **artefacts contents** or the **distribution of responsibilities** amongst the various roles. Organisations do this to adapt the methodology to the specific needs of their structure and culture, and to align with their processes, policies, etc. Tailoring can be also carried out at other levels like a Division, a department or even a smaller sector, and applied to all its projects. **The Development Handbook** (see section 7 ”Artefacts”) **documents and describes ==how and why== PM2-Agile has been tailored** for a particular project so that it better serves the project needs and goals. This typically includes: - the **rationale** for tailoring and deviations; - **information about variations** from the standard practices, and why (typically by identifying artefacts or tools and techniques added or removed); - tailoring of **Roles & Responsibilities**; - **tool** and/or **medium** and format used **for each artefact**; - references to **other guidelines** and information that the project may use in addition to PM2-Agile and PM2; - what (development-specific) **reviews** will be performed and their **level of formality**; - procedures and **artefacts** for **reporting progress, performing measurements, managing requirements, managing change requests**, etc; - **configuration** strategy development-specific assets; - **responsibilities** for review and approval (a RASCI table used). The following list provides typical activities or ==key considerations when tailoring==: - Involve appropriate **stakeholders**. - Identify and create awareness regarding the **mandatory policies and procedures** to be respected within the organisation for all Agile team members. - Decide what **project-specific content** is needed. - Capture/update **glossary of terms** (definitions, acronyms, and abbreviations) specific to the task at hand (project-wide glossary or specific-area process). - Capture **references** (documents important to the task at hand). - Decide how and to what extent work will be **documented**. - Make sure that the **project organisation**, project level and Agile-level **responsibilities** and **interfaces** are **described and clearly understood**. - Decide which **tools** will be used to create and maintain work products. - Ensure the right tools and infrastructure are available and the team **knows how to use them**. - Be aware of available **metrics and reports** and decide which ones you will use and how often. - Determine that team has the **training** and **resources**, including personnel that they require. - **Review and agree on the tailoring**. Next: [[4 PM2-Agile Themes]]