Welcome to the Sunbird release 4.3.0.0 Delivery plan folder!
It captures The purpose of the pages in this folder is to capture release information in a free-flowing, simple, easy to read manner such that stakeholders outside the delivery team find it engaging and useful.
Every organization contributing towards Sunbird release 4.3.0.0:
Submits submits a delivery plan detailing the scope of items capabilities they commit to deliver for the release
Updates updates the status of the committed items capabilities every week on the release status dashboard
The release folder has sub-folders. Every contributor contributing organization has a separate folder with individual pages for every delivery team of the that organization.
The page associated with the organization folder contains a table indicative of the status dashboard. Add as many rows in the table as required. Each row indicates one solution indicates the status of capabilities committed by every delivery team of the organization. Every team has a separate dashboard table.
Add the required number of rows to any table on the page. You may also delete a table if any team does not commit to the release. Each row in the table indicates one committed capability.
There are 3 Planning statuses - Targeted, Dropped, Confirmed. Write Indicate the current status against each proposed capability.
Indicate the delivery status each week using the following colour codes:
Descoped (The team will not deliver the entire solution will not be deliveredcapability) | |
Partial delivery (Some The team will deliver a part of the solution will be deliveredcapability) | |
At risk | |
On track |
Following the table, add the description for each proposed capability.The pages following the organization’s status dashboard provide details of each committed capability.
Each team in the organization has a page of its own.
The page is fitted with a template that provides a sample structure and content.
The lens to be used while writing the information descriptions is ‘Outside - In’.
The information provided should be succinct , but clear. (Sample text is provided.)
Add descriptions for every committed capability.
You may copy the sample structure as many capabilities times as required.