canmove, Confirmed users
1,104
edits
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
It’s a single support entry point for users and it integrates support offered on hardware, software or service issues. We aim to create and scale a community of helpers by starting with Mozilla paid staff, Mozilla and partner's community of helpers, carriers paid support staff, or any FxOS user who might be interested to offer help. We envision partnerships with carriers that will enable them to lower their cost of support by providing credits & incentives to users who help other users. This will also allow us to create a large-scale peer-to-peer service that builds on Mozilla's community-driven support model | It’s a single support entry point for users and it integrates support offered on hardware, software or service issues. We aim to create and scale a community of helpers by starting with Mozilla paid staff, Mozilla and partner's community of helpers, carriers paid support staff, or any FxOS user who might be interested to offer help. We envision partnerships with carriers that will enable them to lower their cost of support by providing credits & incentives to users who help other users. This will also allow us to create a large-scale peer-to-peer service that builds on Mozilla's community-driven support model | ||
== Executive Summary for Last Week == | |||
We currently have 41 open release blockers, including 16 visual design implementation bugs. They all have to be fixed within the next 4 weeks. | |||
You can see all release blockers here: http://mzl.la/1vs8Glx | |||
The biggest risk for phase 1 at the moment: there is no margin of error, if release blockers and visual design bugs are to be implemented fully. | |||
== Important Meetings/Discussions Last Week == | |||
* Last weeks meetup brought together the BuddyUp team, including community contributors for QA. All finally agreed on user stories of phase 1 were delivered on the second day of the meetup, additionally developers fixed 16 release blockers during the week. We got the final revision of UX from Jacqueline based on deliverables for Q1. Joni delivered another round of the content and Helen provided the UI specs based on that. QA went through almost all of the user stories and the bugs they filed gave us a realistic view of the functional readiness of BuddyUP. | |||
* Also last week, Anthony filed the bugs and estimated the visual design implementation. With that final piece we now know what our status regarding release readiness is. | |||
* Sprint 2015.4 started on Tuesday: https://sumo-ernest.herokuapp.com/project/buddyup/bu-2015-4 | |||
* Daily standups with devs at 4pm CET | |||
* Daily triage with QA and Hermina 4.15pm CET | |||
== Important Decisions Last Week == | |||
* Rehan will stay with the project until the end of March | |||
* Sprint 2015.4 contains almost all release blockers | |||
* Sprint 2015.5 (last sprint) will be used for visual design implementation | |||
* QA for remaining bugs will include Hermina. Developers will mark Hermina and QA as needsinfo on every fixed bug. | |||
* QA will run smoke tests once a week | |||
== Coming Up This Week == | |||
* QA is going to finish work on the remaining user stories | |||
== Deliverables This Week == | |||
* QA for remaining user stories | |||
* dev work on release blocker list | |||
* Last of the visual design bugs to be filed. | |||
==Project Information & Documentation== | ==Project Information & Documentation== | ||