You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Product Documentation: case study (what was issue), business case (or mixed), system requirements specification (SRS), synonyms / acronyms
Project Documentation: traditional: project plan, resources, budget, scope, WBS... agile: _______ (agile handling of milestones)... Comparisons, when to use agile, when traditional, compare documentation for both of these.... i.e. not just process but documentation
Technical Documentation: Architecture. Technical specifications for database, API etc. Integration with other systems
Process Documentation: Company wide policies and procedures. For all teams, regardless of project.
Benefits:
For each one, an example, and why, what are the benefits (e.g how this relates to success)
Handling getting responses to no:
We don't have time for it
The client does not want to look at it
There are so many changes and we can't keep up
I don't know what documentation to write
I don't have time for 100 pages, too much
No one will read it
We don't have budget for it
Budgeting:
Budgeting - documentation...
The text was updated successfully, but these errors were encountered:
Documentation types:
Benefits:
Handling getting responses to no:
Budgeting:
The text was updated successfully, but these errors were encountered: