cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
441
Views
0
Helpful
0
Replies

Documenting projects/Reporting

Hi there,

I am looking at finding what is the best "simple" way to structure work and especially work/changes brought across a network. A simple way to provide:

1) plan structure of task to be completed/organise/troubleshooting

2) report simple list of completed task/work

3) report full project and recommendations for improvement

4) technical documentation for technical team to access and edit

Be it building a new system, but even better when bringing changes in to an existent system when a lot of reverse engineer was needed as system underwent a lot of changes in the last 5 years but nobody documented anything.

In a summary, if you may recommend template/links/ideas on how to document:

- Situation analysis of problems/risks > solutions offered, potentially in multiple steps

- Reverse engineering approach/findings/methods/troubleshooting/analysis/corrective actions-solutions

- Documenting per subgroups (WAN/LAN/WLAN/DEVICES/CLIENTS/LOGIC) the work/tasks completed

- Any suggestions on documentation needed and helpful also to plan the work to be done and reporting.

Thank you so much for any suggestions!

 

 

0 Replies 0