It has been suggested that one of the problems of having a user closely involved with a software development team is that they ‘go native’. That is, they adopt the outlook of the development team and lose sight of the needs of their user colleagues. Suggest three ways how you might avoid this problem and discuss the advantages and disadvantages of each approach.
What will be an ideal response?
1. Involve multiple users in the development team. Advantages are you get
multiple perspectives on the problem, better coverage of user tasks and
hence requirements and less likelihood of having an atypical user.
Disadvantages are cost, difficulties of getting user engagement and possible
user conflicts.
2. Change the user who is involved with the team. Advantages are, again,
multiple perspectives. Disadvantages are each user takes time to be
productive and possible conflicting requirements from different users.
3. Validate user suggestions with other user representatives. Advantages are
independent check on suggestions; disadvantage is that this slows down the
development process as it takes time to do the checks.
You might also like to view...
Subsites must be created by the Administrator of the Team site, unless team members have been given full permissions to the team site
Indicate whether the statement is true or false
Which of the following will is considered a logical error?
a) forgetting a semicolon at the end of a programming statement b) typing a curly bracket when you should have typed a parenthesis c) multiplying two numbers when you meant to add them d) dividing by zero e) misspelling an identifier