Coordinate between Communities of Practice on Guide Making

[ExperimentsInHonesty]

Overview

We need to have consistencies across all communities of practice for guide creation and instruction on guide creation.

Related Issues

Review a Guide: How Hack for LA uses Kanban for Project Management Create a Guide/Template: Agile Development/Scrum/Kanban hackforla/engineering#15 - unclear why we need a guide about Kanban for engineers, we should revise the one we have made for pms to be for everyone.

Address the following issues by defining Actions to be taken

• [ ] Review the How to write a Guide and figure out how to revise the guidance about headers and integrate the link to the How to Add Screenshots and Graphics in Guides in the appropriate location.
• [ ] Identify the differences between the guides templates and revise to make sure that all guide templates are focused on people gathering examples from teams first before outside research
• [ ] Audit all guide issues that are already created
  • [ ] if not assigned: revise instructions
  • [ ] if assigned: review and see if they understood that they need to survey existing teams first and annotate if necessary.

Resources/Instructions

How to Write a Guide How to Add Screenshots and Graphics in Guides - should be a google doc, is a word doc. Example of issue not using the same guidelines as PM guides: https://github.com/hackforla/UI-UX/issues/22

Guide Creation Issue Templates:

• Product Management
• UI/UX
• Engineering
• Data Science
• Fundraising
• Marketing

[daniellex0]

Updated How to Add Screenshots and Graphics in Guides (now in Google Doc format, I'm not sure why the other one was Word)

Updated Guide Graphics and Annotations slide deck

The bottom of the Guide to PM Documentation has also been updated with links to this documentation^

The links may need to be turned into links to PDF's since they are currently saved in the UI/UX CoP drive, so PM's may not be able to see the linked docs at the moment.