| A | B | C | D | E | |
|---|---|---|---|---|---|
1 | Overall Objective for project: Produce how-tos out of the effective practices in HfLA community | ||||
2 | Priority Order | Name for Milestone | Objective | What is needed in order to achieve | Labels in milestones |
3 | 1 | Compliance | Make sure that we are not violating any licences or regulations | Document where we have gotten images, Privacy Policy for the landing page | feature: administrative |
4 | 2 | Security | Secure all tokens, passwords, access necessary | 1Password | feature: administrative |
5 | 3 | Project Management | Keep the Project Organized and Efficient | Github maintainance, | feature: board/GitHub maintenance, feature: administrative |
6 | 4 | New Guide Instructions | Have easy-to-follow instructions on how to create new guides | project landing page, basic guide templates stable (how to: write a guide, insert screenshots and images, templates: guide, image) | feature: guidance p-feature: landing page |
7 | 5 | Format Standardization | Standardize existing guides into a consistent format and style | editing of all the guides to match the format once stable, confirm completion by cross checking the folders and the issues. | feature: cleanup guide |
8 | 6 | CoP Coordination | Work with the HfLA Communities of Practice to support their guide creation efforts and needs | interviews to determine their current process and how the guides fit into their CoP roadmap and sentiment about guides, tracker, project landing page | feature: workflow, feature: trackers, feature: user research, p-feature: landing page |
9 | 7 | Tracker Requirements | Define requirement for tracker | tracker | feature: trackers |
10 | 8 | Document Processes | Gather requirements for procedures and systems to automate and accelerate the production of guides | Draft landing page that defines each step of ideation to publication | feature: workflow p-feature: wiki |
11 | 9 | Automate Processes | Create Automations | GitHub and other automations | feature: board/GitHub maintenance, feature: workflow |
12 | 10 | Feedback Instructions | Have easy-to-follow instructions on how to give feedback/comments on guides in development | published landing page | feature: guidance, p-feature: landing page |
13 | 11 | Revision Instructions | Have easy-to-follow instructions on how to provide edits for finished guides | project landing page, a defined path for guide edits | feature: guidance, feature: workflow, p-feature: landing page |
14 | 12 | Publication | Publish the guides on the hackforla.org website | stable guide templates, 10 finished guides | feature: guidance, feature: conversion-ready guide |
15 | 13 | Credit | Serve as a platform/portfolio for guides authors to receive credit internally and externally for their work | credit on the guide with their linkedin/and or github, ability to link to the guide from their linkedin (publishing on the website) | feature: evangelize |
16 | 14 | Incent creation/completion | Incentivize people to make and complete guides | research into the motivations of the people who created guides already (and that those that have not) and how they want to be credited or otherwise incentivized, tracker, project landing page, credits | feature: evangelize, feature: trackers, p-feature: landing page, feature: user research |
17 | 15 | Incent draft feedback/editing | Incentivize people to give feedback and edit draft and completed guides | research into the motivations of people who have edit guides (and those that have not). | feature: evangelize, feature: user research |
18 | 16 | Incent publication feedback/editing | Incentivize people to give feedback and edit existing guides (published) | research into the motivations of people who have edit guides (and those that have not). | feature: evangelize, feature: user research |