Headers
- Chapters
-
Prototype [1/7] Introduction
-
0
0
-
0
-
First, a bit of theory:
let's compare the WATERFALL & AGILE development processes and pick what could work for us.
As we have a hard deadline with limited time, we will use the WATERFALL process.
It works well with the production chapters introduced earlier:
We will also pick great practices from other methodologies such as AGILE and CONTINUOUS DELIVERY.
As our schedule is tight, we need to maintain a workable & playable version to test regularly our software and iterate fast: IDEATE | PROTOTYPE | TEST.
To build the PROTOTYPE, we will follow 6 steps. Can you please re-arrange the process in the right order? Drag and drop in the correct column the process objectives [boxes with a green border ◻ ].
1.
2. PLAN
3. DEV
4. ART & CONTENT
5.
6. REVIEW
Process update incomplete. Please iterate.
Well done! We will explain each step in the next missions. First, we need to build a FEATURE LIST.
The prototype feature list needs to represent the CORE EXPERIENCE of the game: the key functionalities.
Ready?
