game production process
.png)
What is Scrum?
Watch this video to learn more about Scrum
Watch this video to learn more about Scrum
Everyone on the team is valuable and each of them has a vital role in the Scrum framework. Roles help each person know what their responsibilities are and who to ask for support.
The work horse of the Scrum process. These are the coders, artists, and developers of the team. Their roles are diverse but unified under each project's goals.
This person sets clear expectations for the Bencin Studios Development Team and owns the tasks that must be done in order to launch your game.
The Scrum Master inspires, motivates, and protects the Development Team. Their role is to remove blockers and provide resources to our team to ensure they have everything they need to build your game.
Every day is filled with events that help the team work together effectively and communicate accountability and support to each member!
What- The planning period for the work to be done within the next Sprint
Why- Ensures the Team knows what tasks to work on for the client for that Sprint
When- Beginning of Sprint, after Sprint Retro
What- Inspect the work done and adapt the backlog
Why- Allow the Team to collaborate on tasks and find more value for the client
When- End of Sprint, before Sprint Retro
What- Inspect the Team and create a plan for improvements for upcoming Sprint
Why- Provides a plan for improving work done on the client’s next Sprint
When- End of Sprint, before Sprint Planning
What- Brief conversation to inspect progress toward the Sprint Goal and identify impediments
Why- Allows for communication for quick decision-making and collaboration
When- Every morning before the work begins
What - The planning period for the work to be done within the next Sprint
Why - Ensures the Team knows what tasks to work on for the client for that Sprint
When - Beginning of Sprint, after Sprint Retro
What - Inspect the work done and adapt the Backlog
Why - Allows the Team to collaborate on tasks and find more value for the client
When - End of Sprint, before Sprint Retro
What - Brief conversation to inspect progress toward the Sprint Goal and identify impediments
Why - Allows for communication for quick decision-making and collaboration
When - Every morning before the work begins
What - Inspect the Team and create a plan for improvements for upcoming Sprint
Why - Provides a plan for improving work done on the client’s next Sprint
When - End of Sprint, before Sprint Planning