Kanban Board Re-Org

[nooriaali9]

Overview

This issue has been created for to reorganize the Kanban board, currently the board holds a lot of outdated issues & In progress issues that haven't been closed out which need attention.

Action Items

• Get updates from Dev team over outdated issues
• Get updates from UIUX team over outdated issues
• Create Column to track Ongoing issues
• Remove Ready Column - so from Questions & Reviews it moves onto done

Resources/Instructions

Resources

[nooriaali9]

Met with Karen in the PM meeting on 31 July, 2024 - discussed on what is to be worked on - will be tracking any updates here - https://docs.google.com/document/d/1wAlfkgoq2rc1G1QctiEVTXfsFVd-sloACr1lXWrTtPU/edit?usp=sharing

[kcoronel]

@nooriaali9 Jimmy is interested in deleting all the issues from dev. I think we can get to work on getting that done. I think keeping the ones assigned to a team member and those in the ice box for now.

[nooriaali9]

Possible updates to the board -

• Recurring Items - for all agendas - one stop shop
• Remove ready column
• Questions/Reviews - rename to - For Review/ Feedback Needed

Proposed Order of kanban board -

1. Icebox
2. New issue approval
3. prioritized backlog
4. Recurring items
5. In progress
6. For Review/ Feedback Needed
7. Done

Please let me know if this works for you guys @kcoronel @kchotani

[kcoronel]

I love this!! Can you confirm the definitions and workflow below @nooriaali9 @kchotani

Definitions

Icebox: Issues that are going to be addressed, but are not actively worked on because of dependencies.
New Issue Approval: Issues that are newly created or coming out of the icebox that need to be reviewed by Product Manager and/or Leads to prioritize.
Prioritized Backlog: Issues that are ready to work and are prioritized by milestone. This column should be prioritized from top to bottom, with the highest priority issues at the top.
Recurring Items: Issues that are left open to be used on an ongoing basis
In Progress: Issues that are assigned and actively being worked on.
For Review/Feedback Needed: Issues which need review or feedback in order to continue work.
Done: Issues that are complete

Workflow

1. Before Creating an Issue

• Search Existing Issues: Check if a similar issue already exists. This prevents duplicates and saves time.
• Discuss with the Team (if needed): If unsure about the issue or its priority, discuss it with relevant team members.

2. Creating a New Issue

Click on "New Issue": This button is usually located at the top right of the repository's "Issues" tab.
Select the Issue Template (if applicable): Choose the one that best fits your issue type (e.g., bug report, feature request) or choose 'create a blank issue'.

3. Fill in the Issue Details:

• Title: Write a clear and concise title that summarizes the issue.
• Overview: Provide the purpose of this issue in 2 sentences or less. Some ideas include
  • Steps taken, decisions made, expected behavior, actual behavior
• Action Items: If this is the beginning of the task this is most likely something to be researched and documented. If the issue has already been researched, and the course of action is clear, this will describe the steps. However, if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task.
• Research: If there is a site which has documentation that helps with this issue provide the link(s) here.
• Labels: Add relevant labels to categorize and prioritize the issue including role, size, and feature
• Assignees: Assign the issue to the appropriate person or team.
• Milestone: Lnk the issue to the relevant milestone.
• Choose the Right Repository: Make sure you're in the correct repository where the issue belongs.
• Choose the Right Status: New Issue Approval

3. After Creating the Issue

Link Related Issues: If the issue is related to other existing issues or pull requests, link them using keywords or issue numbers (e.g., "See also #123").
Monitor and Respond to Comments: Stay engaged with the issue by responding to comments and providing updates as needed.

Additional Tips

• Be Clear and Concise: Write in a clear and concise manner to ensure everyone understands the issue.
• Use Proper Formatting: Use Markdown formatting to structure your issue description and make it easier to read.
• Attach Relevant Files: If necessary, attach files like screenshots, logs, or code snippets to provide additional context.
• Follow Up: If the issue remains unresolved or requires further discussion, follow up with the assignee or team.
• Example Workflow