2953
Comment:
|
2700
|
Deletions are marked like this. | Additions are marked like this. |
Line 29: | Line 29: |
* jml to create a project picker LEP * jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense |
|
Line 44: | Line 42: |
|| [[LEP/PrivateProjectsAndDistributions#projects|Private projects]] || || || || [[LEP/PrivateProjectsAndDistributions#distributions|Private distributions]] || || || || [[LEP/PrivateProjectsAndDistributions#entitlement|Basic entitlement]] || || || |
|
Line 47: | Line 48: |
1. (2 cycles) alpha level, opt-in only private projects 1. Private distributions 1. As a person with rights over a blacklisted name, I want to create a private project or distribution with a blacklisted name without any Launchpad admin intervention or any other privileges, so that I can just get my stuff done and not accidentally destroy everything |
== Notes == |
Line 51: | Line 50: |
== XXX - missing bits == | * At each checkpoint, make sure to go over [[LEP/BetterPrivacy]] and mark off which requirements have been met |
Line 53: | Line 52: |
* Link to user testing sessions * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/ * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/CodySommerville * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/SteveMagoun |
== Resources == === User research === * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/ * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/CodySommerville * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/SteveMagoun === Still needed === |
Line 60: | Line 65: |
* Turn into template | |
Line 65: | Line 69: |
* Change LEPs to have multiple users stories in a section after the intro and before the constraints |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 4
Next checkpoint: 2011-06-15
Scope
Out of scope
- Private teams work out of scope, except where necessary to enable above
- Any complicated bug linking beyond the bare case for cloning
Blockers
Open questions on LEP/BugLinking
Special actions
jml & sinzui to resolve open questions on LEP/BugLinking
Deliverables
Item |
Owner |
Expected date |
Status |
Signed off LEPs |
jml |
|
DONE |
|
2011-06-16 |
INPROGRESS |
|
|
2011-06-16 |
INPROGRESS |
|
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
Feature documentation |
mrevell |
|
|
Blog post |
mrevell |
|
|
Notes
At each checkpoint, make sure to go over LEP/BetterPrivacy and mark off which requirements have been met
Resources
User research
https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/
https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/CodySommerville
https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/SteveMagoun
Still needed
- Link to exploratory testing
- Link to mockups
Somehow fit in two week cycle -- https://wiki.canonical.com/Launchpad/PolicyandProcess/FeatureDevelopment
How are we going to link from deliverables to LEPs?
- User stories in a LEP can be grouped, can be individual. Either way, must be able to be referenced
- A deliverable can correspond to a group of user stories or a single user story
- Product team uses the user stories when evaluating progress on feature