Wiki » History » Version 42
Thomas Ganley, 03/30/2023 12:26 AM
1 | 20 | Thomas Ganley | h1. Wiki |
---|---|---|---|
2 | 21 | Thomas Ganley | |
3 | 39 | Thomas Ganley | This mission will be managed in a scrum format. Learn more about what that means and how we'll use redmine in this wiki! |
4 | 38 | Thomas Ganley | |
5 | 37 | Thomas Ganley | *Quick Definitions:* |
6 | 1 | Redmine Admin | |_.Term|_.Definition| |
7 | 34 | Thomas Ganley | | Sprint | A 1-month period during which the team establishes priorities and organizes work around these priorities. | |
8 | 35 | Thomas Ganley | | User Story | A unit of work, anywhere from 1-40 hours in duration. Must be completable within a single sprint. | |
9 | | Feature | A subcategory of work which contains many user stories. Used as "parent" tasks, but not assigned to sprints. | |
||
10 | 36 | Thomas Ganley | | Backlog | The list of user stories and features that the team has to complete in the project. (The "Issues" tab.)| |
11 | 35 | Thomas Ganley | | Scrum Master | An individual responsible for the administration of a sprint. Leads stand-ups, sprint planning, and retrospectives. | |
12 | | Product Owner | The individual(s) ultimately responsible for delivery of the product. | |
||
13 | 33 | Thomas Ganley | |
14 | 40 | Thomas Ganley | h3. Sprint Planning Quick Reference |
15 | |||
16 | # Update sprint velocity, dates and scrum master, as a group. |
||
17 | # Split off into smaller planning groups. |
||
18 | # Move prioritized user stories into sprint and assign team members. |
||
19 | # Define "who, what, why" for user stories. Generally this is done by the team member assigned to the task. |
||
20 | # Add estimated time, start and end date |
||
21 | # Reconvene and compare total sprint velocity to total estimated time. |
||
22 | |||
23 | 41 | Thomas Ganley | h3. Sprint Review Quick Reference |
24 | |||
25 | # Go around the table and share update on user stories from this sprint. What were the key accomplishments, challenges, and how can the team help? |
||
26 | # If desired, teams can share a demo of something they worked on. |
||
27 | # Update status of User Stories. |
||
28 | # Record estimated time and actual time in sprint description, for future estimation. |
||
29 | # Unfinished user stories require justification and should be moved back to the backlog. |
||
30 | # Completed a Sprint Retrospective |
||
31 | 1 | Redmine Admin | |
32 | 42 | Thomas Ganley | h3. Sprint Retrospective Quick Reference |
33 | |||
34 | # Complete a retrospective activity. |
||
35 | # Reconvene and have a discussion about activity results moderated by the scrum master. |
||
36 | # Create one or two action items based on the discussion. |
||
37 | # Share these action items with the rest of the team in #general. |
||
38 | |||
39 | 28 | Thomas Ganley | *Northern SPIRIT Redmine 101* |
40 | 21 | Thomas Ganley | [[Backlog_Operations]] |
41 | [[Sprint_Operations]] |
||
42 | 22 | Thomas Ganley | |
43 | 28 | Thomas Ganley | *Agile Scrum 101* |
44 | 25 | Thomas Ganley | [[Happiness_Metric]] |
45 | [[The_Agile_Manifesto]] |
||
46 | 30 | Thomas Ganley | [[Backlog_Grooming]] |
47 | 31 | Thomas Ganley | [[Sprint_Planning]] |
48 | [[Daily_Standup]] |
||
49 | [[Sprint_Review]] |
||
50 | [[Retrospective]] |
||
51 | 27 | Thomas Ganley | |
52 | 25 | Thomas Ganley | |
53 | 24 | Thomas Ganley | Looking for help with using redmine? Check out the "Redmine Wiki":https://www.redmine.org/projects/redmine/wiki |