Ticketing and work methodology system that ensures smooth project management, task prioritization, and team collaboration.

Ticket Management

Ticket Structure:

1. Title: Format as “Q_ / Title of ticket”. Include priority level (Q1-Q4).
2. Description: Provide detailed descriptions with context.
3. Tags: Add relevant tags (Critical-Low, etc.) to highlight urgency and resource requirements.
4. Multimedia Attachments: Embed videos (Loom, YouTube) or images as necessary.
5. Checklists: Tickets with multiple tasks should have a detailed checklist. These remain in “Pending Ticket” until all subtasks are added.

Order of Ticket Assignation:

1. Q1 & Q2 - Crucial & High Priority: These are the team's top priority. Focus on these before other tasks.
2. Quick Fixes: Quick-to-solve issues, prioritized by severity and urgency.
3. Q2 Medium & Q3 Low Priority: Work on these when all critical tasks are cleared.

Ticket Statuses:

• Read Me: Essential information for system understanding.
• In Hold: Paused due to missing information.
• Pending Ticket: Awaiting full details.
• Backlog: Available for future assignment.
• To Do: Assigned and ready for developers to begin work.
• Doing: Actively in progress.
• In Review: Waiting for code review or approval.
• Done: Completed and deployed.

Prioritization and Ranking Matrix

Quadrant System:

• Q1 - Important & Urgent: Immediate attention. These tasks cannot be delayed.
• Q2 - Important, Not Urgent: Major goals with flexible timelines.
• Q3 - Urgent, Not Important: Potential disruptions; these tasks prevent processes from working smoothly.
• Q4 - Neither Important nor Urgent: Distractions or low-priority tasks.

Value Tags:

• Critical: Business-critical tasks that must be solved immediately.
• High: Significant but non-critical tasks.
• Medium: Important tasks but less urgent.
• Low: Tasks with minimal urgency or impact.

Weekly Workflow

Mondays: Planning

• Task Prioritization: Identify critical tasks to be completed by the week's end, focusing on what is both urgent and important.
• Sprint Review: Assess last week's sprint—what was completed, what remains pending, and any delays.
• Backlog and Pending Tickets: Quickly review the Trello board for In Review and Backlog tickets, holding each team member accountable for their work.
• Ticket Assignment: Assign tasks for the week by moving tickets from Backlog to "To Do", while cleaning out last week's "Pending Review" tickets.

Wednesdays & Thursdays: Q&A

• Objective: Facilitate communication around ongoing tasks, answer questions, and remove blockers.

Fridays: Showcase

• Objective: Showcase results to at least one team member to review.