- Clear and structured responsibilities for each team and member - OKRs and KPIs are key to aling interes within stake holders - dinamic and retrospective aproach on team activities and responsibilities create a collective mind set and develope better problem solving.

Milestone-Based Delivery with Iterative Releases: Use these milestones to align creative, technical, and business stakeholders. Clear Backlog Prioritization Establish Clear Quality Metrics: Define criteria for success for each sprint and milestone (e.g., frame rate benchmarks, player retention metrics). Build Resilience to Scope Changes: Maintain a flexible scope by setting a baseline for “minimum viable product” (MVP). New features or ideas should only be added after MVP goals are met. Risk Management: Identify risks (e.g., technical challenges, creative disagreements, team turnover) early and create mitigation plans. Use retrospectives to analyze what went wrong and adapt processes accordingly.

Managing a large-scale game project with agile requires: 1. Tailoring Agile: Hybrid approach for milestones like alpha/beta. 2. Collaboration: Cross-functional teamwork. 3. Iterative Progress: Playable builds each sprint. 4. Quality: Continuous testing and bug prioritization. 5. Scalability: Modular work with CI/CD pipelines. 6. Vision: Adaptable Game Design Document. 7. Post-Launch: Plan updates and incorporate feedback.

- Break the project down into as many small steps as possible. -Designate team members with clear and concise directives. -Designate leaders highly adept at their tasks. -implement measurable qualitative and quantitative kpis to track spending and productivity. -Design the project to be malleable enough to adapt with roadblocks and speed-bumps(build in alternative time tables and be able to adapt to time restraints by getting other parts of the project done) -Consistently evaluate and update the project plan throughout the process