Feedback iteration plan

Adaptive planning—changing the project plan based on the feedback from each iteration Please note that it is perfectly OK to cither add new features or remove already planned features in the forthcoming iterations. This... 

Again regardless of in-house or outsource development, document a list of features and prioritize them. Break the project down into short, timeboxed iterations, each focusing on one or two of these features (Chapter 5). Do not let the iteration deadline slip. Reduce the scope of the iteration if necessary. Implement features with high business values and high business and technical risks in early iterations. Make sure each iteration delivers a production quality partial system to solicit feedback and let the system grow incrementally. The project plan should be adjusted based on the feedback. It is OK if the initial project plan is not accurate. However, it should become more and more accurate as more iterations are completed. Test and integrate early and frequently. 

An iterative, user-centred approach has advantages in many areas of product development but perhaps none more so than in user interface design. Manufacturers should actively plan to work and re-work a user interface many times in the course of a project. Of course the earlier this process begins, the more opportunities there are to tweak the design without compromising project timescales. In the context of a time-bound software development project it may not be realistic to evaluate every screen and function in a system so it makes sense to prioritise those which are used frequently and/or are critical for safety. Even after go-live it is invaluable to solicit feedback from users once they have had the time to use the system in anger and address areas of concern. 

---