|
https://andersdotgames.wordpress.com/2018/02/08/post-1-360-no-scoping-the-project/
“It is very fun to see that your group picked something else than behemoth and that boaty concept document.
your blog starts with listing things that are going to be hard for your group to accomplish, and as soon as the project started you had to bring out the chainsaw to cut features. Were these things you thought of before or after you agreed on picked the concept document?
If this is something you and your group noticed after I think it could be valuable in the future to do a risk analysis on project feasibility beforehand.
Anyway, even if you as a group noticed the risks and problems before or after I salute you on how fast you identified the problems and started cutting features.
Another thing I feel could be added to this blog post is the general discussion you had in the group when deciding on what to cut. Did you start by finding features the game could do without, or did you start by identifying the core mechanics “must have’s” for the game to hit the goal aesthetic? I would recommend doing the later, sense it’s very important that you don’t cut features without first analyzing what mechanics and features will give the desired dynamics so the game hits the ascetics set in the concept document.
Very fun and interesting post Anders, was a pleasure reading.”
About Vidar Grönros
2017 Project Management
|
