User Tools

Site Tools


Overall: Genesis has successfully started its work: The Genesis team identified a set of core requirements and documented them in Jira. OPNFV projects continue to submit their requirements as Jira tickets to Genesis and within the tickets articulate dependencies to their own project work. The Genesis team started the discussion and consolidation of the different requirements and already started to enter accepted requirements into the genesisreq repo

1. Project name Genesis

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 Frank Brockners

4.a link to your Jira tasks (filtered on R2)

5.a link to your Jira dashboard (Kanban: ):

6.a statement of your progress at linking cross project dependencies in Jira Ongoing: Projects continue to submit stories to Genesis articulating their requirements (expectation is that this might even continue post milestone “C”).

7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile) Ready: Work on requirements consolidation and documentation has started.

The Genesis team has gathered a long list of requirements and has also started to discuss these requirement. Once a general understanding on a requirement is achieved, requirements are taken to vote. Requirements which pass the vote are document in the git repo. Some requirements are already present in the genesisreq git repo. 8.a statement of your readiness (high level planning complete & in Jira) for future sprints Genesis expects that all projects have their requirements for Genesis articulated by milestone “C” the latest. Genesis expects that the discussion and finalization of requirements will take another 2 weeks after milestone “C” completion.

9.a statement about any issues you have · Genesis is part of a dependency chain: OPNFV-projects with installer requirements → Genesis → Installer projects. With milestone “C” planning not complete by many projects, Genesis continues to see new requirements entered, even though Sept/21 was communicated as deadline. Genesis expects that all projects have their requirements for Genesis articulated by milestone “C” the latest, so that Genesis “can close the gate”.

· Several Genesis team members are also active with Arno SR1, resulting in less time available for Genesis work. & when you will finish getting your tasks & dependencies into Jira if not complete Per the above: Genesis would like to have all projects report their requirements for Genesis by Milestone C (Sept/29). and when you will get ready to start development for Brahmaputra if not ready now n/a

12.a statement summarizing your project risk analysis & planning status · Genesis deals with moving targets: OPNFV projects might find critical new installer requirements, as they start their work and evolve their planning.

· Requirements brought to Genesis are not always concise and actionable (resulting in additional discussion needs).

· Not a risk for Genesis, but projects depending on Genesis: Requirements brought to Genesis are not always consistent (they might even contradict each other) and/or could fail to find acceptance by the Genesis team.

genesis_milestone_c_report.txt · Last modified: 2015/09/28 21:13 by Debra Scott