Unprecedented levels of change caused by the pace of innovation are stretching traditional contract models to the breaking point. As more organizations adopt Agile and Lean for the development of innovative/complex products and services, new contract models are needed that accommodate change. The Evolutionary Contract Model, based on Agile / Lean principles, offers promise as a possible solution.
The traditional Waterfall model fits nicely with the way companies buy things: requirements are drawn up, a supplier quotes a price, and everyone signs a legally binding agreement. Contracts written this way seldom offer the freedom to work using an Agile approach. This article examines four separate models available to suppliers and customers for establishing contracts for Agile work.
With the recent legal battle between Google and Oracle there is a renewed focus on the patent issues for Java and .NET. Tim Smith introduces the licenses offered by Oracle/Sun and Microsoft, with a focus on how they may affect third party implementation. Possible motivations for Google Android’s unique implementation are also covered.