launchpad development|
Size: 2700
Comment:
|
Size: 2779
Comment: Adding exploratory testing link
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 60: | Line 60: |
| === Exploratory testing === * https://dev.launchpad.net/QA/ExploratoryTesting/Disclosure/TrustedPickers |
|
| Line 62: | Line 66: |
| * Link to exploratory testing |
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 |
CHECKPOINT |
|
|
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
