|Feature Page Structure||One or two sentence status report.||YYYY-MM-DD||Owner Name|
Succinct summary of what this feature is all about.
Complete checklist of items that need to be satisfied before we can call this feature "done".
Next Steps & Open Issues
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 include 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
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
Identify, prioritize, track and communicate any risks associated with this feature/project.
Everyone loves use cases, so you should provide them if you can (and where it makes sense). The Channel Switcher Feature Page has some good examples.
Any and all mockups, design specs, tech specs, etc. Either inline or linked to.
Any and all test plans and strategies. Either inline or linked to.
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.|
Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.