Iteration Plans for COTS Projects
The commodity-off-the-shelf (COTS) project shares a lot of process with the custom system development project. This is common sense since every COTS product is the result of a vendor’s custom development project, and both types of project share a common goal. The advantage to the organization implementing COTS systems is a greatly simplified project.
The COTS implementation includes many of the same activities that comprise various parts of a custom project. The methods for completing COTS projects therefore use many of the same methods used for delivering custom systems. These methods generally address certain design elements or functions of the application that can not, or should not, be pre-configured in the base product by the vendor, as they will vary according to a particular customer’s requirements. In most commercially successful COTS products, the vendor will provide methods to simplify modification or customization of the base application to suit the individual customer’s needs. The customer typically discovers needs and implementation options as the project proceeds. This is usually done in a series of successive, repetitive passes or iterations.
It is beneficial to implement the specific processes to be used for the COTS project from a fully fleshed out and cohesive SDLC customized for that project. A careful evaluation of the project and the customer is needed to gauge the appropriate level of investment in adherence to process. Many professional IT organizations attempt to invoke a prescriptive set of SDLC methods, but for many projects a review of SDLC compliance needs on a project-by-project basis usually saves time and money. How have you addressed the iteration planning challenge? What have you found that works for you? For more detailed information please contact IT Project Methods.
