|
• Concrete requirements – Clear, consistent, complete,
explanatory, non ambiguous, practical, detailed, and
assessable requirements that are agreed to by all members of
the development process as well as the customer’s end. The
use of blue-prints or prototypes is appreciated to help
clear out the customer requirements help nail down
requirements. In highy aggressive environments, the
continuous close communication with customers as well as end
users is very important.
• Realistic deadlines – The overall scheduling of the project should be well defined and every step in the software development life cycle should be given appropriate time. These steps may include planning, testing, coding, bug fixing, testing, re testing, changes, documentation etc. the personnel should be able to complete the project within time. • Sufficient testing – The testing should start early on and re testing should be done after fixes or changes, the time for testing and bug fixing should be well defined in the project plan so that the time constraints do not constrain the testing and bug fixing process.. 'Early' testing is usually the part of the programming process and is done by the programmer while working on the code. • Stay glued to the initial requirements – The programmers must be prepared to contradict and defend against the newly proposed changes that might be provided by the customer during the development process, and to explain consequences of changing the code or requirements to the customer. However, if changes are actually necessary, the changes should be taken into account and reflected in schedule changes for the project. The programmers should work as closely with the customers and end users as possible. This will enable them to have a higher degree of comfort in making their requirements decisions and minimizing the excessive changes in the future. • Communication with customer – Arrange walkthroughs and inspection sessions whenever appropriate, make good quality use of group communication tools like groupware, wiki’s, bug tracking tools and change management tools, intranet etc. Also ensure that the entire documentation that is available is accurate and up to date. Also keep an electronic copy of the documentation instead of paper documentation. Use prototypes and communicate with customers whenever possible to clarify his/her expectations. |
| Sponsored Links: |
| << back |