hackforla / hackforla/product-management
Experience Profile: Jack Haeger
- Dominant language
- No language data
- Stars
- 55
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
### Overview
Fill in the following fields as you work on these items at Hack for LA. Add the link of the items you worked on in the list as examples.
### Action Items
- [ ] [Provisioning the Project]()
- [ ] [Product One Sheet]()
- [ ] [Organizing project resources (Google Drive)]()
- [ ] [Managing the project board]()
- [ ] [Making good issues (Reference - https://www.hackforla.org/guide-pages/github-issues)]()
- [ ] [Prioritizing the backlog]()
- [ ] [Storypoints]()
- [ ] [Recruitment (adding postings to open role boards by practice area)]()
- [ ] [Team Onboarding process]()
- [ ] [Cross functional team management]()
- [ ] [Project Inventory]()
- [ ] [WIKI (project documentation)]()
- [ ] [Communication Style Guide]()
- [ ] [Competitive Analysis]()
- [ ] [User Persona/Journeys]()
- [ ] [OKRs and WBS]()
- [ ] [Product Roadmap]()
- [ ] [Ecosystem map of stakeholders and touchpoints]()
- [ ] [Presentation Deck]()
- [ ] [Template/Guide Creation]()
### Resources/Instructions
Contributor guide
Research direction
Start with the Action Items checklist in this issue and review the linked Hack for LA GitHub issues guide plus each referenced work area. The scope spans project provisioning, resources, onboarding, management, research, and documentation; done would mean completing the applicable items and adding links to representative work.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100