tl;dr
- Aha is a good tool to show connections between user stories (Features <https://mozilla.aha.io/products/FXA/feature_cards>) and their breakdown into Requirements, each linked to Milestones <https://github.com/mozilla/fxa/milestones> and individual Github Issues, respectively. The user stories are all linked in Aha to the main elements of the FxA Roadmap (Initiatives <https://mozilla.aha.io/products/FXA/initiatives>), which help us fufill overall FxA Goals <https://mozilla.aha.io/products/FXA/strategic_imperatives> that the team has set up. - There are four high level user stories proposed for the rest of 43. There's breakdown we need to do on some of them. Let us know what you think. - If you can by next week's meeting please also have a look at the backlog (the Next column on the waffle board) and delete/insert as needed; hopefully new things showing up there should be quality/maintenance stuff. In evolving the process for tracking work getting done in the FxA group, there's been a lot of interest in how the product requirements get planned and where they live; instead of cluttering up the issue system with lots of features, Chris, Ryan Kelly, and I want to make it easy to see where the new features are coming from and how they relate to what engineers are doing day to day. We've got a tool (Aha) that is pretty well suited for this purpose, and I am hoping you give it a try to see how to relate all the pieces of the product together, and actively use it to contribute requirements. I plan to get all engineers licenses to this, after I find out how you want to use it. A full seat license is expensive. Let's start with overall FxA Goals <https://mozilla.aha.io/products/FXA/strategic_imperatives>. These are the Big Things we want for the identity system, and encompass outcomes and measures of success. These are not Mozilla's corporate goals, but they relate to them. Do they make sense? For comparison, the overall Mozilla goals you've seen on a gazillion slides from Chris Beard are listed here <https://mozilla.aha.io/products/FFOX/strategic_imperatives>. The Goals all map to the overall FxA roadmap for 2015 and beyond, broken out into several Initiatives <https://mozilla.aha.io/products/FXA/initiatives>. These are the main things we are trying to get done for the different users of Firefox Accounts, across multiple iterations and releases of Firefox (which we track even if we're usually not landing code the way other client groups are). I think a lot of the team already contributed to this list, and we can evolve it more over time. The elements of the FxA roadmap called Initiatives are ultimately what gives rise to the ideas of what problems to solve for our users, the high level user stories. In Aha these are called Features <https://mozilla.aha.io/products/FXA/feature_cards>. Where do they come from? From you guys, from partners, and others that support engineering on the FxA team such as Edwin and me. Before every two-week sprint, a bunch of us meet to discuss what should be in the next iteration. Here new stories from me or any of us can get proposed. Right now we're finishing items listed under release 42, user-facing features with stories including metrics work. Have a look at the Features listed under the period of time that corresponds to Firefox 43. For the next couple of sprints, I'm proposing we focus on three things: making email communications great and starting to make Device Controller features, although we probably won't finish it in this next sprint. We also want to align with work going on in the Fennec team to use Web flows to support FxA integration with relying services like Hello. Are these the right things to work on next? Don't know, that is what the kickoff meeting of the new sprint is for, so we can all decide. These Features are pretty broad; in some cases they have already been broken down into more detailed requirements listed as part of the Feature, but in many cases they have not. Please weigh in in the Comments section with questions and ideas for how to improve these stories and break them down into bite-sized pieces; these are the Requirements, including the user experiences that need to be created to make this user story have a happy ending. Ultimately each of the Requirements broken down from the Features will end up as a Github Issue linked in Aha. The way we have designed it each of the Features in Aha has a corresponding Milestone in Github, with the due date of the release the Feature/Milestone is attached to. We are going to name the Milestones to make it simple to see the Feature, but we will link them together also. In Github (or on the waffle board) you can always use the view of the Milestone to see the Feature it links to, but I'm hoping you look at the Requirements and Features directly in Aha to see how they fit together and link to Initiatives and Goals in the FxA Roadmap. Of course, these new Features are not the whole picture of what is important in the next sprint and beyond. There are quality initiatives, technical debt to pay off, and operational and administrative work the user will never see; I am not always up to speed on these count on you all to tell me what should be prioritized for the sprint alongside new feature work. There's some more stuff that needs to happen to make this sprint planning process more complete; we clear criteria to show that Features are Done (Milestones are Reached). We need to formalize when we finish Features that people can show the great user-facing things they have made, and identify specific questions that Ryan Feeley can try to answer with user testing. Ideally this should happen at the end of every sprint, but we've got to work up to it. It might be best to show you the tool working real time in fxa eng meeting next week after you poke around. Chris suggests that something async like a screenscast might also be helpful for the farflung team. Let me know what you want, or just ping me with questions. Bill
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
