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.'' <<BR>>
'''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]]''

== 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 ==

<<Anchor(story-name>)>>

=== $STORY_NAME ===

'''As a ''' $PERSON<<BR>>
'''I want ''' $FEATURE<<BR>>
'''so that ''' $BENEFIT<<BR>>

''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 LaunchpadEnhancementProposal``s 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.''