Consolidating Brands and Integrating Development Teams with KanBo

KanBo serves as a global coordination platform—integrating development teams, aligning product delivery, and supporting franchise lifecycle governance.

I. Franchise-Centric Organizational Workspaces

  • Workspaces: Grouped by franchise and department (e.g., QA, Engineering, Creative).
  • Spaces: Tailored to product roadmapping, sprint planning, asset pipelines, and localization.
  • Templates: Standardize workflows across games and regions.

II. Task Management and Agile Execution

  • Cards: Used for bug tracking, new feature implementation, and regional content adaptation.
  • Card Relations: Map out interdependencies across studios and functions.
  • Mirror Cards: Ensure task updates are reflected across regions for synchronization.

III. Resource Planning Across Borders

  • Resource Management: Assign roles and schedule engineers, artists, and QA across time zones.
  • Availability Sync: Integrated with HR systems for up-to-date personnel data.
  • MySpace Dashboards: Help leads balance assignments across multiple initiatives.

IV. Sprint Planning and Timeline Control

  • Time & Forecast Charts: Visualize sprint health, backlog velocity, and delivery forecasts.
  • Gantt Views: Align roadmap timelines with engineering and creative execution.
  • Card Blockers: Flag bottlenecks due to delays or unresolved issues.

V. Cross-Team Collaboration & Asset Governance

  • Comments & Presence Indicators: Enable instant feedback and team visibility.
  • In-Card Document Editing: Allows inline updates to specs, designs, and QA protocols.
  • SharePoint Integration: Centralized version-controlled asset management.

VI. Real-Time Oversight and Performance Visibility

  • Program Dashboards: Provide the PMO and CTO with high-level performance insights.
  • Localization Tracking: Spaces monitor translations and compliance by region.
  • QA Reporting: Dedicated Spaces for bug status, fix rate, and compliance checklists.

Month 1 – Planning and Setup

Months 2-6 – Pilot Phase

Month 7 – Pilot Evaluation

Months 8-18 – Full Rollout