Today's lecture notes - Documentation

To date:

blogs
scribbles
whiteboard
photos
sms
comments on code
project plan
SWOT analysis
email
twitter
code
concepts, sketches, etc
prototypes


What else needed?

iterations of code/files/etc
user feedback
user documentation, manuals, help files, etc
final report for client
portfolio
reflective report (internal)


Why & When Documentation?

--pre-project
project proposal, tender documentation
advertising
(for getting job/clients)
Concepts sketches
SWOT analysis

--early in project
project plan
contract
concepts, sketches, etc
digital prototype

--during project proper
user feedback
iterations of the code/files/etc

--end of project
final report to clients
user documentation, manuals, help files, etc
the code itself

--post project
reflective report (internal)
portfolio
email within project group
communication with client(s)
blog

-->final step: archive everything



**The project actually starts when the contract is signed (start charging the fee). Everything done before is preproject work. SWOT is a consideriation of issues before agreeing on signature.
Clients are more focused on avoiding a delay in the release of their project.
**Contracts can be renegotiated
**project plan written early and don't changed without signing off
** time tracking is an excellent resource, to bring forward to other projects, to make informed decisions, etc.