-
Notifications
You must be signed in to change notification settings - Fork 41
Planning and organizing our work
Epics should be used for discrete projects with a start and date that can be adjusted as needed and will likely encompass several sprints. Each Epic should go on the Roadmap. Epics are not for normal site updates and bugs.
Epics are also used to make 6-8 week work plans with a start and end date and are indicated by dessert names. These Epics should also be shown on the Roadmap found in Zenhub. These Epics contain the goals of the work plans and relevant issues are placed within these epics. Other Epics may be listed under these Epics if they will be completed within the specified time frame.
Try to ensure that Issues are an amount of work that can be completed within a Sprint. Issues should be placed under both project epics and work plan Epics as needed.
Labels are added to Issues to further describe and categorize each Issue. Labels should be used to help organize like Issues and help with work planning.
- Problem statement
- Product vision
- User scenarios
- What we're not trying to do
- Product risks
- Prioritization scale
- Joining the team
- Onboarding checklist
- Working as a distributed team
- Planning and organizing our work
- Sample retro doc
- Content style guide
- Content editing and publishing workflow
- Publishing a blog post
- Content audits: a (sort-of) guide
- User centered design process
- Research norms and processes
- Usability testing process
- Observing user research
- Design and research in the federal government
- Shaping process
- Preview URLs
- How to prepare and review PRs
- Continuous integration tools
- Releasing changes
- Github Labels