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

Value creation and capture: a model of the software development process

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0

Year Published

2009
2009
2014
2014

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 20 publications
(8 citation statements)
references
References 5 publications
0
8
0
Order By: Relevance
“…Furthermore, publications in agile SE converge on that agile methods get "more done with less" [10], [15], [20]. More specifically, in our earlier systematic review [17], we found that agile literature sources agree that business value is considered the key requirements prioritization criterion in most agile projects.…”
Section: Related Workmentioning
confidence: 68%
“…Furthermore, publications in agile SE converge on that agile methods get "more done with less" [10], [15], [20]. More specifically, in our earlier systematic review [17], we found that agile literature sources agree that business value is considered the key requirements prioritization criterion in most agile projects.…”
Section: Related Workmentioning
confidence: 68%
“…However after a certain moment in time it would also start to accelerate at a faster rate, since going beyond a certain point in time without a new version would test customers' patience. Th ese ideas are in fact confi rmed by the real world data [14] and thus this change will be a good candidate for an improved model.…”
Section: Motivationmentioning
confidence: 89%
“…Traditionally, software development is formulated with metrics that view projects that are structured in sequences of stages [2] , [37] . Financial frameworks and models do exist for Agile, however they need to be commonly embraced if Agile is to become more widely integrated into business strategy [38] .…”
Section: Discussionmentioning
confidence: 99%