![]() Added organizational logos/headers to reports.Created a report for RRICAD items with status of “Resolved”.Red: due within 5 days, Orange: due within 15 days, Yellow: Due within 30 days) Added conditional color formatting to due dates (Ex.Some other settings that were changed later included: That is essentially all of the major settings that needed to be made in order to start using the database to store and track RRICAD items. Then, I edited the category selection criteria to include risks, requirements, issues, changes, action items, and decisions. Next, I changed all titles containing “Issue” in the forms and reports by changing the caption within the Property Sheet. The first task was to replace all report/form/table titles from “Issue” to “RRICAD”. The template is located under Lists when creating a new Access file, with the option of a desktop database or an app, which can be launched on a SharePoint. To track the project RRICAD items, the issue tracking template was the best place to start. Either way, it is still important to understand how Access uses relationships before getting too deep into it. I prefer to start with an available template to avoid having to create the tables and relationships between the data. If you have never used Access before, at first glance it can be quite intimidating, especially if starting with a blank database. I started with the issue tracking template that was already available and with some minor customization met the desired goal. However, it’s rare to find one that will meet every requirement, so the best bet, in my opinion, is to develop a tool tailored specifically to a project that meets all requirements and excludes any additional features that may not be necessary.įor this, I used Microsoft Access and created a relational database to house the data. ![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |