These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Gaming Studio Project Mgmt
- Process
- Plan work
Plan work
Admin establishes an active studio organization, project context, and team membership. Project Coordinator then gives a package its owner, counterparty, due date, budget hours, and task plan. The baseline action checks scope and dependencies before work starts.
Step by step
-
Set project scope Admin
Admin checks the organization, eligible project, and active membership. The package must belong to the same organization as its project and owner.
- Establish matching scope and membership
- Updates Organizations, Projects, Team members
-
Plan a work package Project Coordinator
Project Coordinator prepares a draft package and checks the project, owner, due date, budget hours, and current revision. Moving to Planned means the scope is ready for the baseline check.
- Record plan and Draft to Planned transition
- Updates Work packages, Projects
-
Baseline the work Project Coordinator
Project Coordinator checks task identities, dependency cycles, planned hours, expected revision, and stable operation key. A valid baseline freezes its revision and moves the package from Planned to Active.
- Freeze baseline and record guarded outcome
- Updates Work packages, Tasks, Operation receipts
Who does what
Roles and permissions- Admin
- Maintains scope; Project Coordinator owns the package plan and baseline.
Set up Gaming Studio Project Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.