Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| See Also Triage Bugs |
| ### Next Steps Fix a Bug |
| Activity: Schedule Bug Fixing Allotment
Project Manager
Business Analyst
|  |  |  | Plan an Iteration |  |
|  | Participating Roles Responsible: Project Manager Business Analyst
### Overview Scheduling a bug fixing allotment sets the expectations for fixing triaged bugs. Generally, a bug allotment spans the development group but can also be restricted to a single or set of individuals on the team. Bug allotments must be taken from the total development budget. # Entry Criteria Dependencies: The bugs have been triaged. # Sub-Activities
1 | Schedule Bug Allotment | Determine the amount of the development budget required to fix bugs in ideal person days. Leave the allotment as slack in the budget if the Microsoft Excel iteration plan is used. It can optionally be scheduled if the Microsoft Project version of the iteration plan is used.
2 | Consider Dependencies and Other Factors | If scenarios or quality of service requirements are scheduled along with a bug allotment, be sure that key developers with high bug backlogs have enough slack to work on their high priority bugs. Examine the development tasks to be sure of this slack. Reallocate bugs or tasks to ensure that bugs are fixed.
3 | Hold Iteration Kickoff Meeting | Finalize the iteration plan by holding an iteration planning meeting to present the content for the upcoming iteration. This meeting should include all of the members of the team to review the goals of the upcoming iteration. Communicate any priorities within the iteration. Mark a small set of the highest priority bugs as exit criteria. Use this mechanism sparingly.
# Exit Criteria
| The bug allotment is scheduled for the upcoming iteration.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |