From bce462be1d00eff86b6efa827bbb887544f13e9f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Angel=20Fern=C3=A1ndez?= Date: Mon, 12 Feb 2024 10:18:32 +0100 Subject: [PATCH] Nuevos cambios apartado 11 documentacion --- docs/src/11_technical_risks.adoc | 25 ------------------------- 1 file changed, 25 deletions(-) diff --git a/docs/src/11_technical_risks.adoc b/docs/src/11_technical_risks.adoc index b900d7ce..2fbf2f65 100644 --- a/docs/src/11_technical_risks.adoc +++ b/docs/src/11_technical_risks.adoc @@ -1,28 +1,3 @@ -ifndef::imagesdir[:imagesdir: ../images] - -[[section-technical-risks]] -== Risks and Technical Debts - - -[role="arc42help"] -**** -.Contents -A list of identified technical risks or technical debts, ordered by priority - -.Motivation -“Risk management is project management for grown-ups” (Tim Lister, Atlantic Systems Guild.) - -This should be your motto for systematic detection and evaluation of risks and technical debts in the architecture, which will be needed by management stakeholders (e.g. project managers, product owners) as part of the overall risk analysis and measurement planning. - -.Form -List of risks and/or technical debts, probably including suggested measures to minimize, mitigate or avoid risks or reduce technical debts. - - -.Further Information - -See https://docs.arc42.org/section-11/[Risks and Technical Debt] in the arc42 documentation. - -**** [options="header",cols="2,2"] |===