It took me some time to find a reference about this. It looks like you all extracted the best practices of IS in your posts (this is the disadavantage of passing an assignment just hours before deadline tongue ). Good thing i managed to find this site: http://www.ctg.albany.edu/publications/guides/tying and able to find some practices, here's what I found:

Define purpose and scope
-A well-defined purpose and scope are intstrumental for success. With a definite purpose it becomes easy to focus on a project. In defining a purpose project goals should be prioritized and identifying resources, such as funds, time, people, technologies will give insights on what the scope of the project will be.

Adopt tools and techniques that can manage complexity
-In managing system a project requires tools to manage people, time, relationships, partnerships, ideas, conflicts, resources, information, and processes. Visual tools like conceptual and project workflow diagrams and timelines become a guideline to the project that evolve over time.

Train thoroughly
-Mastering a new computer system can be a tricky business for even the most proficient users. When any user adopts a new information system, it creates some anxiety, especially when the new system is not as user-friendly as the system developers because what is user-friendly to the development team may not easy to handle for the end-uses. The process of adopting a new system can easy by offering well-designed, user-oriented training sessions and reference materials. Also by training the users the developers can improve their system by hearing feedbacks from the users.