How do you pick the right way to do "project management fundamentals" like scheduling and status tracking, for the size and culture of your environment? This mini-case study relates the experience of a small game company's founder and the decisions he made for making PM work for a fast-moving, bureaucracy-hating team.
What this is
At a software game development company, an inexperienced but highly conscientious company founder was trying to get a handle on the state of the company's projects and figure out how to manage these teams day to day, to ensure they'd meet key customer dates. The company was undertaking a critical project for a new customer; payments to the game company (and the ability to make payroll!) would depend upon hitting monthly milestones for certain deliverables. To the founder, it was clear some kind of management was needed to ensure these dates would be hit.
Why it's useful
This type of technical work is very iterative, judging completion is very subjective, and the finished product involves many small detailed pieces of work that must be touched by multiple team members: e.g., video footage, sound files, graphics objects, software modules. These teams are full of creative folks who may be very resistant to anything that looks like a "limiting process" or bureaucratic management--especially if that management takes up their precious time. (Status reporting? Yuck! Low-value! Go away!) Sound familiar?
How to use it
Spend 10-15 minutes reading this mini-case to find out what techniques the found used to get the information he needed to manage the project and meet the dates.
©Copyright 2000-2017 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail email@example.com