Session 09: Upgrading Task Management
Hi there! Welcome to this single session. It’s been nearly nine months since the last post. Once the COVID-19 pandemic hit, Cryptiquest went on a project freeze due to a change in priorities. The pandemic is not over but priorities have shifted and projects can resume.
The current focus is on the “How to Make Guides” project. Where this project last left off, I was drafting the guide and got perhaps halfway through that draft. As I was working on the project, there were lots of discovered changes and tools needed for the project management process which ballooned the timeframe estimates.
Some of those changes and tools I made but some of them were put off to the side. It was inconsistent and became a tad overwhelming. In addition to being a reconnection, this session’s goal is to tweak some things for the project in order to inject a system to properly log and plan issues.
So I have about three goals here:
- Convert the “Tasks” of the “Producing Guide Projects” document to serve more as a living document that will be updated as the project changes.
- Convert the “Issue Log” of the “Producing Guide Projects” document to a simple table to store the issue, session discovered, and level of urgency.
- Sift through the new version of the Issue Log and ensure tasks that relate to the project are inserted into the new version of the Task List.
Upgrading the Task List
For starters, let’s take a looky-loo at the Tasks list in the Producing Guide Projects document.
- Production
- Planning the guide
- Drafting the guide
- Drafting supplemental materials
- Conducting an internal review
- Creating the example guide (self test)
- Alpha Test
- Creating the test plan
- Organizing the test
- Testing waves of users
- Review
- Identifying target audience and needs
- Preparing drafts for review
- Conducting necessary reviews and edits
- Implementation
- Conducting final edits
- Creating the guides in desired formats
- Uploading guides to website and update navigation
- Beta Test
- Planning tests
- Testing waves of users
- Launch
- Assessing the target audience needs
- Creating marketing materials
- Launching to market
- Retrospective
- Reviewing the life of the project
- Listing issues
- Analyzing issues
- Recording action items
- Closure
- Identifying loose ends
- Tying up loose ends
This isn’t really a task list as much as it is a loose list of milestones – which is okay but it’s not really helpful for project management. I think the solution will look similar but will be converted to a structure that can incorporate tasks. So the phases will remain and these milestones will be converted to sound more like milestones. Tasks can then be sorted within the milestones.
But what does that structure look like? Is it an outline like before? Is it a table? Accordions? Something to keep in mind is that some discovered tasks won’t be easy to place – as in they may be somewhere in a phase or milestone but it either doesn’t matter or won’t make sense to place it until more work is complete.
I’m thinking the structure should be something like the following:
Phase Name
That looks okay. The accordions could all be closed but the one that is current. I’m not sure how nested accordions look with the current styles so I may need to update that. I’m going to convert that all now.
Okay. That will not work as you cannot nest shortcodes in WordPress. No big deal. I can just use an outline and since that would all be one “block” in WordPress, I can draft that here then transfer it.
- EXPLORATION PHASE – DONE
Milestone: Project and Product Scopes Identified
- PLAN PHASE – DONE
Milestone: Project Plan Document CreatedMilestone: Goal and Objectives IdentifiedMilestone: Target Audience IdentifiedMilestone: Milestones and Tasks ListedMilestone: Design Specs Defined
- PRODUCTION PHASE – CURRENT
- Milestone: Guide Drafted – CURRENT
- Milestone: Draft Reviewed Internally
- Milestone: Alpha Test Conducted
- REVIEW PHASE
- Milestone: Peer Reviewed
- Milestone: Prototype Created
- Milestone: Prototype Tests Conducted
- LAUNCH PHASE
- Milestone: Beta Version Implemented
- Milestone: Announcement Made
- Milestone: Markets Reached Out To
- CLOSE PHASE
- Milestone: Retrospective Complete
- Milestone: Loose Ends Tied
I think that looks good. Next, tasks need to be added:
- EXPLORATION PHASE – DONE
Milestone: Project and Product Scopes Identified
- PLAN PHASE – DONE
Milestone: Project Plan Document CreatedMilestone: Goal and Objectives IdentifiedMilestone: Target Audience IdentifiedMilestone: Milestones and Tasks ListedMilestone: Design Specs Defined
- PRODUCTION PHASE – CURRENT
- Milestone: Guide Drafted – CURRENT
- Add a step for creating a “project document” and “how to journal” in the Planning Phase
- Tease the current Plan Phase section into two different phases: Exploration Phase and Plan Phase.
- Restructure current draft into Phase > Milestone > Steps structure.
- Draft Launch Phase
- Draft Close Phase
- Draft Project Need Analysis Tool
- Draft Objectivity Repository
- Draft Alternate Task List Template
- Draft Guide Style Standards
- Draft Guide Template
- Milestone: Draft Reviewed Internally
- Analyze steps
- Milestone: Alpha Test Conducted
- Analyze steps
- Milestone: Guide Drafted – CURRENT
- REVIEW PHASE
- Milestone: Peer Reviewed
- Analyze steps
- Milestone: Prototype Created
- Analyze steps
- Milestone: Prototype Tests Conducted
- Analyze steps
- Milestone: Peer Reviewed
- LAUNCH PHASE
- Milestone: Beta Version Implemented
- Analyze steps
- Milestone: Announcement Made
- Analyze steps
- Milestone: Markets Reached Out To
- Analyze steps
- Milestone: Beta Version Implemented
- CLOSE PHASE
- Milestone: Retrospective Complete
- Analyze steps
- Milestone: Loose Ends Tied
- Analyze steps
- Milestone: Retrospective Complete
So far, so good, I think. I’m going to wait until the first draft is ready before filling out the tasks for the other phases since process changes will undoubtedly be discovered along the way.
Next up: The Issue Log. Currently it’s just a long list. It needs more data – like an issue log for tech projects. This would require a table. I don’t need a robust table, I think the basic table that’s default to WordPress will work okay. Here’s the empty version:
ID | Issue | Session Discovered | When to Address |
---|---|---|---|
1 | A need to split the first project phase into two phases: Exploration and Planning was identified. | Session 04: Drafting the Planning Phase | Immediately |
2 | There needs to be a repository for objectives. | Session 04: Drafting the Planning Phase | During the current production phase |
I think that works. This isn’t intended to track the issues. Or should it? I guess it should.
ID | Issue | Session Discovered | When to Address | Status |
---|---|---|---|---|
1 | A need to split the first project phase into two phases: Exploration and Planning was identified. | Session 04: Drafting the Planning Phase | Immediately | Slated |
2 | There needs to be a repository for objectives. | Session 04: Drafting the Planning Phase | During the current production phase | Slated |
Good enough, I guess. Now I need to add all the issue log items.
ID | Issue | Session Discovered | When to Address | Status |
---|---|---|---|---|
1 | Versioning system was never established | Session 02: Designing the Solution | As a new project | Slated |
2 | Do not have “Testing Phases” in project plan guidelines. | Session 03: Drafting the Guide | Immediately | Done |
3 | Create Need Analysis Tool and reference it in PM Guidelines | Session 04: Drafting the Planning Phase | During the current production phase | Slated |
4 | “Project Scope” needs to be split into “Product Scope” and “Project Scope” | Session 04: Drafting the Planning Phase | Immediately | Done |
5 | A sample guide will be needed for this guide | Session 04: Drafting the Planning Phase | During the current production phase | Slated |
6 | A need to split the first project phase into two phases: Exploration and Planning was identified. | Session 04: Drafting the Planning Phase | Immediately | Slated |
7 | There needs to be a repository for objectives. | Session 04: Drafting the Planning Phase | During the current production phase | Slated |
8 | This project has blown way out of scope since it’s upgrading the project planning process. | Untangling Project Conflicts | Immediately | Done |
9 | A need was identified to separate formal project content from notes. | Untangling Project Conflicts | Immediately | Done |
10 | A section is needed to identify the target audience during project planning. | Session 06: Backing Up to Scope ? | Immediately | Done |
11 | Need a “how to have a session” guide. | Session 05: Drafting the Planning Phase (Again?) | During the current production phase | Slated |
12 | Need a “Styling your guide” guide. | Session 05: Drafting the Planning Phase (Again?) | During the current production phase | Slated |
13 | Need a section or guide (or section in the “how to have a session” guide) about PM journaling. | Session 07: Drafting Your Guide | Immediately | Slated |
14 | A section is needed in project planning for creating the project document | Session 07: Drafting Your Guide | Immediately | Slated |
15 | Need to add a Target Audience section to the project document | Session 08: Drafting the Review and Prototype Phases | Immediately | Done |
16 | Upgrade Tasks in the PM Document | Session 09: Upgrading Task Management | Immediately | Done |
17 | Upgrade Issue Log in the PM Document | Session 09: Upgrading Task Management | Immediately | Done |
Okay. I think that’s good. I will implement the new issue log and the new task list now. The Action Items for this session are going to be things I already addressed here but haven’t been added to an Action Item list yet.
It looks like the next session will be about adding instructions for journaling and creating project documentation. Should be fun.
See you there!
Action Items
- Convert the “Tasks” of the “Producing Guide Projects” document to serve more as a living document that will be updated as the project changes.
- Convert the “Issue Log” of the “Producing Guide Projects” document to a simple table to store the issue, session discovered, and level of urgency.