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