Mapping requirements
It may seem obvious, but we need to ensure requirements are recorded and referred to during the projects life cycle. Especially with agile projects, requirements can change through the project, and any such decisions need to be logged and updated along with the reasons why they were changed.
There are specialist tools available to help do this, however, a simple spreadsheet or document and a central, easily accessible location is sometimes all that is needed. Other options could include Microsoft Teams, Microsoft SharePoint, or Azure DevOps. The point is that we don't need expensive, specialized, architecture toolsets; we just need a log.
For each requirement, we should log who it came from, any reasoning behind decisions, and what technology choices have been made. The following is an example of something I often use:
Other information you may wish to capture includes risks, assumptions, and dependencies. However, the key point is that we should log...