retropectives:arno
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
retropectives:arno [2015/06/13 21:31] Ray Paik |
retropectives:arno [2015/06/13 21:49] (current) Ray Paik |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| * Within 2 months of project launch, there was a relatively clear idea of the Arno scope. This reduction in scope was a contributing factor in being able to deliver. | * Within 2 months of project launch, there was a relatively clear idea of the Arno scope. This reduction in scope was a contributing factor in being able to deliver. | ||
| * The communication of the Arno scope after the decision was made could have been better | * The communication of the Arno scope after the decision was made could have been better | ||
| - | * There was not an change management process for decision making during Arno and better communication could have reduced friction | + | * Not having a clear idea of the resources available made it very difficult to manage the risk of the scope |
| + | * There was not a change management process for decision making during Arno and better communication could have reduced friction | ||
| + | * On change management, there's a need to be wary of imposing too much top-down control/benediction of project leaders vs allowing leaders to arise organically as we grow as a community. | ||
| + | * A structured approach to using Jira would be helpful in coordinating community efforts | ||
| + | * Schedule | ||
| + | * Additional effort is needed to address risk mitigation when making our plans | ||
| + | * Successful time-based projects manage releases by gating early on feature readiness and gating early | ||
| + | * Establishing clear milestones and being concise on the meaning of those milestones and qualifications will be important | ||
| + | * Individual projects will have their own timeline that may or may not coincide with a time-based release activity. We need to be clear on the correlation between release and content. | ||
| + | * Discussion that it may be acceptable to set our release date based on upstream dependencies rather than trying to stay to a completely time-based release cycle. | ||
| + | * There was a discussion about release cadence, and how features will make it from upstream into a release. | ||
| + | * There is not a shared understanding of what a "release" means, what release artifacts the project will create, or even what it means to be in a release | ||
| + | * Project resources | ||
| + | * Multiple timezones require effective communications in the community. | ||
| + | * Discussion on challenges with the OPNFV hardware in the LF lab. A question was raised if there is a way to automate a lot of activities on the LF hardware. | ||
| ===MeetBot Minutes=== | ===MeetBot Minutes=== | ||
| [[http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-11-13.01.html]] | [[http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-11-13.01.html]] | ||
retropectives/arno.1434231075.txt.gz · Last modified: 2015/06/13 21:31 by Ray Paik
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
