Software projects are inherently risky, and the ways to run astray begin even before the project begins. The quality of a procurement solicitation governs the results of a project, laying a solid foundation for success or creating unnecessary problems that doom a project. Since the negative examples are often more illustrative, here are a few pitfalls to avoid: 1. There is no such thing as etcetera in a specification . Over the past few weeks I have reviewed requests for proposals that list open-ended requirements for integration, mentioning one or two specifics and then the dreaded "etc." rears its head. The result is that vendors either decide not to bid or pad the price to cover the risk of the unnamed integration. 2. Fixed price requires fixed specifications . If you choose a fixed price contract, vendors cannot determine a price without complete and detailed specifications. Fixed price combined with vagueness can result in a game of change orders where bid
From James Townsend, vice president of Sylogist, thoughts on digital transformation, marketing automation, customer relationship management, Power Apps , Microsoft Dynamics 365, government contracting, customer service and more.