📑 Change Request Policy Summary

1. Sources of Change Requests

New features, improvements, or bug fixes can originate from:

• Sales Team: Identifies opportunities or gaps and creates a Product Requirements Document (PRD).
• Customer Success Team: Brings forward client needs or issues and creates a PRD.
• Any Team: Reports technical issues or bugs in the bug tracking system.

2. Prioritization Process

• The Product Team owns the prioritization process through a weekly roadmap.
• Each week, PRDs and bugs are reviewed, and priorities are selected based on:
  • Client acquisition or retention impact
  • Technical urgency
  • Overall business impact
• The Tech Team reports progress every Friday, listing completed and pending tasks, and updating the sprint board.

3. Preparation for Execution

• The Product Team prepares a Project Card, assigns a Tech Responsible, and defines events and metrics.
• The project is moved to the "Planned" stage.
• The Tech Team breaks the project into actionable tech cards and moves it to "Ready to Execute".

4. Execution Phase

• During the sprint week:
  • The Tech Team holds daily standups, works on tech cards, and tracks progress.
  • Once development and deployment are complete, the project moves to "Measuring Impact".