Iterative development dates back to the 1950s when it was used by NASA in Project Mercury, but it wasn't until the 1990s that it was leveraged in the Rational Unified Process (RUP), a framework that was widely used throughout the industry. I remember being trained in RUP in 1999 and at this point, it was being hailed as the solution to the all-too-common failure of large waterfall projects. Agile and Scrum were almost unknown and Iterative Development was the hot new thing in IT.
Organizations often tell me that one of their inhibitors to adopting Agile frameworks is the contracts they have with their clients. In the commercial world of projects, there are, broadly speaking, two types of contracts: Fixed Price: The scope, cost, and timeframe are defined up-front. Payment milestones are often linked to delivery milestones (such as requirements sign-off, code released to UAT, etc.) Time and Materials: The client is hiring a vendor project team and agrees to pay them for the hours they work. Normally it is based on the submission of monthly time sheets.
#iterative development #Rational Unified Process #Agile frameworks #fixed price contracts #time and materials contracts
[
add
]
[
|
|
...
]