launchpad development|
Size: 1176
Comment:
|
Size: 1831
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| The 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''''' |
|
| Line 5: | Line 11: |
| '''On Launchpad:''' ''hyperlink to a blueprint, normally'' | '''Contact:''' ''The primary contact for this LEP. Normally the drafter or the implementer.'' <<BR>> '''On Launchpad:''' ''Link to a blueprint, milestone or (best) a bug tag search across launchpad-project'' |
| Line 12: | Line 19: |
''Consider breaking down the feature workflows as different [[UserStories|user stories]] and provide mockups for them.'' '''''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.''''' ''Link this from [[LEP]]'' |
|
| Line 23: | Line 37: |
| == Constraints == | == Constraints and Requirements == === Must === |
| Line 27: | Line 43: |
| === Nice to have === === Must not === |
|
| Line 28: | Line 48: |
=== Out of scope === |
|
| Line 33: | Line 55: |
| == Workflows == ''What are the workflows for this feature?'' ''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.''''' |
|
| Line 42: | Line 57: |
| ''How will we know when we are done?'' | === How will we know when we are done? === |
| Line 44: | Line 59: |
| ''How will we measure how well we have done?'' | === How will we measure how well we have done? === |
The 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
$HEADLINE
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?
Consider breaking down the feature workflows as different user stories and provide mockups for them.
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.
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.
Success
How will we know when we are done?
How will we measure how well we have done?
Thoughts?
Put everything else here. Better out than in.
