Optimal Documentation in IT Projects: Enough, Connected, and Up To Date

Does documentation take too much time and seem futile? Is it always outdated, and there is never enough of it? Have you given up on keeping documentation current? It doesn't have to be this way!

It IS POSSIBLE to document reasonably and in a way that contributes to the project's progress! It IS POSSIBLE to document so that the right information is always accessible when needed! It IS POSSIBLE to keep documentation up-to-date!

The course teacher and IT analyst-architect Kaja:

Hi! I'm Kaja, IT analyst-architect with experience of over 20 years.
My strengths are analysing complex demands and offering best solutions to business processes.
I have worked in various fields, including energy, finance, telecommunications, and government. I have been involved in a range of projects, from software development to system integration. In addition, I am the founder and consultant at Liriel OÜ and a part-time teacher at ITBAC. I specialize in system analysis, architecture, and business process analysis. I have carefully considered and tested documentation methods in practice and am now ready to share this with anyone who feels overwhelmed with IT projects.

I have thought through and tested these methods in practice, and I am now ready to share them with everyone who has felt that documentation is a mess in
IT projects.

Welcome to the course that will change your understanding of documentation in IT projects!

In this course, we will discuss:

Day 1:
*Why do we document?
*Why is there a belief that documentation is unnecessary?
*Why should we actually document?
*Documentation and agile software development
*What to document?
*Which roles require what documentation?
*When is this documentation needed?
*What should be included in the document?

Day 2:
*How to document?
*What do you need from a good documentation tool?
*Common tools and their pros and cons
*Structuring a good document
*Documentation repository
*What is needed from a documentation repository?
*Common options, their pros and cons, and how to use them effectively
*Structuring and linking the documentation repository
*How to keep documentation up-to-date?
*Which documents should be retained and which should not?
*When to write documentation?
*When to add a document to the repository?

Join us and gain practical skills that will help you succeed in IT projects!
The course takes place online on two dates:
06.11 14-16 (2h)
08.11 14-16 (2h)