8
Useful tips
● Over 50% of decision makers have difficulties establishing requirements of the project14. And over 50% of those change them during the development. That is why some tips might be helpful.
● To avoid throwing money and unnecessary delays, the Partner might want to consider a few aspects of the project. It's worth asking these questions:
❖ What is the subject of the product? (What do we want to do?)
❖ What tools, people, and methodologies do we want to use? (How do we want to do it?)
❖ What happens when all fails? (What is the safety net?)
● Make sure a team you choose takes care of the process of making software as much as you do15 . This directly means that the price should not be a factor. Good and cheaper teams can be found all over the world. Good teams that actively participate in the process are hard to come by.
● Take care of Definition of Done in the contract itself. If the software has passed the required tests, all documentation has been gathered, and software has the previously assumed code quality, DoD has been met. DoD should exist as an attachment to the contract and be established during the negotiations of it.
● Analyse who owns the copyright in the created code and make sure you get the rights to the source code after the release of the software.
'Everybody in the real world will agree - the moment a project is behind deadline, quality assurance tends to go out the window'
Alan Cox, British developer, co-author of a Linux core