Skip to content

Latest commit

 

History

History
24 lines (16 loc) · 945 Bytes

project-journal.md

File metadata and controls

24 lines (16 loc) · 945 Bytes

Project Journal

What is a Technical Narrative?

A Technical Narrative is a document that shows the incremental history of the research and development you undertook during your project.

For our purpose we'll call our Technical Narrative a "Project Journal".

What should be written in a Project Journal?

  • A hypothesis for the technical solution
  • Outline the current limitations eg. Knowledge, Budget, Time
  • The documentation and education resources you used
  • The challenges you faces
  • The outcomes you were able to achieve (success or failures)
  • The evolution of your architectual diagram

Why can't I just build the project, why bother with a Project Journal?

The process you undertook to build your Cloud Project is equal or more important then the outcome of your Cloud Project.

  • A project journal will demostrate strong documentation skills
  • A project journal will help you recall and
  • A project journal will prove