-
-
Notifications
You must be signed in to change notification settings - Fork 0
Product Manager and Owner
Each of the resources below can be considered a work-in-progress. These resources will evolve and adapt as the team and team needs change. Feel free to open an issue with a link to whichever resource needs improvement and a description of the suggested change.
-
Learn how we setup our GitHub Kanban boards and please comment if there is anything in the document that is unclear.
-
This Software Development Lifecycle Diagram is a sample of what the process is generally like at Hack for LA and each project is different.
-
Review our Milestones.
-
Communicate with other product team members and leadership to discuss project priorities and strategic direction.
-
Open this link and change the parts in brackets "[ ]" with your name
-
Submit the issue
-
Self Assign the issue
-
Add the issue to the project board
-
Move the issue to the In progress column
-
Let us know when you have completed these steps by posting in the #guides Slack channel
-
Provide weekly updates (in comments at the bottom of your issue) using this template
Please provide update 1. Progress: 2. Blockers: 3. Availability: 4. ETA: 5. Pictures (if necessary):
How to fill out the template
Please provide update Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."
-
Review your notes with the team at team meetings.
-
Review the Project Board and the Product Management issues available on that board to identify an actionable backlog item.
The Wiki is a working document and we would love to improve it. Please compile any questions and suggestions you may have and submit it via creating an issue.