Confirmed users
964
edits
Program Management/Sprint Guide: Difference between revisions
→Events and Actions: asd
(→Events and Actions: update) |
(→Events and Actions: asd) |
||
| Line 51: | Line 51: | ||
|} | |} | ||
Glossary: | |||
{| class="wikitable" | |||
|- | |||
! Term !! Description | |||
|- | |||
| Rank || Relative backlog priority. Specifically, P1's are rank 15 by default, then lower or increase based upon relative priority. There will be duplicates which is fine. | |||
|- | |||
| Backlog || The set of prioritized tasks for the sprint team to complete. The product owner sets priority and team takes items in order from priority as it makes sense. We want to encourage cross training here, but want to be efficient if someone is in a specific area of code already. | |||
|- | |||
| Priority || Higher level large grouping of importance. Based upon the impact of the task or need for inclusion in the targeted release. | |||
|- | |||
| Theme || Large groupings of tasks in common supporting a feature. Often used to map to a user story. | |||
|- | |||
| iteration || used to denote a team member taking an item to work on for a sprint (e.g. 41.1, 42.2) | |||
|} | |||
[[Program_Management/ProjectPlanTemplate/Firefoxdesktop | Detailed info on the approach]] | [[Program_Management/ProjectPlanTemplate/Firefoxdesktop | Detailed info on the approach]] | ||