-
Notifications
You must be signed in to change notification settings - Fork 192
Task Boards
A task board is a board of issues representing all current and potential work associated with the project. The Development Team at GiveWP uses ZenHub to generate task boards based on GitHub issues.
The issues in each pipeline are ordered by priority with the highest-priority issues at the top. Team members should proceed through their issues by removing an issue from the top of the Sprint Backlog and moving it to In Progress.
Each pipeline on the board represents a stage in the development process. Issues generally proceed from left to right on the task board as progress is made towards completion.
The New Issues pipeline is the starting point of a newly created issue which remains in place until processed by a senior developer.
The Icebox holds low-priority issues that may be addressed some day. Generally these issues don't enter development unless conditions change such as additional customer interest or the removal of a technical barrier.
The Epics pipeline holds large, multi-issue epics so that they can be accessed easily and do not get mixed up with individual issues.
The Product Backlog holds issues that are next in line for development. This pipeline represents work that the team has committed to completing, but has not yet set a timeframe for completion. Issues in this pipeline that are labeled high-priority will be highly considered for inclusion in the next sprint.
The Sprint Backlog holds issues that are assigned to developers in the current sprint. This pipeline represents work the team has committed to completing in a two-week period of time but does not guarantee completion by the end of the sprint.
The In Progress pipeline holds issues that are currently under development. Each developer should ideally have no more than one issue in progress at any given time.
The Blocked pipeline holds issues that are impeded in such a way that the developer cannot move forward without additional discussion or action taken by another team member.
The Ready for QA pipeline holds issues that are ready for review with an associated pull request. Issues in this pipeline are expected to have been tested by the developer and proven to satisfy all acceptance criteria.
The Docs pipeline holds issues strictly limited to documentation. It is helpful to keep these issues separate from development-related issues since they are often addressed by the Support Team.
The Closed pipeline holds all issues that have been closed for any reason. Issues in this pipeline may be reopened if necessary.
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.