This repository has been archived by the owner on Nov 10, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 41
Joining the Natural Resources Revenue Data project team
lpgoldstein edited this page Jan 15, 2020
·
19 revisions
Follow the instructions in the onboarding checklist to create an issue that will guide you through tasks that will lead you through the product orientation and get you up to speed and contributing in no time. Track your progress by checking the boxes as you complete tasks.
This site provides open data about natural resource management on federal lands and waters in the United States, including oil, gas, coal, and other extractive industries.
We're in the process of migrating the style guide from Fractal to a React-based pattern library.
The regular cadence of sprint activities. Each meeting has a video call link in the calendar event. The product manager will invite you to each.
| Meeting | Description | Regularity | Duration |
|---|---|---|---|
| Sprint planning | At sprint planning meetings, the tasks that the team agrees they can complete over the course of the sprint are prioritized and assigned for completion. | First Monday of each new sprint | 1 hour |
| Sprint demo | Sprint demos allow the team to present work that was completed in the sprint to other team members and stakeholders. They also create opportunities to others to ask clarifying questions. | Second Thursday of each sprint | 1 hour |
| Sprint retro | Retrospectives allow the team to reflect on the sprint that just finished and discuss what's working and what's not. This allows the team to identify areas to improve. | Second Thursday of each sprint | 30 minutes |
| Standup | Daily standup meetings allow team members to share progress on assigned tasks and surface any blockers to their work. | Every day except the first Monday of the sprint and the second Thursday of each sprint (the days with sprint planning and demo/retro meetings) | 30 minutes or less |
| Roadmapping | Roadmap check in meetings allow the team to plan work spanning several sprints. | Every 6-8 weeks | 60 minutes |
| Backlog grooming | During backlog grooming, the team goes through open issues to close duplicate or unnecessary issues and to assign remaining issues. | Monthly | 60 minutes |
- 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