launchpad development|
⇤ ← Revision 1 as of 2011-11-01 05:49:58
Size: 1675
Comment: First shot
|
Size: 1573
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| ''Short description of feature'' | Currently, personal branches are of the form lp:~stevenk/+junk/foo. |
| Line 12: | Line 12: |
| '''On Launchpad:''' ''Link to a blueprint, milestone or (best) a bug tag search across launchpad-project'' ''Consider clarifying the feature by describing what it is not?'' ''Link this from [[LEP]]'' |
'''On Launchpad:''' https://bugs.launchpad.net/launchpad/+bug/147407 |
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
Less Junk for personal branches
Currently, personal branches are of the form lp:~stevenk/+junk/foo.
Contact: StevenK
On Launchpad: https://bugs.launchpad.net/launchpad/+bug/147407
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?
User stories
$STORY_NAME
As a $PERSON
I want $FEATURE
so that $BENEFIT
Have as many as you like. Group user stories together into meaningfully deliverable units. They'll be used as the driving elements of exploratory testing QA.
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.
