copper:planning
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
copper:planning [2015/09/22 16:12] Bryan Sullivan |
copper:planning [2015/09/24 18:57] (current) Bryan Sullivan |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| (draft in progress) | (draft in progress) | ||
| - | 1. Copper | + | ^ Criteria ^ Copper Status ^ |
| - | 2. Green | + | | 1. Project name | Copper | |
| - | 3. Bryan Sullivan | + | | 2. Project status indicator for milestone C readiness: Green/Yellow/Red; GREEN = on track; YELLOW = working minor issues to get back on track; RED = offtrack with major issues | Green | |
| - | 4. https://jira.opnfv.org/browse/COPPER-1?jql=project%20%3D%20COPPER%20AND%20labels%20%3D%20R2 | + | | 3.Name of person providing status | Bryan Sullivan | |
| - | 5. https://jira.opnfv.org/browse/COPPER | + | | 4.a link to your Jira tasks (filtered on R2) | [[https://jira.opnfv.org/browse/COPPER-1?jql=project%20%3D%20COPPER%20AND%20labels%20%3D%20R2| Copper R2 Jira tasks]] | |
| - | 6. a statement of your progress at linking cross project dependencies in Jira | + | | 5.a link to your Jira dashboard | [[https://jira.opnfv.org/browse/COPPER | Copper Jira Dashboard]] | |
| - | 7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile) | + | | 6.a statement of your progress at linking cross project dependencies in Jira | Complete: see [[https://jira.opnfv.org/browse/GENESIS-54?jql=project%20%3D%20GENESIS | Genesis-54]], [[https://etherpad.opnfv.org/p/testing_requests_for_b_release | Functest input]] | |
| - | 8.a statement of your readiness (high level planning complete & in Jira) for future sprints | + | | 7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile) | First development cycle is underway. | |
| - | 9.a statement about any issues you have | + | | 8.a statement of your readiness (high level planning complete & in Jira) for future sprints | We do not plan to organize around sprints. | |
| - | 10.how & when you will finish getting your tasks & dependencies into Jira if not complete | + | | 9.a statement about any issues you have | Complexity of getting lab resources; steep/long learning curve on fundamentals of creating workloads and virtual network environments under OpenStack and OpenDaylight; | |
| - | 11.how and when you will get ready to start development for Brahmaputra if not ready now | + | | 10.how & when you will finish getting your tasks & dependencies into Jira if not complete | Jira is complete. | |
| - | 12.a statement summarizing your project risk analysis & planning status | + | | 11.how and when you will get ready to start development for Brahmaputra if not ready now | Development for Brahmaputra is underway. | |
| + | | 12.a statement summarizing your project risk analysis & planning status | Detailed risk management planning has not been attempted. Overall nature or risks and dependencies is clear, e.g. see issues above. No obvious solutions to these issues other than additional resources. We will do our best. | | ||
| + | |||
| ===== Planned Tasks for B Release ===== | ===== Planned Tasks for B Release ===== | ||
copper/planning.1442938342.txt.gz · Last modified: 2015/09/22 16:12 by Bryan Sullivan
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
