-
Notifications
You must be signed in to change notification settings - Fork 0
Production Plan
Dates | Miletsones | Versions | |
---|---|---|---|
Sprint 1 - Concept Discovery | 24th of February - 9th of March | Milestones 1 | 0.1 |
Sprint 2 - Vertical Slice | 9th of March - 23rd of April | Milestones 2 | 0.2, 0.3, 0.4, 0.5 |
Sprint 3 - Alpha | 23rd of April - 17th of May | Milestones 3 | 0.6, 0.7, 0.8 |
Sprint 4 - Gold | 17th of May - 1st of June | Milestones 4 | 0.9, 1.0 |
In order to reach our goal of completing the development of Fallout Strategy in time and leave no bugs in he final versions we have set some milestones distributed through this four big sprints which finish in the delivery dates:
- Polished idea of the game.
- All art included into the game.
- Basic entity system and movement implemented.
- Wiki finished.
- Zoom.
- Player can create and control multiple entities.
- Buildings fully working
- Map fully designed and created.
- Fog of war.
- AI.
- Random modular map generation.
- Alpha installer.
- Deathclaws.
- Completely functional UI.
- Polished game.
- No bugs left.
Click the image watch it bigger:
Gant done in instagantt.com
Risk | Probability | Impact | Solution |
---|---|---|---|
A member leaves the team | Very unlikely | Very high | His tasks will be distributed equally between the other team members |
A member's computer stops working for a medium period like a week | Unlikely | High | Part of his tasks will be equally distributed between the other team members but this member must find a way to keep working to at least do a part of the taks he should be doing |
Fatal error in the build which makes the game crash | Likely | High | The members in charge of code try to find the bug. If it's not found quickly and a release must be made to accomplish the milestone, the whole team helps to find the bug |
Even though we have 4 sprints we meeting once a week to discuss and distribute tasks among the members of the team, for this distribution we are using Hacknplan a webpage with many interesting tools to control the workflow, the times and the current situation of every task. Normally the asignation and control of this tasks is done while meeting by the Leader or the Manager. If any of the team members is not going to accomplish a task in it's respective time he has to comunicate this to the manager so he can update the Hacknplan to a new date or, if possible, asign someone to help this member to fulfill this task on time.
Meeting | Postmortem | Versions | |
---|---|---|---|
Sprint 1 - Team + Concept Discovery | Meeting conclusions | Postmortem | Log of deviation |
Sprint 2 - Vertical Slice | Meeting conclusions | Postmortem | Log of deviation |
Sprint 3 - Alpha | Meeting conclusions | Postmortem | Log of deviation |
Sprint 4 - Gold | Meeting conclusions | Postmortem | Log of deviation |