2018
DOI: 10.1109/ms.2018.2141017
|View full text |Cite
|
Sign up to set email alerts
|

Agility, Risk, and Uncertainty, Part 2: How Risk Impacts Agile Architecture

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
6
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(6 citation statements)
references
References 5 publications
0
6
0
Order By: Relevance
“…The architect takes into account the temporal dimension of architecturally important events (Poort, 2016); assesses the architectural impact on risk (Martini & Bosch, 2016;Poort, 2016); assesses the technical risk of developing complex and critical systems (Waterman, 2018b); demonstrates the benefits of new technologies by designing an executable prototype (Erder & Pureur, 2016); understands that erosion of architecture can lead to technical bankruptcy (Sturtevant, 2017); understands and maps the essencial characteristics of development process selection to the context (Ozkaya, 2019).…”
Section: Risk and Time Dimension Managementmentioning
confidence: 99%
“…The architect takes into account the temporal dimension of architecturally important events (Poort, 2016); assesses the architectural impact on risk (Martini & Bosch, 2016;Poort, 2016); assesses the technical risk of developing complex and critical systems (Waterman, 2018b); demonstrates the benefits of new technologies by designing an executable prototype (Erder & Pureur, 2016); understands that erosion of architecture can lead to technical bankruptcy (Sturtevant, 2017); understands and maps the essencial characteristics of development process selection to the context (Ozkaya, 2019).…”
Section: Risk and Time Dimension Managementmentioning
confidence: 99%
“…The architect takes into account the temporal dimension of architecturally important events (Poort, 2016); assesses the architectural impact on risk (Martini & Bosch, 2016;Poort, 2016); assesses the technical risk of developing complex and critical systems (Waterman, 2018b); demonstrates the benefits of new technologies by designing an executable prototype (Erder & Pureur, 2016); understands that erosion of architecture can lead to technical bankruptcy (Sturtevant, 2017); understand and map the essential characteristics of development process selection to the context (Ozkaya, 2019).…”
Section: Risk and Time Dimension Managementmentioning
confidence: 99%
“…The architect for the decisions the team makes is consistent throughout the system (Madison, 2010;Buschmann, 2012); influences design decisions that affect the whole system (Buschmann, 2012); protects the conceptual integrity of product architecture and design (Buschmann, 2012;Poort, 2014;Erder & Pureur, 2016); manages technical debt (Zimmermann, 2016); reduces risk to a level that's satisfactory to the team and stakeholders (Waterman, 2018b); balances between risk and agility (Waterman, 2018b); designs for failure in which, instead of preventing failures (reliability), learn how to deal with failures (resilience) (Shahin et al, 2019).…”
Section: Preserving System Integritymentioning
confidence: 99%
“…The architect ensures that team's decisions are consistent throughout the system (Madison, 2010;Buschmann, 2012); influences design decisions that affect the whole system (Buschmann, 2012); protects the conceptual integrity of product architecture and design (Buschmann, 2012;Poort, 2014;Erder & Pureur, 2016); manages technical debt (Zimmermann, 2016); reduces risk to a level that's satisfactory to the team and stakeholders (Waterman, 2018b); balances between risk and agility (Waterman, 2018b); designs for failure in which, instead of preventing failures (reliability), learn how to deal with failures (resilience) (Shahin et al, 2019).…”
Section: Additional Readingmentioning
confidence: 99%
“…The architect has empathy for users and works closely with users -the "follow-me-home" technique (Mirakhorli & Cleland-Huang, 2013); receives real requests from users feedback (Mirakhorli & Cleland-Huang, 2013); assesses team's and customer's risk tolerance (Waterman, 2018b); balances customer demands, with a focus on their delivery (Erder & Pureur, 2016); removes artificial barriers to delivering better, faster, cheaper software to the users (Ozkaya, 2019).…”
Section: Additional Readingmentioning
confidence: 99%