1. Project name ONOSFW
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
3.Name of person providing status Ashlee Young (firstname.lastname@example.org)
4.a link to your Jira tasks (filtered on R2) https://jira.opnfv.org/browse/ONOSFW-116?jql=project%20%3D%20ONOSFW
5.a link to your Jira dashboard https://jira.opnfv.org/browse/ONOSFW/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
6.a statement of your progress at linking cross project dependencies in Jira We are waiting to hear back from test leads on their requirements, and we’re waiting to hear back if we’re accepted into Genesis. But other than that, we have no other dependencies.
7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile) We have our stories done. Just organizing our boards. We have a high-level overview of our sprints on our forum. While we’re still dealing with Jira, we are operating to this diagram: http://forum.onosfw.com/t/brahmaputra-sprint-schedule/69
8.a statement of your readiness (high level planning complete & in Jira) for future sprints We have our tasks entered, that we know of. We are trying to finalize our feature development by end of October so that we can transition to tests and integration. This is per our schedule in the above link. The tasks are organized for our features, but we cannot start the sprint in Jira. We are getting an error message that we need admin rights. Regardless, our sprint0 started on 9/21. We have a breakdown of 8 sprints and 6 categories. This is posted on our forum: http://forum.onosfw.com/t/brahmaputra-sprint-schedule/69
9.a statement about any issues you have Jira permissions. Still have committers without gerrit access. Right now, we’re funneling commits through those with access. None of this is slowing down development.
10.how & when you will finish getting your tasks & dependencies into Jira if not complete Tasks and dependencies are done. We’re dealing with organizing our tasks into sprints. Getting admin permission errors in Jira.
11.how and when you will get ready to start development for Brahmaputra if not ready now Officially, our sprint0 started on 9/21, though we started some of the features much earlier.
12.a statement summarizing your project risk analysis & planning status Risk is low. Our development is on track. Some modules have begun testing, optimization and bug fixing. We expect to be code complete by mid-November.