Included a new section and references about Risk Management.

docs/ENG-FUNDAMENTALS-CHECKLIST.md

@@ -76,6 +76,7 @@ More details on [agile development](agile-development/README.md)
 - [ ] Project advisors are invited to design reviews or asked to give feedback to the design decisions captured in documentation.
 - [ ] Discover all the reviews that the customer's processes require and plan for them.
 - [ ] Clear non-functional requirements captured (see [Non-Functional Requirements Guidance](design/design-patterns/non-functional-requirements-capture-guide.md))
+- [ ] Risks and opportunities captured (see [Risk/Opportunity Management](agile-development/advanced-topics/backlog-management/risk-management.md))
 
 More details on [design reviews](design/design-reviews/README.md)
 

docs/agile-development/advanced-topics/README.md

@@ -4,5 +4,6 @@ Documentation that help you going beyond the basics and core expectations.
 
 - [Backlog Management](./backlog-management/)
 - [Collaboration](./collaboration/)
+- [Risk Management](./risk-management/)
 - [Effective Organization](./effective-organization/)
 - [Team Agreements](./team-agreements/)

docs/agile-development/advanced-topics/backlog-management/risk-management.md

@@ -0,0 +1,29 @@
+# Risk Management
+
+Agile methodologies are conceived to be driven by risk management principles, but no methodology can eliminate all risks.
+
+## Goal
+
+Anticipation is a key aspect of software project management, involving the proactive identification and assessment of potential risks and challenges to enable effective planning and mitigation strategies.
+
+The following guidance aims to provide decision-makers with the information needed to make informed choices, understanding trade-offs, costs, and project timelines throughout the project.
+
+## General Guidance
+
+- **Identify** risks in every activity such as a planning meetings, design and code reviews, or daily standups. All team members are responsible for identifying relevant risks. 
+
+- **Assess** risks in terms of their likelihood and potential impact on the project. Use the [issues](https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/manage-issues-impediments) to report and track risks. Issues represent unplanned activities.
+
+- **Prioritize** them based on their severity and likelihood, focusing on addressing the most critical ones first.
+
+- **Mitigate** or reduce the impact and likelihood of the risks.
+
+- **Monitor** continuously to ensure the effectiveness of the migitation strategies.
+
+- Prepare **contingency plans** for high-impact risks that may still materialize.
+
+- **Comunicate and report** risks to keep all stakeholders informed.
+
+## Opportunity Management
+
+The same process can be applied to opportunities, but while risk management involves mitigating actions to decrease the likelihood of a risk, in opportunity management, you enhance actions to increase the likelihood of a positive outcome.