Getting What You Want in Your Next Development Project

Top 10 Tips for Successful Development Projects

10. Requirements:

Describe Desired Functionality In As Much Details As Possible - Do Not Describe How It Should Be Done
 

9. Requirements:

Shoot for the Sweet Spot: Requirements, Use Cases, Mockups

Requirements:
8. Standard Language

• Code made available under the GNU General Public License version 2 or later
• Code must be shared in a public git repository
• Require that tech specs are shared with community
• No negative performance impacts - ask them to identify how development will affect performance
• Public catalog (and web client) - visually accessible and responsive design
• New text strings should be translatable
• Developer will provide automated tests that integrate with community tools such as BuildBot and the live tester.

Requirements:

7. Nice-to-have items can be add-ons

Requirements

6. Get (and understand) developer's detailed approach after contract is signed

Testing:

5. Strongly Consider the Question of Testing on Production Data

Testing:

4. Test early and often

Testing:

3. Test against every requirement and every spec that was written

3a. Also test for breakage of existing functionality

Testing:

2. Know your leverage when reporting issues

Project

1. Know that you quite often get everything you want out of your development project

Testing Add-On:

Special Considerations for the Web Client

Community Test Cases at http://evergreen-ils.org/dokuwiki/doku.php?id=qa:eg_test_cases

Questions