This repository was archived by the owner on Jun 18, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Team practices
Melissa Braxton edited this page Oct 16, 2019
·
1 revision
The team:
- Uses sprint planning to commit to a set of issues achievable within a sprint
- Maintains and abides by a shared definition of done
- Maintains an open project board of planned, in progress, and completed issues
- Works with the Product Owner to groom and break down issues and user stories as the project permits
- Has an agenda for sprint ceremonies
- Regularly conducts sprint reviews to show work and get feedback on these from other team members as well as stakeholders or other interested parties
- Regularly participates in retrospectives
Home
How we work
- Roles
- Team practices
- Sustainment plan
- Considerations when reviewing vendor proposals
- Open Forest Design System
- Accessibility checklist
- Usability Test Quality Heuristics
Technical information
Ongoing updates
Resources
User research
- Field trip 1: Observing frontliners and fuelwood permit purchasers at Mount Hood
- Firewood permit service blueprint, current state
- Field trip 2: Observing LEOs in the field
- Usability Test 1: Online permit buying flow and printable load tags
- Topline: Timber Permitting E&I interview
- Topline: Require Permit Information For Permittee
- Usability Test 2: Firewood Landing Page (September 2020)
- Usability Test 3: Load Tag (September 2020)