• General Calendar
  • Sprints
  • Milestones
• Risk and Contingency List
• Gantt Chart
• Budget
• Sprint Record and Log of Average Estimation Deviation
  • Sprint 1: 20/2/2018

For the production of the Warcraft II: The Stolen Artifacts project, we have arranged a planning for a duration of 17 weeks for it to be completed and ready to go public.

• Weekly Objectives will be set to assure a controlled progression.

• Group Face-to-Face Meetings will take place every Tuesday from 12:00 to 15:00. In these meetings, last week objectives will be reviewed, analysed and evaluated to set the new objectives for the following week.

This weekly plan will be taken into an excel document to recollect all the information on every single one of the 17 weeks:

• During the week we will need to be communicated in order to keep track of which member is doing what and when, or if any problems occur in the duration of the sprint. For this, everyone will be using Trello; there will be the tasks "To Do", "In progress" and "Done". Slack will also be used by everyone in order to talk about anything regarding the project, different channels are included to avoid confusion, these are "General", "Code", "Design", "Art" and "UI".

• Monday and Friday at 14:00, we will all have a 15 minute Face-to-Face talk to inform everyone on how they are doing with the sprint that week.

• Each Saturday a Build will be created of the progression done during the sprint and the next day it will have to be tested and analysed to know which bugs have to be fixed on Monday.

We have assigned four different milestones which will be included as deliveries in this github project. With the controlled sprints and an in-depth planning, we can be sure that these will be completed:

Concept Discovery (March 4th)

• Game Design Document
• UI Document
• Art and Audio Bible
• Tech Design Document
• QA Plan
• Production Plan

Vertical Slice (April 15th)

• Sprites/Animations
• Player Movement and Abilities
• Random Map Implementation
• Portals
• Basic UI
• Battle System
• Win/Loss Condition

Alpha (May 13th)

• All Map Designs
• UI Complete
• Everything Functionable
• Boss and Rest of Characters

Gold (June 6th)

• Fix Final Bugs
• Polish and Complete Game
• Website
• Trailer
• Gameplay
• Spreadsheet

Our plan is to have the minimum amount of problems as possible in the development process of the project, but we know that we still might encounter problems regardless of a good previous organization. On that note, we have to be prepared and know how to act if one of them appears so that we can fix it and continue to work as fast as possible, because time is essential.

RISK	PROBABILITY	IMPACT	SOLUTION
A team member of the team leaves the project.	Really Low	Really High	The tasks that the member had will be assigned to the rest of the team and extra hours will be have to be put in holidays, weekend or nights to complete his tasks during the remainder of the project. If this is not possible, some of the additions to the project will have to be cancelled in order to assure that we have time to complete a functional and fun game with the members we have.
A team member falling sick.	Medium	Medium	His tasks will be distributed to the rest of the team during his absence if he is incapable of working.
The objectives in a Sprint are not completed.	Low	Medium	First of all, the members should inform the rest that they can not finish the task before the end of the sprint so that the rest can help to complete it in time. The unfinished task will be evaluated to decide if the other members should help complete the task in time or if it can wait and put an extra effort to complete it the following week.
The objectives in a Milestone are not completed.	Really Low	High	This will be seen the last weeks before the date of the milestone but it is really unlikely to happen as there are weekly controlled sprints. Even though, if it does happen, every member should leave what they are doing and focus on completing the tasks of the respective milestone in order to present a functional delivery.
Some frames in the animations are not correclty centered.	High	Low	Members in charge of art will be assigned to improve the spritesheet in order for the animation to be correct depending on its priority.
Error in a commit.	High	Medium	The QA responsible will be in talks with the member in problems and together they will fix the error using the last commit done before that.
Team member computer does not work.	Low	High	This member will work temporarly with the computers provided in the CITM or with another team member's computer.
New characters are harder than expected to implement.	Low	Medium	The group will have a meeting to discuss whether we can fix the problem in time or if we should eliminate these characters and reorganize the balance of the game with the member in charge of design.
Map randomness is having issues.	Really Low	Really High	Map randomness and logic are a big part of the fun and replay of the game, which is the reason why we have been started to work on it since day one. It should not be an issue but, if it eventually is, everyone should leave their tasks and focus on this as it is a very important part of the game. If we see that there is no time to do so, we would have to make just a basic map for the game, but this would be our last resort.

An in-depth planning has been made and in the image below there is an image of the gantt chart we have created to have a better visualization of the plan. You can also check the gantt chart here.

NEW INFORMATION: Due to management problem, GANTT will be modified depending on what we plan for each deadline

Members	Cost	Months	Total Cost
Leader	1000	4	4000
Manager	1000	4	4000
Art/Audio Lead	1000	4	4000
Code Lead	1000	4	4000
Designer	1000	4	4000
QA	1000	4	4000
UI	1000	4	4000
			28000

A 15 percent of their salary will be added for terms like Social Security, this means that the total cost of the employees will be of 32200.

In addition to this, a marketing budget should be applied, but as the social media and branding has already been created, this budget would go to assure the consistency of these (2500€), the creation of the website (2000€) and the trailer (2000€).

The total budget in this case is going to be of 38700.

The tasks that were done in each week and its corresponding deviation can be find in this excel. The record of every single task with the developer who was in charge and the time deviation can also be found there.

• Duration: 1 week.
• Points: General game idea, create planning and organization (meetings on tuesdays), team presentation.
• Postmortem: Game idea still unclear.

• Duration: 1 week.
• Points: Wiki completion.
• Postmortem: Polish game idea.

• Duration: 1 week.
• Points: Map logic, pathfinding, Map designs.
• Postmortem: Set more specific tasks.

• Duration: 1 week.
• Points: Group movement, pathfinding, buildings, camera movement.
• Postmortem: Random maps harder than thought.

• Duration: 1 week.
• Points: Collisions, improve and finish previous.
• Postmortem: Going too slow.

• Duration: 1 week.
• Points: Attack, units implementations, more buildings.
• Postmortem: Attack is much harder than thought.

• Duration: 1 week.
• Points: Main menu, settings, gold.
• Postmortem: Going too slow.

• Duration: 1 week.
• Points: Audio, pause menu, life bars, fix random map error.
• Postmortem: One defined map for the delivery, deleted random map (will be selection of different maps already created), better preparation for presentation as a group and has to be a more strategic game.

• Duration: 1 week.
• Points: Bug fixing
• Postmortem: Errors and ocasional crashes to be fixed, plan for the future deliveries and debating if to have a boss level or not.

• Duration: 1 week.
• Points: Implement new units (Gryphone Rider and Dragon) and improve map "randomization".
• Postmortem: No more units will be added as we won't reach the deadline, final objective will be rescuing both prisoners and won't implement boss or prisioners attack.

• Duration: 1 week.
• Points: Better AI, improve visual feedback, fog of war.
• Postmortem: Feedback has to be better (art and audio).

• Duration: 1 week.
• Points: Polish, add ships to base, prepare presentation.
• Postmortem: Game has to be more entertaining.

• Duration: 1 week.
• Points: Group units, polish and balance.
• Postmortem: Save and load not finished.

• Duration: 1 week.
• Points: Save and load, web and final balance.

• Duration: 1 week.
• Points: Trailer, spritsheet and presentation.

< Previous