The Development Process Best (and Good) Practices

1. Identify the appropriate approach and solution based on the problem(s) analysis and business requirements
2. Conduct as, and when required, the appropriate assessments for the business processes, system, applications, infrastructure, and/or network early and in a timely manner.
3. Determine if Rapid Application Development is required
a. RAD/JAD
b. Prototype and mockups
c. Facilitated sessions and surveys
4. Select a model and implementation methodology (RUP, others, PMI, Agile, Iterative and Incremental, Waterfall, etc.)*that is appropriate for the solution
5. Use Development and Configuration Management/Control Tools *
6. Document terminologies and abbreviations and include in proposal/contract and development and implementation documentation (especially in requirements and design documents)
7. Select IDE (including CASE) if required and conventions to be followed* (example: esclipse, etc. ). Typically an IDE is dedicated to a specific programming language as to provide a feature set which most closely matches the programming paradigms of the language. However, some multiple-language IDEs are in use, such as Eclipse, ActiveState Komodo, recent versions of NetBeans, Microsoft Visual Studio, WinDev, and Xcode.
8. Select and conduct technical reviews (schedule them)
9. Perform development and system testing, use as required automated test tools *
*Identify and select the appropriate tools, applications, and methodologies

Worst/Bad Practices
1. Not including users/customers in the beginning of a project and throughout the development process. Not trusting their participation, commitment, and collaboration as a team member. (They are the ultimate users and benefactors.