2007
DOI: 10.1007/978-3-540-73105-4_7
|View full text |Cite
|
Sign up to set email alerts
|

Incorporating User Centered Requirement Engineering into Agile Software Development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
26
0
4

Year Published

2009
2009
2017
2017

Publication Types

Select...
5
1
1

Relationship

1
6

Authors

Journals

citations
Cited by 41 publications
(34 citation statements)
references
References 2 publications
0
26
0
4
Order By: Relevance
“…The type of adoption (as is, with modifications) depends on the particular features and resources of each project. Contextual analysis [32] As Is Context of use [34] As Is Contexts of use [31] As Is…”
Section: Resultsmentioning
confidence: 99%
See 3 more Smart Citations
“…The type of adoption (as is, with modifications) depends on the particular features and resources of each project. Contextual analysis [32] As Is Context of use [34] As Is Contexts of use [31] As Is…”
Section: Resultsmentioning
confidence: 99%
“…Mock-ups and prototypes [34] As As mentioned above, we found that some usability techniques are being adopted thanks to adaptations. For example, the HCI discipline stipulates that, in order to apply contextual inquiry, all the people involved in applying the technique (developers and users) must have previous training and the team must participate in the multidisciplinary meeting from beginning to end.…”
Section: Scripted Prototypesmentioning
confidence: 97%
See 2 more Smart Citations
“…They have a list of features and/or tasks made by experts that should be implemented by the end of the project. These requirements are collected in the Product Backlog (Duchting et al, 2007). Team members estimate the completion time for each task.…”
mentioning
confidence: 99%