requirements and good communication.
1. Ensure the requirements are solid, clear, complete, detailed,
cohesive, attainable and testable. All players should agree to
requirements. Use prototypes to help nail down requirements.
2. Have schedules that are realistic. Allow adequate time for
planning, design, testing, bug fixing, re-testing, changes and
documentation.
Personnel should be able to complete the project without burning out.
3. Do testing that is adequate. Start testing early on, re-test after
fixes or changes, and plan for sufficient time for both testing and
bug fixing.
4. Avoid new features. Stick to initial requirements as much as
possible. Be prepared to defend design against changes and additions,
once development has begun and be prepared to explain consequences. If
changes are necessary, ensure they're adequately reflected in related
schedule changes. Use prototypes early on so customers' expectations
are clarified and customers can see what to expect; this will minimize
changes later on.
5. Communicate. Require walk-throughs and inspections when
appropriate; make extensive use of e-mail, networked bug-tracking
tools, tools of change management. Ensure documentation is available
and up-to-date. Use documentation that is electronic, not paper.
Promote teamwork and cooperation.
No comments:
Post a Comment