Confirmed users
3,314
edits
m (→Marco) |
(→Chris) |
||
(6 intermediate revisions by one other user not shown) | |||
Line 2: | Line 2: | ||
==Chris== | ==Chris== | ||
* Geolocation: | * Geolocation: | ||
** Define clear roadmap and B2G QA story. | ** {{miss|}} Define clear roadmap and B2G QA story. | ||
** Geofencing WebAPI: work with QC to write API proposal for W3C standardization. | ** {{defer|}} Geofencing WebAPI: work with QC to write API proposal for W3C standardization. | ||
* e10s: Focus on add-on compatibility with organized testing and reaching out to add-on developers. | * {{done|}} e10s: Focus on add-on compatibility with organized testing and reaching out to add-on developers. | ||
* Shumway: define milestones and drive to enable Shumway (in Nightly) by end of Q3. | * {{done|}} Shumway: define milestones and drive to enable Shumway (in Nightly) by end of Q3. | ||
* RR2P: | * RR2P: | ||
** Test drive Trello for Geolocation and report experience: [https://trello.com/b/TCwBhEYd/mozilla-geolocation mozilla-geolocation board] | ** {{done|}} Test drive Trello for Geolocation and report experience: [https://trello.com/b/TCwBhEYd/mozilla-geolocation mozilla-geolocation board] | ||
** Maybe interview engineering managers about their planning/project tools and write a report. | ** {{drop|}} Maybe interview engineering managers about their planning/project tools and write a report. | ||
* Browser Benchmark Automation: | * Browser Benchmark Automation: | ||
** Work with A-Team to build and deploy automation and reporting servers. | ** {{done|}} Work with A-Team to build and deploy automation and reporting servers. | ||
** Identify Gecko teams interested in adding new benchmarks. | ** {{done|}} Identify Gecko teams interested in adding new benchmarks. | ||
==Erin== | ==Erin== | ||
Line 28: | Line 28: | ||
==Marco== | ==Marco== | ||
* Implement and evaluate V1 Desktop iteration process changes | * Implement and evaluate V1 Desktop iteration process changes initiated on Iteration 34.2 (Tuesday August 5): | ||
** Point estimation will be conducted with the whole team | ** {{done|}} Point estimation will be conducted asynchronously with the whole team. | ||
** | ** {{done|}} Establish a point cap where the whole team will select bugs up to the median value of the velocity range at the planning meeting. | ||
** Each planning group will have its own | ** {{done|}} Each planning group will have its own point cap based on their own production capability. | ||
** {{done|}} 'Review+' bug status will now be considered work in progress and count towards the point cap during the planning meeting. | |||
* Aim to achieve the following performance gains based on the above mentioned process changes at the conclusion of Iteration 35.2 (Monday September 29): | |||
** | ** {{done|}} Reduce the average percentage of points selected by 25%. | ||
* Aim to achieve the following performance gains based on the above mentioned process changes at the conclusion of Iteration 35.2 | *** Achieved: average percentage point selection decreased by 28%. | ||
** Reduce the average percentage of points selected by 25%. | ** {{done|}} Increase the average percentage of completed work to 75%. | ||
** | *** Achieved: average percentage complete increased from 56% to 76%. | ||
** Reduce the average percentage of carry over work to 25%. | ** {{done|}} Reduce the average percentage of carry over work to 25%. | ||
*** | *** Achieved: average percentage carry over decreased from 44% to 24%. | ||
==Sheila== | ==Sheila== |