-
Notifications
You must be signed in to change notification settings - Fork 0
Admin
- All member and non-member pages front-end
- Learn the admin side of things
- Add names to the readme
- Learn the admin side of things
- Add names to the readme
- Backend login, sign-up handled
- Admin pages done
- Backend ticketing done
- Frontend ticketing done
- Everything complete
- Bug tested
- Documented
A sprint is a set period of time during which specific work has to be complete. A user story is used for a sprint per person. Each user story issue has all the relevant information required for that feature. An Epic is a collection of tasks that overarch a large feature.
We will have meetings per fortnightly cycle (2 weeks).
Week 1:
- Wednesday - 2 hours - Sprint Review, Retrospective, Planning
- Friday - 15 minutes - Chat/Stand-up
- Sunday - 2 hours - Dev Session (optional, available for you if you have questions)
Week 2:
- Wednesday - 1 hours - Mid sprint stand-up, dev check-in
- Friday - 15 minutes - Chat/Stand-up, next sprint tasks assigned
- Sunday - 2 hours - Dev Session (optional, available for you if you have questions)
Within one of the meetings, you will have the option to pick up an issue. I will assign that issue to you. Move it to the "To Do" list within the projects page of GitHub. When you begin, move it to the "In progress" list. Once complete, move it to the "Waiting For Merge". Once the tech lead has reviewed it, it will go through automated testing and be moved to completion.
Each ticket has information and acceptance criteria. Please inform the tech lead how you plan to tackle this issue before coding it up and getting approval from them prior to starting.
Make sure that you create a branch for every new issue you solve.
Please follow the best practices page when using GitHub and coding