Session 02: Deliverables

Hi. Welcome to this session of the project log for Zones – a mechanic for the CQ StoryHammer game system. Th goals, objectives, and tools for measuring those objectives have already been generated. Today, I’m going to take those initial elements and turn them into deliverables.

Here is a reminder of those elements:

Goal: By the end of this project, I will have a product that I can use for testing future mechanics of CQ StoryHammer.

Objective 1: The product needs to be setting and mission-agnostic.
Objective 2: The product needs to be made with a two-week time-frame for major upgrade.
Objective 3: The product needs to enable testing of zone configurations.
Objective 4: The product needs to follow Cryptiquest Guidelines for Inclusive Physical Components.
Objective 5: The project needs to follow Cryptiquest Guidelines for Intellectual Property Protections.

Tool 1: Definition of Zones
Tool 2: List of Zone Configurations for Testing
Tool 3: Cryptiquest Guidelines for Inclusive Physical Components
Tool 4: Cryptiquest Guidelines for Intellectual Property Protections

I’ve been doing this enough now to know that in addition to my claim that there is a 6 phase structure (Ideate > Plan > Design > Produce > Refine > Launch), there are three super-phases that deliniate those phases: Pre-production (Ideate and Plan), Production (Design, Produce, and Refine) and Post-Production (Launch). It seems that the Pre and Post production super-phases have standard elements:

Pre-Production

1. Goal (done)
2. List of objectives (done)
3. Tools for measuring objectives (done)
4. List of deliverables (in progress)
5. Steps and timelines for each deliverable

Post-Production

1. Launch plan
2. Supplemental materials
3. Launch

So we need to come up with deliverables for the production phase. We have the tools – which will each be their own project outside of this project.

1. Definition of Zones
2. List of Zone Configurations for Testing
3. Cryptiquest Guidelines for Inclusive Physical Components
4. Cryptiquest Guideline for Intellectual Property Protections

Once those are complete, production on this project can continue:

1. Component Design
2. Component Production Plan
3. Template Design
4. Component Drafts
5. Component Draft Tests
6. Component Refinement
7. Component Refined Drafts
8. Component Refined Tests
9. Component Finals

That seems good for the components. There may be a need for instructions though, which I will lift from a previously established project:

1. First draft of rules
2. Final draft of rules
3. Advice from peers
4. Final version of the rules

I think that concludes the Deliverables for this project. Here is the list:

1. Goal (done)
2. List of objectives (done)
3. Tools for measuring objectives (done)
4. List of deliverables (in progress)
5. Steps and timelines for each deliverable
6. Definition of Zones
7. List of Zone Configurations for Testing
8. Cryptiquest Guidelines for Inclusive Physical Components
9. Cryptiquest Guideline for Intellectual Property Protections
10. Component Design
11. Component Production Plan
12. Template Design
13. Component Drafts
14. Component Draft Tests
15. Component Refinement
16. Component Refined Drafts
17. Component Refined Tests
18. Component Finals
19. First draft of rules
20. Final draft of rules
21. Advice from peers
22. Final version of the rules
23. Launch plan
24. Supplemental materials
25. Launch

Phew! That seems like a lot of deliverables for something that was already in progress, though admittedly, a lot of these steps were skipped or not considered which is why this project has stalled. And seeing how important this project is to the rest of the CQ StoryHammer projects, it’s important to get this right.

Next time, I’ll cover the Steps and Timelines for these deliverables.