2016
DOI: 10.1016/j.jss.2016.05.001
|View full text |Cite
|
Sign up to set email alerts
|

Agile methods in embedded system development: Multiple-case study of three industrial cases

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

2
21
0
5

Year Published

2016
2016
2022
2022

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 24 publications
(29 citation statements)
references
References 11 publications
2
21
0
5
Order By: Relevance
“…In space system development and in embedded system development, there is a need to carefully select or tailor the practices. This was also noted in our recent study [38]. A case study can enhance the knowledge over the challenges and benefits of agile methods in embedded space system development.…”
Section: Embedded System Developmentsupporting
confidence: 75%
“…In space system development and in embedded system development, there is a need to carefully select or tailor the practices. This was also noted in our recent study [38]. A case study can enhance the knowledge over the challenges and benefits of agile methods in embedded space system development.…”
Section: Embedded System Developmentsupporting
confidence: 75%
“…The next disadvantage is that, particularly, in the space industry the traditional plan‐driven approach are typically long lead times on hardware development . A study done by Watson, Neeley, and Blackburn at NASA found that 2 of the major drivers of launch vehicle cost was production of development hardware and development test cost.…”
Section: Plan‐driven Life‐cycle Approachmentioning
confidence: 99%
“…Many systems engineers who follow an Agile SE approach misinterpret the principles of Agile SE as advocating for less process control and less documentation . Since the Agile SE approach emphasizes enhanced teamwork and communication, it often leads to a diminished need for documentation . Agile SE practitioners may interpret this as documentation is not needed.…”
Section: Agile Se Life‐cycle Approachmentioning
confidence: 99%
“…Context method guidance [24] procedures, artifacts, roles [16] [14] Recently, some authors began to describe cases of the introduction of Scrum to non-traditional contexts. For example, Könnölä et al (2016) report on successful adoption of Scrum to embedded system development [24].…”
Section: Contextmentioning
confidence: 99%
“…For example, Könnölä et al (2016) report on successful adoption of Scrum to embedded system development [24]. They provide method guidance highlighting the specific needs of this context, such as longer iteration cycle of hardware development compared to software development.…”
Section: Contextmentioning
confidence: 99%