Support/Goals/2011Q3/Identity Documentation): Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 9: Line 9:
| [[Identity SUMO Content Creation]]
| [[Identity SUMO Content Creation]]
| {{StatusHealthy|status=Working on initial concept}}
| {{StatusHealthy|status=Working on initial concept}}
| YYYY-MM-DD
| 2011-09-30
| Ibai Garcia
| Ibai Garcia
<section end="status" />
<section end="status" />
Line 31: Line 31:
Team list should make it clear who to ask about what, and who to ping when they're needed.  If you do not need someone in a particular role (ie: Security), that's fine, just delete that line.  Contact info for each person would also be handy.
Team list should make it clear who to ask about what, and who to ping when they're needed.  If you do not need someone in a particular role (ie: Security), that's fine, just delete that line.  Contact info for each person would also be handy.


== Release Requirements ==
== Goals ==
Complete checklist of items that need to be satisfied before we can call this feature "done".
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.


== Next Steps ==
== Project Plan ==
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.  Including the name of who's responsible for each item, and a rough ETA can be useful.
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.  Including the name of who's responsible for each item, and a rough ETA can be useful.
== Open Issues ==
Unanswered questions, things that need to be explored, decisions that still need to be made, etc.  Again, including the name of who's responsible for each item can be useful.
== Related Bugs & Dependencies ==
N/A
== Designs ==
N/A
== Use Cases ==
Everyone loves use cases, so you should provide them if you can (and where it makes sense).  The [[ChannelSwitching/ChannelSwitchingFeature#Use_Cases|Channel Switcher]] Feature Page has some good examples.
== Test Plans ==
Any and all test plans and strategies.  Either inline or linked to.
== Goals ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.


== Non-Goals ==
== Non-Goals ==
Things we are specifically not doing or building as part of this feature.
Things we are specifically not doing or building as part of this feature.


== Other Documentation ==
== Additional Documentation ==
Can include things like:
 
* Competitive landscape
* Research & references
* Whatever else is useful to the project.


== Legend (remove if you like) ==
== Legend (remove if you like) ==
Line 81: Line 60:


__NOTOC__
__NOTOC__
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.


[[Category:Features]]
[[Category:Features]]
[[Category:Firefox]]
[[Category:Firefox]]
[[Category:Platform]]
[[Category:Services]]
[[Category:Services]]
[[Category:Mobile]]
[[Category:Other]]

Revision as of 14:08, 30 June 2011

Feature Status ETA Owner
Identity SUMO Content Creation Working on initial concept 2011-09-30 Ibai Garcia

Summary

A set of articles and templates that explains the processes and potential issues of using Identity/Browser ID. The goal is to have an initial set ready with the Beta launch in Q3.

Team

Who's working on this?

  • Goal Manager: Ibai Garcia
  • Lead Developer:
  • Product Manager: Dan Mills
  • QA:
  • UX:
  • Security:
  • Etc.

Team list should make it clear who to ask about what, and who to ping when they're needed. If you do not need someone in a particular role (ie: Security), that's fine, just delete that line. Contact info for each person would also be handy.

Goals

The high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.

Project Plan

Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished. Including the name of who's responsible for each item, and a rough ETA can be useful.

Non-Goals

Things we are specifically not doing or building as part of this feature.

Additional Documentation

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked.
  At Risk: feature is at risk of missing its targeted release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.