User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

promise_milestone_c_report [2015/09/28 22:20] (current)
Debra Scott created
Line 1: Line 1:
 +1. Project name
 +2. Project status indicator for milestone C readiness:
 +3.Name of person providing status
 +Peter Lee <​>​
 +4.a link to your Jira tasks (filtered on R2)
 +5.a link to your Jira dashboard
 +6.a statement of your progress at linking cross project dependencies in Jira
 +Completed providing cross project linkage with GENESIS-55 and Functest
 +7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile)
 +Epics, Stories, and Tasks have been identified and planned for Sprint-1
 +8.a statement of your readiness (high level planning complete & in Jira) for future sprints
 +High-level planning for future sprints has been completed. ​ Promise project will have 8 primary EPICs and 4 Sprints leading up to the B-release. ​ Each Sprint will be 4 week in duration (one sprint every month). ​  There will be additional planning prior to each Sprint iteration in order to identify any additional Stories/​Tasks before commencement.
 +9.a statement about any issues you have
 +There are no major issues at this time, other than reserving time and resources for the project (no pun intended…)
 + & when you will finish getting your tasks & dependencies into Jira if not complete
 +The main Stories/​Tasks for Sprint-1 are complete. ​ We will likely define additional Sub-Tasks as necessary as assignments are delegated next week.
 + and when you will get ready to start development for Brahmaputra if not ready now
 +Development for B-release has already begun (outside Jira) but we will be commencing the Jira based Sprint-1 on October 1st.
 +12.a statement summarizing your project risk analysis & planning status
 +Risk level is low.  There are no blocker dependencies from other projects/​components and current planning indicates B-release readiness along the established timelines. ​ Primary risk is around integration with a community NFVI lab to ensure consistent deployment and functionality verification.
promise_milestone_c_report.txt · Last modified: 2015/09/28 22:20 by Debra Scott