Like I mentioned before, there are many software solutions available that are great for managing different types of project data. In this case, RICA was extended to RRICAD ( Risks, Requirements, Issues, Changes, Action items, Decisions). So, the goal became to develop a single, centralized database to manage the project RICA structures. Lastly, action items were being recorded in meeting minutes and stored away in the configuration management database, but were never formally assigned or followed up on during the next meeting. Instead, they were parsed out in various briefs, white papers, meeting minutes, etc. Issues, changes, and decisions were not being tracked in any specific location. Requirements were being tracked in separate spreadsheets, independent of one another based on each functional team on the project. Risks were being tracked and updated in an online repository. I realized that the project I was working on had six things that were being tracked or updated regularly. I started thinking about those two points and eventually morphed them into a single goal. Work to keep all work centralized and easy to access from one access point of reference.Work to keep tasks, risks, issues, changes, actions, documents, updates, hours, and assignees always associated to the project or operations tracking unit.Of the 41 slides in the webinar, two points stood out:
![sample microsoft access project database sample microsoft access project database](https://www.contrapositionmagazine.com/wp-content/uploads/2020/01/microsoft-access-crm-database-template-free.jpg)
I had considered this for a while as the potential problem area on past projects, but it wasn’t until I watched a webinar called 5 Project Management Practices You Can’t Live Withoutthat I began actively seeking ways to become more efficient and productive. In Managing Risks with Microsoft Project, I mentioned that many projects utilize multiple separate data repositories to store various work products and how doing so can be a challenge.