Development Cycle Plan - ljackl/BubbleTrouble GitHub Wiki

Development Cycle for Bubble Trouble

Chosen style: Waterfall

Justification:
The chosen development cycle for this project was decided on being Waterfall for a number of reasons.

1. The disadvantage of "changing customer requirements" doesn't impact us as this project is 'in-house' therefore unlikely to change
2. The requirements for this project are very clear and not easy to misinterpret because this is a re-imagining of an existing project, meaning if a requirement is ambiguous there is a reference point.
3. Due to limited time, there probably isn't going to have more than one iteration.
4. A waterfall approach resembles the game development life cycle the most and as the team is developing a game it is deemed the best approach.

Waterfall Stages:

• Requirements
  • Vision Statement
  • Features and Functionality
• Design
  • Game Screens and Flow
  • User Interface
  • Gameplay
• Implementation (Current stage)
• Verification
• Deployment
• Maintenance

Waterfall Project Plan