Confirmed users
4,160
edits
Firefox/Metro/WorkWeekII: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 138: | Line 138: | ||
<p> </p> | <p> </p> | ||
* Travel Day | * Travel Day | ||
==Work Week Results== | |||
<p> </p> | |||
'''Defect & Change Backlog''' | |||
* 4 Defect Stories removed from V1 release. | |||
* 31 of 38 Defect/Change Stories prioritized from P1 - P5. | |||
<p> </p> | |||
'''Planning Backlog''' | |||
* 2 Feature Stories moved to Story Backlog ready for upcoming iterations. | |||
<p> </p> | |||
'''Story Backlog''' | |||
* 9 P4 and P5 Feature Stories removed from V1 release. | |||
* 2 P4 and P5 Feature Stories promoted to P3 priority status. | |||
<p> </p> | |||
'''Scope Contingency''' | |||
* Feature Story removals replenished our Scope Contingency from 16 to 77 points. | |||
<p> </p> | |||
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. | |||
# If you know how to fix a bug, dump the information in it to save other people time. | |||
# If you're trying to fix a bug in an iteration and you're having trouble, transfer it back to the Story Backlog and let someone else pick it up on a later iteration. Don't be afraid to re-assign to someone else. Substitute with a bug you feel more confident in. | |||
# Faster reviews, review it right away if you know what it is, take a day at most or warn that it'll take longer. | |||
# 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> | |||
Strategies for Improving Test Coverage: | |||
1. Each team member will particpate in release testing on release planning day of the iteration (day 11) to assist the QA department in achieving a 100% test coverage. | |||
2. Metro will work with QA and Release Management to organize regular 'Metro Test Days' to gather community testers. | |||
3. 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. | |||