Pre- & Post-demonstration Timeline

GREEN: Product Demonstration

BLUE: Items that are triggered by a RELEASE demonstration

YELLOW: Items that are triggered by a SPRINT demonstration

WHITE: Items that are triggered by both a Sprint AND a Release demonstration

Time relative to Demo Date	Upcoming Demo type	Time	Activity	Who
T minus 1 week* Only in the last sprint of a release, ie. if a new Release is about to start	Release	anytime	Release pre-planning: Yared Ayalew and Aaron Holmes and Abdulkerim Essa to map out options for upcoming release Determine domain experts Ratify plan with FMIP Task-force & eek release of desired domain experts Schedule meeting with domain experts for Demonstration Day plus 1 (in the morning if possible)	Yared Ayalew Aaron Holmes
T minus 3 days	All	afternoon (2pm)	PO & PM to preview demonstration. Additional preview days at discretion of Yared Ayalew	Abdulkerim Essa Yared Ayalew Aaron Holmes
T minus 2-3 days	Release	anytime	Meet with Case-Team leaders who have CATS functionality in Pilot- or Field-test: Make sure they and their staff are using CATS Document what problems they are experiencing (CATS-related, connectivity, power, time, etc.) Remind them that they should provide an update at the upcoming demonstration	Abdulkerim Essa Yared Ayalew Aaron Holmes
T minus 2 days	Release	anytime	Inform key domain experts to attend next sprint planning session	Abdulkerim Essa Yared Ayalew
T minus 1 day	All	anytime	Reminder email sent to DRMFSS participants	Aaron Holmes
T- minus 1 day	All	anytime	Ensure items in the Pre-Demonstration Checklist are complete	Yared Ayalew Aaron Holmes
T minus 12 hours	All	afternoon	Final commit to code-branch to be demonstrated	Yared Ayalew
T minus 1 hour	All	morning	Development team on-site & start set-up	Yared Ayalew
	All	morning (10:00 AM-12:30 PM)	Product Demonstration as per Demonstration Agenda & Checklist Demonstration Discussion as per Demonstration discussion ground rules	Aaron Holmes Yared Ayalew Development Team
T plus 2 hours	All	afternoon (2pm)	Developers' retrospective	Yared Ayalew Aaron Holmes
T plus 4 hours	Sprint	afternoon (3.30pm)	Sprint planning (not Release planning)	Abdulkerim Essa Yared Ayalew Aaron Holmes
T plus 1 day	Release	morning (9:30am - 12:30pm)	Release planning (only when starting a new Release)	Abdulkerim Essa Yared Ayalew Aaron Holmes Development Team Domain experts
T plus 1 day	All	morning	Initiate new sprint/release Demo feedback compiled into Demonstrtion Feedback wiki Release planning wiki up-to-date Sprint planning wiki up-to-date Run the CATS: Sprint Issues with no assigned version filter & ensure all issues in the sprint are allocated to the current release Run the CATS: Sprint Issues with no assigned CATS Role filter & ensure all issues, where appropriate, have been assigned a CATS role	Yared Ayalew
T plus 1 day	All	afternoon	Checkpoint Report preparation	Yared Ayalew
T plus 2 days	All	afternoon (2pm)	Checkpoint Report: Review Developers' retrospective Project Management Retrospective Product Demonstration Retrospective Review Demonstrtion Feedback Product Development Review	Yared Ayalew Aaron Holmes