Professional Documents
Culture Documents
It has been observed that when any software project is started the people
involved are unhappy with each other during the time of the development
and afterwards. The clients are dissatisfied by the technical team and the
technical team is unhappy with the user representatives.
There are many reasons for this hostile behavior of the team members
representing the users and developers, but the major of all the reasons that
cause the dissatisfaction of the team is its inability to communicate. This
reason can then be further classified into the following sub categories.
• Users are reluctant to give away information: users assume that if the
technology will be applied, it will pose a threat to their importance or
need in the organization. That’s why they are reluctant to give away
the information to the requirements engineer.
For all of the above reasons the communication is not good between the
development team and the user representatives.
Apart from the reason of inability of the user representatives and the
development team; the internal conflicts of the organization is also one of
the reasons of unhappiness.
Before getting any system developed the management require to take the
employees in confidence and should pay attention towards the real users
of the system, not on the representatives of the real users. This will save
the development team from the future rework.
The features that users present as their “wants” don’t necessarily equate
to the functionality they need to perform their tasks with the new product.
To get a more accurate view of user needs, the requirements analyst must
collect user input, analyze and clarify it, and determine just what to build
to let users do their jobs. The analyst has the lead responsibility for
recording the new system’s necessary capabilities and properties and for
communicating that information to other stakeholders. This is an iterative
process that takes time. If you don’t invest the time to achieve this shared
understanding – this common vision of the intended product – the certain
outcomes are reword, delayed completion, and customer dissatisfaction
Most products have several groups of users who might use different
subsets of features, have different frequencies of use, or have varying
experience levels. If you don’t identify the important user classes for
your product early on some user needs won’t be met. After identifying all
user classes, make sure that each has a voice.