My Message close
GAME JOBS
Latest Jobs
spacer View All     Post a Job     RSS spacer
 
May 24, 2013
 
DoubleDown Interactive
Software Game Developer
 
Autodesk, Inc
Senior Principal Engineer - 2D Engine
 
Kabam
Backend Game Engineer
 
Gameloft
Senior Programmer
 
LeapFrog
Game Designer
 
YAGER Development
Senior Game Systems Designer (f/m)
spacer
Blogs

  Planning for Proof of Concept Tech
by Stephen Northcut on 06/24/12 11:25:00 pm
2 comments Share on Twitter Share on Facebook RSS
 
 
The following blog was, unless otherwise noted, independently written by a member of Gamasutra's game development community. The thoughts and opinions expressed here are not necessarily those of Gamasutra or its parent company.

Want to write your own blog post on Gamasutra? It's easy! Click here to get started. Your post could be featured on Gamasutra's home page, right alongside our award-winning articles and news stories.
 

Proof of Concept Tech, as we define it at the Guildhall at SMU, is the milestone in which the development team verifies the game concept is attainable in the game engine. For this milestone my team is responsible for four distinct levels. These include a programmer sandbox, a level design whitebox, an art reference level, and a production level, which contains UI elements and sound.

When planning for this milestone my team used the fundamentals of Scrum to help us. We created a Product Backlog to get a wholistic view of the requirements of the project. After creating the product backlog, we took the highest priority tasks from the list and started to break them down into more detailed tasks.

One of the most important parts of this process is letting the team members make estimates for how long each task should take. This really helps the team members fully commit to the project. There is no other person telling them how long it should take for them to complete a task. They are the only ones who truely understand how much they know and how long it will take them to complete their task. That doesn't always mean that they make perfect estimates on their tasks, but after the task is completed they have a better understanding for the next time they plan a similar task.

 
 
Comments

Elizabeth Stringer
profile image
How did the teams estimate their tasks?

Stephen Northcut
profile image
The team didn't have any experience to fall back on, so they had to make estimates based on similar tasks they completed in their other classes. Each team member was responsible for making the estimates for their own task. I helped to guide some of the estimates if they seemed to be too long, since I have previous experience with making a game in UDK.


none
 
Comment:
 




 
UBM Tech