Confirmed users
4,174
edits
Firefox/Metro/WorkWeekII: Difference between revisions
Jump to navigation
Jump to search
→Work Week Results
No edit summary |
|||
| Line 155: | Line 155: | ||
* Feature Story removals replenished our Scope Contingency from 16 to 77 points. | * Feature Story removals replenished our Scope Contingency from 16 to 77 points. | ||
<p> </p> | <p> </p> | ||
Strategies for Improving Team Velocity: | '''Strategies for Improving Team Velocity:''' | ||
# Only work on what you can reproduce, if someone else can reproduce it then transfer the work to them as quickly as possible. | # Only work on what you can reproduce, if someone else can reproduce it then transfer the work to them as quickly as possible. | ||
# If you know how to fix a bug, dump the information in it to save other people time. | # If you know how to fix a bug, dump the information in it to save other people time. | ||
| Line 162: | Line 162: | ||
# Developers will use their discretion to determine if a defect found during iteration testing is a P4 or P5 priority status. Those that are will not be considered to block the feature story and it can be resolved. | # Developers will use their discretion to determine if a defect found during iteration testing is a P4 or P5 priority status. Those that are will not be considered to block the feature story and it can be resolved. | ||
<p> </p> | <p> </p> | ||
Strategies for Improving Test Coverage: | '''Strategies for Improving Test Coverage:''' | ||
# Each team member will participate in release testing on release planning day of the iteration (day 11) to assist the QA department in achieving a 100% test coverage. | |||
# Metro will work with QA and Release Management to organize regular 'Metro Test Days' to gather community testers. | |||
# Faster reviews, review it right away if you know what it is, take a day at most or warn that it'll take longer. This will help us identify and resolve defects quicker before the end of an iteration. | |||