2020
DOI: 10.2478/acss-2020-0012
|View full text |Cite
|
Sign up to set email alerts
|

Survey on Risk Classification in Agile Software Development Projects in Latvia

Abstract: Software development method, which does not have any faults or gaps in project implementation, has not been elaborated so far. Due to this reason, the authors have decided to perform this study to make it easier for the companies, which use one of the agile development methods, to better foresee potential risks and to deal with their consequences. The aim of the research is to identify and classify risks in agile software development methods and the related projects based on the obtained survey data. To achiev… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2023
2023
2024
2024

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 5 publications
0
2
0
Order By: Relevance
“…Daily Standup Meetings [10,28] Sprint Planning [10,3,23,11] Brainstorming [23,22,9] Checklist [22] Weekly Sprint Meetings [16] Increment [17] Prototype [17] Product backlog refinement meeting [17,28,4] Weekly risk meeting [17] Technical specification [17] Risk Identification Meetings [23] Sprint backlog [28] Sprint review [14,3,4,18] Sprint Retrospective [3]…”
Section: Practices Referencesmentioning
confidence: 99%
See 1 more Smart Citation
“…Daily Standup Meetings [10,28] Sprint Planning [10,3,23,11] Brainstorming [23,22,9] Checklist [22] Weekly Sprint Meetings [16] Increment [17] Prototype [17] Product backlog refinement meeting [17,28,4] Weekly risk meeting [17] Technical specification [17] Risk Identification Meetings [23] Sprint backlog [28] Sprint review [14,3,4,18] Sprint Retrospective [3]…”
Section: Practices Referencesmentioning
confidence: 99%
“…Creative teams with diversity in expertise are the key to success in brainstorming [17]. However, they must give up intentional ignorance for team collaboration to be effective [18]. As a result, risk identification assistance tools must consider the above constraints and facilitate communication and collaboration among participants [19][20][21][22][23].…”
Section: Introductionmentioning
confidence: 99%