Wiki » History » Revision 12
Revision 11 (John Mabanta, 03/08/2023 12:52 AM) → Revision 12/14 (Priya Manavalan, 04/03/2023 06:16 PM)
h1. Wiki
This mission will be managed in a scrum format. Learn more about what that means and how we'll use redmine in this wiki!
*Quick Definitions:*
|_.Term|_.Definition|
| Sprint | A 2-week period during which the team establishes priorities and organizes work around these priorities. |
| User Story | A unit of work, anywhere from 1-40 hours in duration. Must be completable within a single sprint. |
| Feature | A subcategory of work which contains many user stories. Used as "parent" tasks, but not assigned to sprints. |
| Backlog | The list of user stories and features that the team has to complete in the project. (The "Issues" tab.)|
| Scrum Master | An individual responsible for the administration of a sprint. Leads stand-ups, sprint planning, and retrospectives. |
| Product Owner | The individual(s) ultimately responsible for delivery of the product. |
h3. Sprint Planning Quick Reference
# Update sprint velocity, dates and scrum master, as a group.
# Split off into smaller planning groups.
# Move prioritized user stories into sprint and assign team members.
# Define "who, what, why" for user stories. Generally this is done by the team member assigned to the task.
# Add estimated time, start and end date.
# Reconvene and compare total sprint velocity to total estimated time.
h3. Sprint Review Quick Reference
# Have all team members log time spend on their user stories.
# 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?
# If desired, teams can share a demo of something they worked on.
# Update status of User Stories.
# Record estimated time and actual time in sprint description, for future estimation.
# Unfinished user stories require justification and should be moved back to the backlog.
# Complete a Sprint Retrospective.
h3. Sprint Retrospective Quick Reference
# Complete a retrospective activity.
# Reconvene and have a discussion about activity results moderated by the scrum master.
# Create one or two action items based on the discussion.
# Share these action items with the rest of the team in #general.
h3. Backlog Grooming Quick Reference
# Add tasks to the backlog.
# Prioritize tasks in the backlog by changing the priority.
# Ensure all tasks are parented.
*CUBICS Redmine 101*
[[Northern SPIRIT:Backlog_Operations]]
[[Northern SPIRIT:Sprint_Operations]]
*Agile Scrum 101*
[[Northern SPIRIT:Happiness_Metric]]
[[Northern SPIRIT:The_Agile_Manifesto]]
[[Northern SPIRIT:Backlog_Grooming]]
[[Northern SPIRIT:Sprint_Planning]]
[[Northern SPIRIT:Daily_Standup]]
[[Northern SPIRIT:Sprint_Review]]
[[Northern SPIRIT:Retrospective]]
Looking for help with using redmine? Check out the "Redmine Wiki":https://www.redmine.org/projects/redmine/wiki