canmove, Confirmed users
1,953
edits
Engagement/MDN Durable Team/Agile glossary: Difference between revisions
Jump to navigation
Jump to search
Engagement/MDN Durable Team/Agile glossary (view source)
Revision as of 23:32, 28 June 2016
, 28 June 2016no edit summary
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
===Acceptance Criteria=== | ===Acceptance Criteria=== | ||
Verifiable work products or achievements that together are necessary and sufficient to implement a User Story. | Verifiable work products or achievements that together are necessary and sufficient to implement a User Story. | ||
===Backlog=== | |||
The set of Epics and User Stories that have been defined, driven by the team's Initiatives. | |||
===Deliverable=== | |||
A tangible work product completed with a quarter (3 months) in support of an Initiative. | |||
===Durable Team=== | ===Durable Team=== | ||
A team using an agile methodology, where the team continues to work together on multiple projects, with minimal changes in members, over a long period of time. It is in contrast to an agile ''project'' team, which exists only for the duration of a single project. See [http://www.agileiowa.org/articles/2013/12/08/finding-your-own-durable-team/ Finding your own durable team] for a detailed explanation. | A team using an agile methodology, where the team continues to work together on multiple projects, with minimal changes in members, over a long period of time. It is in contrast to an agile ''project'' team, which exists only for the duration of a single project. See [http://www.agileiowa.org/articles/2013/12/08/finding-your-own-durable-team/ Finding your own durable team] for a detailed explanation. | ||
===Epic=== | |||
A large-scale User Story that takes more than one Sprint to complete. An epic should be decomposed into User Stories that do fit within a Sprint. | |||
The MDN durable team uses [https://tree.taiga.io/project/viya-mdn-durable-team/issues?page=1 "issues" in Taiga] to represent epics, with tags based on the issue number to associate User Stories with their corresponding epic. | |||
===Initiative=== | |||
A priority area of investment with a specific audience, which affects a KPI and will require a minimum of 6 months to complete. | |||
===KPI, Key Performance Indicator=== | |||
A metric that indicates how well the team is achieving its mission. | |||
===Maker=== | |||
[Role] A team member who executes Tasks, collaborates with the Product Owner on vision and priorities, and decides what work gets done and when. While all team members have specialized skills, in theory, any maker can take on any Task. | |||
===Product Owner=== | ===Product Owner=== | ||
The person ultimately responsible for the product being worked on. This role creates the product vision, approves works, and communicates with stakeholders. | [Role] The person ultimately responsible for the product being worked on. This role creates the product vision, approves works, and communicates with stakeholders. | ||
===Scrum Master=== | ===Scrum Master=== | ||
A project manager who drives projects, manages the team's process, removes blockers, and facilitates meetings. | [Role] A project manager who drives projects, manages the team's process, removes blockers, and facilitates meetings. | ||
===Sprint=== | ===Sprint=== | ||
| Line 17: | Line 37: | ||
===Sprint Board=== | ===Sprint Board=== | ||
A visual representation of the team's work. | A visual representation of the team's work plan and status for a Sprint. The MDN durable team uses [https://tree.taiga.io/project/viya-mdn-durable-team/ Taiga] for its sprint board. | ||
===Stand-up=== | ===Stand-up=== | ||