3 ms·
> Just having the system continually documented In my experience this is the hardest part. Can't count how many times my team started documenting and then slow
by arthur_sav 5y ago
> Just having the system continually documented
In my experience this is the hardest part. Can't count how many times my team started documenting and then slowly, for one or the other reason, the documentation became outdated.
The cycle is: Meetings for communication -> becomes too cumbersome and time consuming -> implement policy to document things -> everyone start documenting (for a month or two) -> docs are not up-to-date because people forget/leave etc.. -> go back to meetings
- castlecrasher2 5y agoIn my experience it's a culture thing. When I learned to love Jira/Confluence was when the product team conducted meetings directly from Jira and during task discussion almost always asked us if tasks and documentation were done. It could have been really annoying but the product lead was extremely empathetic and that could be felt in any task discussion, and his attitude made me want to do it instead of making it feel like busy work like it has in other companies.
- albrewer 5y agoThis is supposed to be enforced in code review or with other team practices / processes.