Auto-tools/Projects/XTalos

Feature	Status	ETA	Owner
Feature Page Structure	One or two sentence status report.	YYYY-MM-DD	Owner Name
Feature	Status	ETA	Owner
Feature Page Structure	One or two sentence status report.	YYYY-MM-DD	Owner Name

Summary

Very succinct (one or two line) summary of what this feature is all about.

Team

Who's working on this?

• Feature Manager: (required)
• Lead Developer:
• Product Manager:
• 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.

Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done".

Next Steps

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.

Open Issues

Unanswered questions, things that need to be explored, decisions that still need to be made, etc.

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.

== Designs =={| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | style="font-weight: bold; background: #DDD;" | ETA | style="font-weight: bold; background: #DDD;" | Owner |-

| Feature Page Structure | style="background:#9D9;" | One or two sentence status report. | YYYY-MM-DD | Owner Name

|- |}

Summary

Very succinct (one or two line) summary of what this feature is all about.

Team

Who's working on this?

• Feature Manager: (required)
• Lead Developer:
• Product Manager:
• 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.

Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done".

Next Steps

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.

Open Issues

Unanswered questions, things that need to be explored, decisions that still need to be made, etc.

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.

Designs

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

Test Plans

Any and all test plans and strategies. Either inline or linked to.

Goals/Use Cases

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

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

Other Documentation

Can include things like:

• Competitive landscape
• Research & references
• Whatever else is useful to the project.

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.

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

Test Plans

Any and all test plans and strategies. Either inline or linked to.

Goals/Use Cases

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

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

Other Documentation

Can include things like:

• Competitive landscape
• Research & references
• Whatever else is useful to the project.

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.

|}

Summary

Very succinct (one or two line) summary of what this feature is all about.

Team

Who's working on this?

• Feature Manager: (required)
• Lead Developer:
• Product Manager:
• 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.

Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done".

Next Steps

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.

Open Issues

Unanswered questions, things that need to be explored, decisions that still need to be made, etc.

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.

Designs

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

Test Plans

Any and all test plans and strategies. Either inline or linked to.

Goals/Use Cases

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

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

Other Documentation

Can include things like:

• Competitive landscape
• Research & references
• Whatever else is useful to the project.

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.