Firefox OS/Comms/Dialer/Restructure/Proposal: Difference between revisions

Jump to navigation Jump to search
m
Line 110: Line 110:
* ✔ Clean up general docs on dialer.
* ✔ Clean up general docs on dialer.
** See https://wiki.mozilla.org/FirefoxOS/Comms/Dialer
** See https://wiki.mozilla.org/FirefoxOS/Comms/Dialer
*? Start estimating during sprint planning.
* Catalog long-term projects that we can work on, encourage brainstorming and feedback.
*? Catalog long-term projects that we can work on, encourage brainstorming and feedback.
** Since we're still in damage-control mode, I don't believe that it's a good idea to put serious thought into implementation of these yet. We have to get ourselves under control, and then start on these when we can.
** Since we're still in damage-control mode, I don't believe that it's a good idea to put serious thought into implementation of these yet. We have to get ourselves under control, and then start on these when we can.
*? Kill the comms meeting.
* Kill the comms meeting.
** This isn't really in our scope but it's partly our fault that it still happens.
** This isn't really in our scope but it's partly our fault that it still happens.
** This isn't done but is effectively out of our hands.
*? Get the UX and VD people on Vidyo/Skype and IRC.
*? Get the UX and VD people on Vidyo/Skype and IRC.
** I've contacted Vicky and she's looking into how to get on IRC with the Telefonica firewall in place (she's going to ask Arnau).
** I've contacted Vicky and she's looking into how to get on IRC with the Telefonica firewall in place (she's going to ask Arnau).


====Phase 2 (sprint v2.0-S6 to sprint v2.1-S1)====
====Phase 2 (sprint v2.0-S6 to sprint v2.1-S1)====
* ✔ Switch to the people rotation system that the contacts team uses. (see "Differences Between Teams" / "Contacts" / "People")
* ✔ Begin setting aside time for long-term projects.
*? Gather feedback from the changes previously implemented, iterate where necessary.
*? Begin cross-collaboration and sharing of ideas with other teams. Ask them for feedback and help where necessary.
*? Begin cross-collaboration and sharing of ideas with other teams. Ask them for feedback and help where necessary.
* - Decide on which long-term projects we will be prioritizing.
*? Decide on which long-term projects we will be prioritizing.
* - Begin actual planning of long-term projects, discussing architecture, designs, etc.
*? Begin actual planning of long-term projects, discussing architecture, designs, etc.
** We will be careful to include every team member in these discussions.
** We will be careful to include every team member in these discussions.
* - Switch to the people rotation system that the contacts team uses. (see "Differences Between Teams" / "Contacts" / "People")
* - Begin setting aside time for long-term projects.
* - Establish better relations with UX and VD, consider setting up progress-based meetings for when we need to discuss many things with them.
* - Establish better relations with UX and VD, consider setting up progress-based meetings for when we need to discuss many things with them.
* - Gather feedback from the changes previously implemented, iterate where necessary.
* - Continue to improve technical documentation.
* - Continue to improve technical documentation.
* - Start estimating during sprint planning.
** We decided to delay this until next sprint due to lack of features to estimate.


====Phase 3 (sprint v2.1-S1 onward)====
====Phase 3 (sprint v2.1-S1 onward)====
Confirmed users
525

edits

Navigation menu