2004
DOI: 10.1007/978-3-540-27777-4_6
|View full text |Cite
|
Sign up to set email alerts
|

An Agile Customer-Centered Method: Rapid Contextual Design

Abstract: Abstract. Agile methods have proven their worth in keeping a development team focused on producing high-quality code quickly. But these methods generally have little to say about how to incorporate user-centered design techniques. Also the question has been raised whether agile methods can scale up to larger systems design. In this paper we show how one user-centered design method, Contextual Design (CD), forms a natural fit with agile methods and recount our experience with such combined projects.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
136
0
7

Year Published

2006
2006
2022
2022

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 134 publications
(143 citation statements)
references
References 6 publications
0
136
0
7
Order By: Relevance
“…Next, we present some of the studies that highlight the importance of artifacts as an important channel of communication between different areas [23]. Beyer, Holtzblatt and Baker [21] state that, by using conceptual diagrams and mockups, team communication can be facilitated. In their study, task models were used to show the scope of issues from all customers to the entire team.…”
Section: A Artifacts On Agile User-centered Designmentioning
confidence: 99%
See 1 more Smart Citation
“…Next, we present some of the studies that highlight the importance of artifacts as an important channel of communication between different areas [23]. Beyer, Holtzblatt and Baker [21] state that, by using conceptual diagrams and mockups, team communication can be facilitated. In their study, task models were used to show the scope of issues from all customers to the entire team.…”
Section: A Artifacts On Agile User-centered Designmentioning
confidence: 99%
“…Pre-Planning [27], [38], Pre Release Planning [27], Span Plan [22], and Plan Parallel Iteration [46] were also considered as Planning since their main goal was to define what would integrate an iteration. For the planning period, UI design and user stories are delivered to the development team and they can use them to estimate how much effort they need for the next iteration [21]. Cards are the most used artifact on planning event, as seen in Figure 2.…”
Section: B Events In Which Artifacts Are Usedmentioning
confidence: 99%
“…Contextual inquiry [30] With modifications Context inquiry [16] As Is Contextual inquiry [35] As Is Contextual Inquiry [36] As Is…”
Section: Contextual Interviewsmentioning
confidence: 99%
“…Task Scenarios Task Scenarios Usability user stories [30] With modifications Usability user stories [31] As Is Usability user stories [43] With modifications Task Sorting…”
Section: Develop Product Conceptmentioning
confidence: 99%
See 1 more Smart Citation