canmove, Confirmed users
1,953
edits
Engagement/MDN Durable Team/Processes: Difference between revisions
Jump to navigation
Jump to search
Engagement/MDN Durable Team/Processes (view source)
Revision as of 19:22, 25 July 2018
, 25 July 2018→User Story Life Cycle
(→Planning Sprints: Added info about Sprint Goals) |
|||
| Line 97: | Line 97: | ||
: All tasks have been completed; it is ready for review by subject-matter experts (for content stories), or code review by a peer (for development stories). | : All tasks have been completed; it is ready for review by subject-matter experts (for content stories), or code review by a peer (for development stories). | ||
; Done | ; Done | ||
: The work and reviews have been completed. It is ready for sign-off by the Product Owner. | : The work and reviews have been completed. It is ready for sign-off by the Product Owner or relevant team lead. | ||
; Closed | ; Closed | ||
: The Product Owner has signed off, based on the Acceptance Criteria and [[Engagement/MDN_Durable_Team/Agile_glossary#Definition_of_Done|Definition of Done]], and has closed the issue. | : The Product Owner (or team lead) has signed off, based on the Acceptance Criteria and [[Engagement/MDN_Durable_Team/Agile_glossary#Definition_of_Done|Definition of Done]], and has closed the issue. | ||
; Icebox | ; Icebox | ||
: The issue is valid, but is not going to be worked on by the core staff team. It might be picked up by a volunteer. Or, the issue is deferred, but the future sprint it will go in is not defined. | : The issue is valid, but is not going to be worked on by the core staff team. It might be picked up by a volunteer. Or, the issue is deferred, but the future sprint it will go in is not defined. | ||