Kevuru Games

We start by discussing the project’s goals, scope, technical requirements, and production schedule with the client. Depending on the project, we review available documentation, design materials, technical specifications, and existing workflows.

Our producers and relevant specialists clarify open questions, identify potential risks, and agree on deliverables, timelines, and responsibilities before production begins. For ongoing development or co-development projects, requirements are reviewed with the client’s team as the work progresses.

We start by understanding what the client wants to achieve, whether it’s launching a new game, expanding an existing title, or supporting a specific part of production. We agree on priorities, deliverables, timelines, and responsibilities before work begins. Throughout the project, we review progress with the client, discuss feedback, and adjust plans when requirements change. Our goal is to make sure the work supports both the project’s immediate needs and the client’s broader production plans.

We adapt our development process to the project and the client’s existing workflow. For game development and co-development, we commonly use Agile practices, including Scrum and Kanban, with regular planning, reviews, and feedback. For art production, we often work with milestone-based schedules and approval stages. When joining an existing production, we follow the client’s established tools and processes.

We keep clients informed through regular progress reports, project tracking tools, and direct communication with the production team. Updates cover completed work, upcoming tasks, milestones, and any issues that need attention. Depending on the project, we share builds, art previews, or other deliverables for review. Clients have a clear point of contact and can discuss priorities or changes as production progresses.

Meeting frequency depends on the project and the client’s preferences. We typically arrange weekly progress meetings, with more frequent check-ins during active development, important milestones, or time-sensitive production stages. Teams working in co-development may also join the client’s regular stand-ups and planning sessions. Between meetings, we stay in touch through agreed communication channels.

Quality checks are part of our production process. For game development, we review functionality, performance, and compatibility with project requirements. For game art, we check assets against approved references, technical specifications, and engine requirements. Depending on the scope, our teams also perform testing, internal reviews, and revisions before delivery. We work with clients to resolve issues identified during their review.

We assess potential risks during project planning and continue reviewing them throughout production. These may include technical challenges, unclear requirements, dependencies, or schedule constraints. When an issue arises, we discuss its possible impact with the client and agree on the next steps. For complex tasks, we may recommend an early prototype or technical assessment to identify problems before committing to a larger production scope.

Post-delivery support depends on the project and the agreed scope of work. We can assist with bug fixes, performance improvements, platform updates, and further development after release. For ongoing projects, our teams can continue supporting new features, content updates, and technical maintenance. The duration and level of support are agreed with the client based on the project’s needs.