Github Project Workflow

Assumptions:

• Due dates for all Ready (this week) Tasks

Estimations table:

Time spend	less than 30 min	1 hour	2-3 hs	4-5 hs	entire day	More than 1 day	Split into smaller stuff
Estimation Size	0	1	2	3	5	8	13
Examples	Adding a comment	add a function		Changes in multiple tools		Refactoring

1. Triage

Explanation: This is the initial status for all new issues or tasks. During triage, the team reviews and assesses the task’s priority, relevance, and completeness. It’s essentially a sorting phase where decisions are made about the next steps.

Key Activities:

• Review new issues.
• Ensure the issue contains enough information to be actionable.
• Determine the initial priority and assign labels if necessary.
• Decide if the issue should be moved to the backlog, handled immediately, or closed as ‘Won’t Do’.

2. Backlog

Explanation: Tasks that have been reviewed during triage and are deemed valuable but not immediately actionable are moved to the backlog. The backlog is a holding area for tasks that the team intends to address in the future.

Key Activities:

• Regularly prioritize tasks.
• Refine tasks to ensure they are well-defined and ready to be moved to the next stages when the time comes.
• Continuously groom the backlog to keep it manageable and relevant.

3. Ready (This Week)

Explanation: Tasks in this status are prioritized and selected from the backlog to be addressed in the current week. Tasks in this status must be estimated and have a due date assigned. This ensures the team has a clear focus and knows what needs to be accomplished in the immediate term.

Key Activities:

• Review and confirm that tasks are ready to be worked on.
• Estimate the effort required for each task (e.g., story points, hours).
• Assign due dates to each task to provide a clear timeline.
• Assign tasks to team members.
• Make sure all necessary resources and information are available for the task.

4. In Progress

Explanation: Tasks that are actively being worked on by team members. This status indicates that work has started and the task is being actively developed or addressed.

Key Activities:

• Work on the task.
• Regularly update the status and comments to reflect progress.
• Collaborate with team members as necessary.

5. In Review

Explanation: Tasks that have been completed by the developer and are now waiting for review. This could be code review, design review, or any other type of peer review to ensure quality and correctness.

Key Activities:

• Submit work for review.
• Reviewers provide feedback, request changes, or approve the work.
• Iterate based on feedback until the task meets the acceptance criteria.

6. Done

Explanation: Tasks that have been completed and reviewed successfully. This status indicates that the task has met all the criteria and is now finished.

Key Activities:

• Confirm that the task meets all requirements and acceptance criteria.
• Close the issue.
• Optionally, document the completion and any relevant outcomes.

7. Won’t Do

Explanation: Tasks that are no longer deemed necessary or relevant. This status is used to close tasks that won’t be worked on, either because they are outdated, irrelevant, or not feasible.

Key Activities:

• Provide a clear reason for why the task is being closed.
• Communicate this decision to the relevant stakeholders.
• Close the issue to keep the board clean and focused.

Workflow Overview:

1. Issue Creation: New tasks are created and automatically placed in Triage.
2. Triage Meeting: The team reviews tasks in Triage and decides whether to move them to Backlog or close them as Won’t Do.
3. Backlog Grooming: Regular sessions to prioritize and refine tasks in the Backlog.
4. Sprint Planning: During planning meetings, tasks are moved from Backlog to Ready (This Week) based on priority and team capacity. Each task must be estimated and have a due date assigned.
5. Development: Team members pick up tasks from Ready (This Week) and move them to In Progress as they start working on them.
6. Review Process: Completed tasks are moved to In Review for peer review and feedback.
7. Completion: Once reviewed and approved, tasks are moved to Done.
8. Triage Cycle: Continuously triage new tasks to maintain a manageable and prioritized backlog.

By ensuring that all tasks in the “Ready” status are estimated and have a due date, the team can better manage their workload and track progress against deadlines. This addition enhances planning and provides a clearer roadmap for the immediate term.