Share the documentation in your work log in Teams.
I put it on my files on teams under my name. I can move it if that doesn’t work. I saved it as a PDF.
Reflect on this experience on a blog post in your portfolio site: after both reading and writing documentation, what do you think is necessary to create good documentation? What documentation will you and your project lead need to create for your Vivero project – and what steps do you need to take to make this happen?
I am miraculously have been working on my project documentation for the past several weeks, so this is awesome timing for me 🙂 . Between this training and my own work on documentation, I have learned that documentation is a lot of work. To create good documentation, I think that different projects require different things. My project last year was very visual, so I made a presentation that went through the different visual tools I utilized and how I created or used them. I wanted it to be more like a “showcase” because I didn’t feel like it made sense if I didn’t show visuals. For this year’s project, my documentation is mostly a Black and White, step-by-step list of goals, steps, and how-tos. It is really important that our project this year has good documentation that could teach someone else how to do it it continuity is a huge goal. So, we need to create very teachable documentation! I will just keep trying to do my documentation AS we do the project. It’s hard to do that sometimes because I often change things and don’t want to document it too soon through all my trials.
Leave a Reply