Floating responsibility for Issue Tracker

[VojtechBartoska]

This discussion is tracking floating responsibility for this Project Issue Tracker.

Team members Order for floating responsibility:

• me-no-dev
• SuGlider
• lucasssvaz
• P-R-O-C-H-Y
• VojtechBartoska

How it Works:

Weekly Rotation: The responsibility for managing the issue tracker rotates among team members on a weekly basis, following the sequence of Team members written above.

Primary Point of Contact: The assigned team member becomes the primary point of contact for all issues, tasks, and updates related to the issue tracker during their designated week.

Key Responsibilities:

Issue Triage: Effectively triage incoming issues, ensuring they are correctly categorized, prioritized, and assigned to the appropriate team member for resolution.

Communication Hub: Act as the central communication hub for issue-related discussions, updates, and resolutions within the team.

Progress Tracking: Regularly update the team on the status of ongoing issues, highlighting any challenges, and proposing solutions.

Collaboration Facilitation: Foster collaboration by ensuring that relevant team members are involved in discussions and resolutions, promoting a smooth workflow.

Benefits:

Diverse Skill Exposure: Team members gain exposure to different aspects of our projects and enhance their skills by managing diverse types of issues.

Collaborative Environment: Encourages a collaborative environment where every team member contributes to all areas of the Project.

Shared Responsibility: Distributes the responsibility of issue tracking evenly among team members, preventing burnout and promoting a sense of shared ownership.

[VojtechBartoska]

This comment will be updated every week with Issue tracker responsible person:

• 25.-29.03.2024 - @me-no-dev

[VojtechBartoska]

Status update:

• currently we are able to manage Issue tracker more easily so we will drop floating responsibility approach and keep assigning the issues to area managers by any Developer