launchpad developmentThe purpose of this template is to help us get ReadyToCode on features or tricky bugs as quickly as possible. See also LaunchpadEnhancementProposalProcess.
The bits in italics are the bits that you should fill in. Delete the italic bits.
Talk to the product strategist soon after cutting a first draft of this document
Tracking QA
Short description of feature
Contact: The primary contact for this LEP. Normally the drafter or the implementer.
On Launchpad: Link to a blueprint, milestone or (best) a bug tag search across launchpad-project
As a $PERSON
I want $FEATURE
so that $BENEFIT
Consider clarifying the feature by describing what it is not?
Link this from LEP
Rationale
Why are we doing this now?
What value does this give our users? Which users?
Stakeholders
Who really cares about this feature? When did you last talk to them?
Constraints and Requirements
Must
What MUST the new behaviour provide?
Nice to have
Must not
What MUST it not do?
Out of scope
Subfeatures
Other LaunchpadEnhancementProposals that form a part of this one.
Workflows
What are the workflows for this feature? Even a short list can help you and others understand the scope of the change. Provide mockups for each workflow.
You do not have to get the mockups and workflows right at this point. In fact, it is better to have several alternatives, delaying deciding on the final set of workflows until the last responsible moment.
Success
How will we know when we are done?
How will we measure how well we have done?
Thoughts?
- Don't want to burden other projects in Launchpad in with overhead of QA widgets
Options
- More statuses
- Separate QA fields on bugs
- Separate entity / process for doing QA
