Expected |
Major Softgoal |
sub Softgoal |
Cont.
Value |
Eval.
Value |
Study |
Situation |
Good Collaboration |
|
|
|
|
|
|
avoid
under utilization of customer |
+ |
PD |
|
from
100% availability of customer, only 20% was necessary |
|
minimized
technological gap between customer and developers |
+ |
PS |
|
training the customer (as
needed), |
|
|
|
|
|
|
commitment |
customer
be available when needed |
++ |
D |
|
lack
of on-site customer |
|
|
|
|
|
|
self-motivation |
|
|
|
|
|
be effective |
minimum
customer/company cultural conflict |
+ |
PD |
|
|
|
customer
can handle multiple tasks and roles |
++ |
D |
|
Large
project (S6) - customer could not play the role of all stakeholders |
|
|
|
S |
|
Team
of Customers, rather than one customer were on-site |
|
|
|
S |
|
Classical
stakeholder analysis had been performed, before working with on-site customer |
|
company
does not overinfluence the customer |
+ |
D |
|
Development
team could easily convince the customer, without actualy implementing some of
the user stories |
|
customer does not
overinfluence the team |
+ |
D |
|
when
customer noticed that he can influence the team, started to complain about
anything and everything |
|
|
|
S |
|
customer
(team) was trained on how, and when to represent their idea, besides he was
asked to think of "…so that..." in order to have a good reason for
his demands |
customer be beneficial to the team |
customer
be competent |
++ |
? |
|
|
|
customer
be knowledgable (about domain needs, priorities) |
++ |
? |
|
|
|
customer be credible |
++ |
? |
|
|
|
customer
have managerial support |
++ |
? |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|