launchpad development|
Size: 2872
Comment:
|
Size: 2779
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-06-15 | '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-06-29 |
| 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 37: | Line 35: |
| || [[LEP/TrustedPickers#person-pickers|Person pickers]] || || 2011-06-16 || INPROGRESS || || [[LEP/TrustedPickers#project-pickers|Project pickers]] || || 2011-06-16 || INPROGRESS || |
|| [[LEP/TrustedPickers#person-pickers|Person pickers]] || || 2011-06-17 || INPROGRESS || || [[LEP/TrustedPickers#project-pickers|Project pickers]] || || 2011-06-23 || INPROGRESS || |
| Line 54: | Line 52: |
| == XXX - missing bits == | == Resources == |
| Line 56: | Line 54: |
| * 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 * Link to exploratory testing |
=== 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 === Exploratory testing === * https://dev.launchpad.net/QA/ExploratoryTesting/Disclosure/TrustedPickers === Still needed === |
| Line 63: | Line 68: |
| * Turn into template |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 4
Next checkpoint: 2011-06-29
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-17 |
INPROGRESS |
|
|
2011-06-23 |
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
Exploratory testing
Still needed
- 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
