DRAFT: Enforce Important Performance-Related Page Characteristics

(Sorry, this is a placeholder. Hopefully I will fill it in within a few hours.)

Short description of feature

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

What MUST the new behaviour provide?

What MUST it not do?

Unnecessary Desires

What are ideas that might be desirable, but are *not* constraints for this proposal?

Success

How will we know when we are done?

How will we measure how well we have done?

Subfeatures

OPTIONAL

Other LaunchpadEnhancementProposals that form a part of this one.

Implementation Proposal

Description

How will this work?

Workflows

OPTIONAL

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.

Risks

What are the risks associated with this implementation? Consider risks that may make the implementation fail to meet its goals, risks that may make the delivery time slip, security risks, performance risks, and usability/documentation risks.

Experiment 1

It will often be appropriate to construct one or more experiments to address the identified risks before proceeding to the implementation step. Make sure that the effort to construct experiments is significantly less than the effort expected to be expended on the implementation!

Goal

What is the goal of the experiment? What risk or risks do you intend to explore?

Design

How will the experiment work?

Result

How did it turn out?

Thoughts?

Put everything else here.