### 7.2.2 Development Work Plan The Development Work Plan gathers the relevant information that helps to manage the development aspect of the project. Viewed as a container of different perspectives on what needs to be done and how the development goals will be achieved. It **includes the Work Items List (WIL), the corresponding Release Plan and the supporting iterations**. These tree elements allow the Agile Project Core Team (A-PCT) to set and manage the other project organisation members’ expectations. The Development Work Plan is a **living artefact** that must be kept current by incorporating **new information details** and **work progress status** as they become available. It should be updated as often as necessary to capture and incorporate any **changing business priorities and needs**, including **changes in the Work Items List (WIL)** or in the contents of the Release Plan. The Development Work Plan becomes **part of the Project Work Plan** and therefore should be aligned with important project milestones as defined by the Project Manager (PM) and the whole Project Core Team (PCT). The Development Work Plan can be documented using varied formats and media (e.g. MS Office-based documentation, applications such as Atlassian ==JIRA==, IBM Rational Team Concert, etc). | Key Participants | Description | |:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Team Coordinator (TeCo) | Responsible for collecting data of all activities involved in the definition of the Development Work Plan in general, and for the Release Plan, in particular. | | Agile Team Member (ATeM) | Actively supports the definition of the Development Work Plan, playing a critical role in the definition of the Iteration Plans. | | Product Owner (PrOw) | The Product Owner also supports the definition of the Development Work Plan as a whole. Responsible for the Work Items List (WIL) <br> and an important contributor for the definition of the Release and Iteration plans. | | Architecture Owner (ArOw) | Supports the Team Coordinator (TeCo) providing technical advice and identifying technical constraints In the context of each iteration. <br> Helps the Product Owner (PrOw) prioritising the Work Items List (WIL) and organising the release plans. | | [[Project Manager (PM)]] | As accountable, needs to be aware on how the Agile Project Core Team (A-PCT) plans to deliver the solution and how will that be aligned with the overall project milestones. | **Guidelines** The Development Work Plan consists of two parts: - **Work Items List** –The Work Items List includes all the items (e.g. user stories, bugs, enabler stories) that need to be addressed within the IT-domain-specific aspect of the project and proposed work that may affect the information system in this or future projects. All the Work Items need to be ==prioritised== and ==estimated== at some point, since the Work Items List (WIL) is the ==main driver of the project==. - **Schedules** – There are two schedule detail levels: a release level schedule (==Release Plan==) and an iteration level schedule (==Iteration Plan==). In the Release Plan, the focus is primarily on what needs to be done and when. In an Iteration Plan, the focus is on how it will be done by the Agile Project Core Team (A-PCT). ![[7.2.2 Development Work Plan — Inputs and main roles.png]] ![[7.2.2 Development Work Plan.png]] #### [[7.2.2.1 Work Items List]] #### [[7.2.2.2 Release Plan]] #### [[7.2.2.3 Iteration Plan]]