|
ABSTRACT
If designing and developing optimal products, services, and information requires clarity and audience awareness, then developing ways to acquire customer input is a critical piece in the best development workflow solutions [43]. Seeking direct input from customers and learning how they use a product are the most effective methods for generating ideas for enhancements and innovations to the technical content that supports a product, as well as to the product itself [21]. Taking the steps to create opportunities for customer feedback enables direct customer input and establishes the proactive best practice of demonstrating to the customer that they are a top priority in the product development focus [34]. While there may not be a fixed agenda for an optimal customer meeting, there may, in fact, be a set of topics for discussion that comprise a set of best practices for gaining customer input for the user assistance [45]. Customer input helps provide requests for change and thus aids in managing change, raising the importance of a change and requirements management system [34, 52]. A change and requirements management system is even more critical in the context of application lifecycle management and globally distributed development [27, 49, 50, 55]. Managing relationships with customers leads to a two-way path for collaboration, both for helping customers solve their problems and for a company to enhance its products and overall success [26, 28].
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
 |
1
|
|
| |
2
|
|
| |
3
|
|
| |
4
|
|
| |
5
|
Carmel, E. Global Software Teams. Prentice Hall, 1999.
|
| |
6
|
|
| |
7
|
|
| |
8
|
Benjamin, R. and Levinson, E. (1993). "A framework for managing IT-enabled change," Sloan Management Review, Vol.34, No.4, pp. 23--33.
|
| |
9
|
|
| |
10
|
Booch, G. and Brown, A. Collaborative Development Environments. Advances in Computers Vol. 59, Academic Press, August 2003.
|
| |
11
|
|
 |
12
|
|
| |
13
|
Currie, Wendy, and Hlupic, Vlatka, R. and R. Murray. 1993. Getting ready for strategic change: surviving business process redesign. Information Systems Management: Summer: 23--29.
|
 |
14
|
|
| |
15
|
|
| |
16
|
|
| |
17
|
Davids, M. (1999). "How to avoid the 10 biggest mistakes in CRM," Journal of Business Strategy, Vol.20, No.6, pp. 22--11.
|
 |
18
|
|
| |
19
|
Duck, Jeanie D., Managing Change: The Art of Balancing, Harvard Business Review, Nov-Dec, 1993.
|
| |
20
|
Garvin, David A., Building a Learning Organization, Harvard Business Review, Jul-Aug, 1993.
|
 |
21
|
Karen E. Goeller, Zen and the art of learning support: combining documentation, training, and online help functions for a unique organizational approach to information development, Proceedings of the 12th annual international conference on Systems documentation: technical communications at the great divide, p.119-125, October 02-05, 1994, Banff, Alberta, Canada
[doi> 10.1145/192506.192552]
|
 |
22
|
|
 |
23
|
|
| |
24
|
|
| |
25
|
Hammer, M., and J. Champy. 1993. Re-engineering the Corporation: A Manifesto for Business Revolution, London: Nicholas Brearley Publishing.
|
 |
26
|
|
| |
27
|
|
 |
28
|
Erin E. Heximer , Uliyana Markova , Lisa Wu , Justine Yoon, A multidisciplinary approach to improving the user experience: information development, test, and user experience design teams working together, Proceedings of the 20th annual international conference on Computer documentation, p.72-78, October 20-23, 2002, Toronto, Ontario, Canada
[doi> 10.1145/584955.584966]
|
| |
29
|
|
| |
30
|
|
| |
31
|
IBM Rational ClearQuest, http://www.ibm.com/software/awdtools/clearquest/
|
| |
32
|
Janson, R. 1993. How re-engineering transforms organizations to satisfy customers. National Productivity Review (Winter):45--53.
|
 |
33
|
|
 |
34
|
|
| |
35
|
Kleiner, Art, and Roth, George, How to Make Experience Your Company's Best Teacher, Harvard Business Review, Sep-Oct, 1997.
|
| |
36
|
Kotter, J. Leading Change, Harvard Business Press, 1996.
|
 |
37
|
|
| |
38
|
|
 |
39
|
|
| |
40
|
|
| |
41
|
|
| |
42
|
Nonaka, Ikujiro, The Knowledge-Creating Company, Harvard Business Review, Nov-Dec, 1991.
|
 |
43
|
|
| |
44
|
Orlikowski, W. J. (1996). "Improvising organizational transformation over time: A situated change perspective," Information Systems Research, Vol.7, No.1, pp. 63--92.
|
 |
45
|
|
| |
46
|
Paolucci E., F., Bonci, and Russi. 1997. Redesigning organizations through business process re-engineering and object-orientation. In Proceedings of the European Conference on Information Systems, Cork, Ireland: 587--601.
|
 |
47
|
|
 |
48
|
|
 |
49
|
|
| |
50
|
|
| |
51
|
Rigby, D., Reichheld, F., and Schefter, P., "Avoid the four perils of CRM," Harvard Business Review, Vol.80, No.2, (2002), pp. 101--109.
|
| |
52
|
Ryals, L. and Knox, S. (2001). "Cross-functional issues in the implementation of relationship marketing through customer relationship management," European Management Journal, Vol.19, No.5, pp. 534--542.
|
 |
53
|
|
| |
54
|
Scacchi, Walt. "Process Models in Software Engineering." Final version appears in, J. Marciniak (ed.), Encyclopedia of Software Engineering, 2nd. Edition, Wiley, pp. 993--1005, 2002.
|
 |
55
|
|
| |
56
|
Worren, N. A. A, Ruddle, and Moore, (1999). "From Organizational Development to Change Management: The emergence of a new profession," The Journal of Applied Behavioural Science, Vol.35, No.3, pp. 273--286
|
INDEX TERMS
Primary Classification:
D.
Software
D.2
SOFTWARE ENGINEERING
D.2.7
Distribution, Maintenance, and Enhancement
Subjects:
Documentation
General Terms:
Design,
Documentation,
Standardization,
Theory
Keywords:
computer documentation,
customer feedback,
information,
outside-in development,
software documentation,
user assistance
|