target process documentation - raeker/ARC-Wiki-Test GitHub Wiki
Advanced Research Computing : Target Process Documentation
- TP View - Team - Tasks by Person
- Agenda
- Purpose
- TP View - Sprint Task Board
- Already sorted in Sprint Priority Order
- Take tasks that you can work on
- DO NOT take items pre-maturely. Generally if your actively
working on it
- TP View - My Work
- Just your items you have claimed
- Epic - Longer than a feature / Could be related to MVP milestones
- Features - 2 sprints or less
- User Story - 3-5 days or less
- Task - One person no more than 1 day
- Descriptions
Cross Team Hand off - User story or higher NO TASKS
- Project Planning - At start of project
- Roughing out definition of done for a project
- Epics and Features, small group
- Include some experts
- Generate stories
- Stories Descriptions / definition of done
- Sprint Planning - Process every two weeks
- TP View - Sprint Planning <team name>
- Contains Stories and Bugs
- Backlog Grooming next Sprint Generation - Shortly before
Managers Sprint Planning
- review everything in current sprint and create next sprint
- <jointly review at Managers planning meeting> - Only Bug,
Feature or Epic
- Before next sprint 'Finish' current sprint
- Select 'Move User Stories'
- Sprint Planning with your team
- Stories and Bugs
- Stories
- Goal: Team is happy with title and definition of done
- Title: For (person benefiting): I need Y
- Description
- Summary:
- Definition of done: Very Important
- Points (Relative complexity)
- Team creates tasks
- Goal: if all are completed definition of done is met
- Relations (Dependencies)
- Generally Story Level only and not tasks
- Is Points still valid for complexity?
⚠️ **GitHub.com Fallback** ⚠️