-
Notifications
You must be signed in to change notification settings - Fork 191
Sprints
A sprint represents a timeboxed effort towards a group of goals.
- Sprints typically last two weeks or 10 working days.
- Each developer is responsible for about 50 story points in an average sprint.
- Once a sprint begins, issues should remain fixed, with exceptions for urgent hotfixes.
- Sprints begin with a sprint kickoff and end with a sprint retrospective.
- Sprints are mirrored in GitHub through Milestones.
During a sprint, the task board is at the center of everything you'll do.
- Bookmark the URL of the sprint on the task board with the appropriate filters for easy access.
- Drag and drop issues into correct pipelines as progress is made.
- Hide distracting clutter on the tasks board using filters.
Before a sprint begins, the team meets to discuss the goal of the sprint and the issues it contains.
If a feature isn't tested, it cannot be done. Testing is a continuous process during sprints. You are responsible for testing the code you write.
Once you have fully developed and tested an issue you should drag it into the "Ready for QA" pipeline for final review by the project manager.
When the sprint finishes, the team discusses whether the sprint matched its definition of success and discusses what can be done to make the next sprint even more successful.
Work not completed during a sprint is reviewed and either moved to the next sprint or returned to the Product Backlog for future consideration if priorities have changed.
This Wiki is focused on GiveWP development. For help using our WordPress plugin, head over to our website where you'll find Plugin Documentation and Support.