Session 03: Deliverables
Welcome to the third session in the Online Notes project where I’m trying to establish a system for posting project notes online. The goal of this session is to identify the deliverables for the project.
This is where the project stands after the last session:
Goal: Establish a system for writing notes and logs for Cryptiquest projects online.
Objective 1: The system must connect to a populated online community with the intention of facilitating discussion about the posts.
Objective 2: The system must be able to accommodate advanced formatting, including lists, indents, an tables.
Objective 3: The system must allow session-based posts.
Objective 4: The system must feature a way for posts to be linked together under the same project.
Objective 5: Ensure the system allows for Cryptiquest, LLC to maintain rights to all content posted for and by Cryptiquest, LLC.
Guideline 1: Content generated through this system shouldn’t be trite or inconsistent.
Guideline 2: Content generated through this system shouldn’t be confusing or boring.
Guideline 3: Content generated through this system shouldn’t contain “off switches”.
Okay. So: deliverables. Starting with the planning phase (you can learn more about Cryptiquest project phases here) we know that we should create the following standard deliverables:
- Goal (done)
- List of objectives and guidelines (done)
- Tools for measuring objectives (done)
- List of deliverables (in progress)
- Steps and timelines for each deliverable
Next is the design phase. I’ll have to do some research here, specifically, I need to look into what types of online tools already exist to see if anything out there matches my needs. It is possible that my list of project phases needs to be updated to include a “research phase” in with the design phase though I suppose that this research part is just the “ideation phase” of a sub-project of designing the system? I don’t know but it does seem to make sense.
Anyway, I need to conduct research resulting in data collection, then I need to analyze that data and design the system.
- List of available online tools for system
- Analysis of using online tools for system
- Design of system
For the production phase, I need to implement the system and add content to the system (I’ve been writing project sessions [like the one you are reading] offline while waiting for this system to exist). Once the content is up-to-date, then the project will be considered finished (I think) as that should prove its usefulness, yes?
- Implement the system
- Add content to the system (up until it is up-to-date)
The refinement phase will mostly happen simultaneously with the production phase since if the system won’t work while implementing, it will need to be adapted and changed. But there may come a point where the system is working enough to add content but needs tweaking to get it to look or function perfectly. That might look the following:
- Analysis of system
- List of changes
- Implement changes
The launch phase for this project should be baked into the system was the system needs to be designed with an intention of facilitating discussion about the posts. However, this is a major upgrade for Cryptiquest, so making a press release about it could jumpstart the discussion and also serve as an invitation for such discussions.
- Launch plan
- Supplemental materials
Okay. I think that’s a good start. Like always, I can’t count on this being a comprehensive list and will have to adapt as I learn new things. Here’s the tally:
- Goal (done)
- List of objectives and guidelines (done)
- Tools for measuring objectives (done)
- List of deliverables (done)
- Steps and timelines for each deliverable
- List of available online tools for system
- Analysis of using online tools for system
- Design of system
- Implement the system
- Add content to the system (up until it is up-to-date)
- Analysis of system
- List of changes
- Implement changes
- Launch plan
- Supplemental materials
During the next session, I’ll try to establish steps for each deliverable and a timeframe, resulting in an abstract work schedule.