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.
- Group movement.
- Buildings fully working
- Map fully designed and created.
- Random modular map generation.
- Fog of war.
- Resource management.
- Wild animals.
- Pause menu.
- Particle systems.
- Minimap.
- Loading screen.
- Units and buildings can be upgraded.
- Main menu.
- Intro video.
- Alpha installer.
- Completely functional UI.
- Deathclaws.
- Polished game.
- No bugs left.
A release should be made with a time space of between one and two weeks betwen them. Knowing this the release dates should be the following:
| Release | Date | Release | Date |
|---|---|---|---|
| 0.1 | 8th of March | 0.6 | 22nd of April |
| 0.2 | 22nd of March | 0.7 | 3rd of May |
| 0.3 | 29th of March | 0.8 | 16th of May |
| 0.4 | 5th of April | 0.9 | 24th of May |
| 0.5 | 12th of April | 1.0 | 31st of May |
These release dates may be changed through time depending on unexpected problems through development.
A more detailed approach of what each release will include is detailed in our Tech Design Document.
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 |
| A release date is close and the work delay is too big to get in time | Likely | Medium-high | All team puts more effort to get as close to the expected content of the release as possible but trying to avoid introducing dangerous bugs |
| A member is on a holiday with no computer for more than 2 days | Likely | Medium-High | The member has to notify to all the team this situation to prevent a posible delay in the build |
| A member gets very sick | Likely | Low-Medium | Probably the member would work but with a lower quality and performance so it's possible to expect delays, the team can anticipate this situation and adapt the schedule |
| Time for a milestone was heavily misscalculated and in the middle of the process some tasks are impossible to be commited in order to deliver in time | Unlikely | Very high | The group does a quick meeting in person or by call and priorities are checked. Tasks are ordered depending on their importance and all the team tries to do them in order to at least complete the most important objectives on time. |
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, asing someone to help this member to fulfill this task on time.
| Meeting | Postmortem | Versions | |
|---|---|---|---|
| Sprint 1 - Team + Concept Discovery | All goals set and tasks distributed. To start with, all art should be included into the game, the wiki must be done and a simple movement and entity system must be implemented. | 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 |