User:Dria/NewFeaturePageStructure2: Difference between revisions

Revision as of 17:25, 21 June 2011

{{{feature name}}}
Stage	{{{stage}}}
Version	{{{version}}}
Health	{{{health}}}
Status note	{{{status}}}

{{#set: |feature name = {{{feature name}}} |stage = {{{stage}}} |version = {{{version}}} |health = {{{health}}} |status = {{{status}}} }}

Product Manager	{{{product manager}}}
Feature Manager	{{{feature manager}}}
Lead Developer	{{{lead developer}}}
Security	{{{security}}}
Privacy	{{{privacy}}}
Localization	{{{localization}}}
Accessibility	{{{accessibility}}}
Quality assurance	{{{qa}}}
User experience	{{{ux}}}

{{#set: | product manager = {{{product manager}}} | feature manager = {{{feature manager}}} | lead developer = {{{lead developer}}} | security = {{{security}}} | privacy = {{{privacy}}} | localization = {{{localization}}} | accessibility = {{{accessibility}}} | qa = {{{qa}}} | ux = {{{ux}}} }}

Open issues/risks

Stage 1: Definition

1. Feature overview

2. Users & use cases

3. Dependencies

4. Requirements

Non-goals

Stage 2: Design

5. Functional specification

6. User experience design

Stage 3: Planning

7. Implementation plan

8. Reviews

Security review

Privacy review

Localization review

Accessibility

Quality Assurance review

Operations review

`

Stage 4: Development

9. Implementation

Stage 5: Release

10. Landing criteria

{{#set:Feature open issues and risks= |Feature overview= |Feature users and use cases= |Feature dependencies= |Feature requirements= |Feature non-goals= |Feature functional spec= |Feature ux design= |Feature implementation plan= |Feature security review= |Feature privacy review= |Feature localization review= |Feature accessibility review= |Feature qa review= |Feature operations review=` |Feature implementation notes= |Feature landing criteria= }}

Feature details

Priority	"unprioritized", "P1", "P2", "P3"
Roadmap	whichever Roadmap this Feature is from, or set by Prod Mgr
Secondary Roadmap	{{{secondary roadmap}}}
Feature List	"Desktop", "Mobile", "Platform", "Services", or "Other"
Engineering Team	Engineering team who will be doing primary development.

{{#set: |priority = "unprioritized", "P1", "P2", "P3" |roadmap = whichever Roadmap this Feature is from, or set by Prod Mgr |secondary roadmap = {{{secondary roadmap}}} |feature list = "Desktop", "Mobile", "Platform", "Services", or "Other" |team = Engineering team who will be doing primary development. }}

Team status notes

Teams are welcome to use these fields however they see fit. Both fields can be used in queries to generate lists on other wiki pages. If you would like help or have questions, please contact Deb.

	status	notes
Products
Engineering
Security
Privacy
Localization
Accessibility
Quality assurance
User experience

{{#set: | product-status = | product-note = | security-status = | security-note = | privacy-status = | privacy-note = | localization-status = | localization-note = | accessibility-status = | accessibility-note = | qa-status = | qa-note = | ux-status = | ux-note = }}

Revision history

date	author	change
YYYY/MM/DD	Your Name Here	Initial feature proposal.

@@ Line 18: / Line 18: @@
 }}
-== Open issues/risks ==
+{{FeaturePageBody
-List
+| Feature open issues and risks =
+| Feature overview =
+| Feature users and use cases =
+| Feature dependencies =
+| Feature requirements =
+| Feature non-goals =
+| Feature functional spec =
+| Feature ux design =
+| Feature implementation plan =
+| Feature security review =
+| Feature privacy review =
+| Feature localization review =
+| Feature accessibility review =
+| Feature qa review =
+| Feature implementation notes =
+| Feature landing criteria =
+}}
-== Stage I: Definition ==
-=== 1. Feature overview ===
-{{RequiredLabel}} Overview description of the feature, motivation for the feature, goals, why it's important.
-=== 2. Users & use cases ===
-{{RequiredLabel}} A clear definition of the target users/audience and the use cases that we want to support, for either end-users or developers.
-=== 3. Dependencies ===
-Defining giver dependencies and taker dependencies so you know who owes to whom what and when.
-=== 4. Requirements ===
-A list of things that the feature should do (must-haves and nice-to-haves) for users and/or developers.  This should '''not''' include implementation decisions or options, but should include performance/latency/SLA/responsiveness requirements.
-==== Non-goals ====
-Optional - things we're specifically not trying to do with this particular iteration of a feature.
-== Stage II: Design ==
-=== 5. Functional specification ===
-What the feature will do to satisfy the requirements, in written form.
-=== 6. User experience design ===
-Designs, interactions, etc., mainly in visual form, if relevant.
-== Stage III: Planning ==
-=== 7. Implementation plan ===
-Summary of the high-level approach to be taken
-=== 8. Security ===
-Are there security risks; has the design been reviewed; what needs to be changed before we proceed?
-=== 9. Privacy ===
-Are there privacy risks; has the design been reviewed; what needs to be changed before we proceed?
-== Stage IV: Development ==
-=== 10. Implementation ===
-Links to bugs -- we '''don't''' try to track the detailed progress here, that should happen in bugzilla.
-== Stage V: Release ==
-=== 11. Landing criteria ===
-Final checklist for everything the feature team feels should happen before a feature can land -- could be a scalability model, security code review, etc.  Will eventually develop a standard table for this.
 == Feature details ==