User Tools

Site Tools


doctor_milestone_c_report

Differences

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

Link to this comparison view

doctor_milestone_c_report [2015/09/28 20:47]
Debra Scott created
doctor_milestone_c_report [2015/09/28 20:48] (current)
Debra Scott
Line 1: Line 1:
  ​1.Project name: Doctor  ​1.Project name: Doctor
  
-  ​2.Project status indicator for milestone C readiness: Green+ 2.Project status indicator for milestone C readiness: Green
   ​   ​
-  ​3.Name of person providing status: Ryota Mibu+ 3.Name of person providing status: Ryota Mibu
   ​   ​
-  ​4.a link to your Jira tasks (filtered on R2): https://​jira.opnfv.org/​issues/?​jql=project%20%3D%20DOCTOR%20AND%20labels%20%3D%20R2+ 4.a link to your Jira tasks (filtered on R2): https://​jira.opnfv.org/​issues/?​jql=project%20%3D%20DOCTOR%20AND%20labels%20%3D%20R2
   ​   ​
-  ​5.a link to your Jira dashboard: https://​jira.opnfv.org/​browse/​DOCTOR+ 5.a link to your Jira dashboard: https://​jira.opnfv.org/​browse/​DOCTOR
   ​   ​
-  ​6.a statement of your progress at linking cross project dependencies in Jira: Cross project tasks are created in both side of projects and linked (DOCTOR-21, 22).+ 6.a statement of your progress at linking cross project dependencies in Jira: Cross project tasks are created in both side of projects and linked (DOCTOR-21, 22).
   ​   ​
-  ​7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile): All tasks, related to OPFNV B release, are tagged with '​R2'​ and set deadlines.+ 7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile): All tasks, related to OPFNV B release, are tagged with '​R2'​ and set deadlines.
   ​   ​
-  ​8.a statement of your readiness (high level planning complete & in Jira) for future sprints: All epics are identified and created in Jira (DOCTOR-32, 34 and 35).+ 8.a statement of your readiness (high level planning complete & in Jira) for future sprints: All epics are identified and created in Jira (DOCTOR-32, 34 and 35).
   ​   ​
-  ​9.a statement about any issues you have: No current issue+ 9.a statement about any issues you have: No current issue
   ​   ​
-  ​10.how & when you will finish getting your tasks & dependencies into Jira if not complete: (We believe that those are complete.)+ 10.how & when you will finish getting your tasks & dependencies into Jira if not complete: (We believe that those are complete.)
   ​   ​
-  ​11.how and when you will get ready to start development for Brahmaputra if not ready now: (If more detailed planning are required in milestone-C,​ we can start the elaboration in task DOCTOR-31.)+ 11.how and when you will get ready to start development for Brahmaputra if not ready now: (If more detailed planning are required in milestone-C,​ we can start the elaboration in task DOCTOR-31.)
   ​   ​
-  ​12.a statement summarizing your project risk analysis & planning status: Low risk and on track+ 12.a statement summarizing your project risk analysis & planning status: Low risk and on track
  
doctor_milestone_c_report.1443473263.txt.gz ยท Last modified: 2015/09/28 20:47 by Debra Scott