AgileScotland - “Extremely Profitable Programming with COBOL" - by Clarke Ching, Edinburgh, 12th of May, 2008.
On the first day of the project, I met with our project's key customer - a senior manager with one of the UK's largest companies - he said to me, "I don't know you Clarke, but we simply don't trust your client. We've had too many bad expereinces". Fortunately, my client had warned me to expect this and, in fact, my "promise" to them was specifically to "rebuild trust with their customer". Three months later, mid-way through the project, they flew some of their experts down to visit us, to find out how we'd achieved such a turnaround. A few days later we discovered – and fixed - our first defect. By the end of the project we had rebuilt trust considerably, we'd profitably delivered the project as promised, and in doing so the customer made tens-of-millions of pounds in extra profit. However, we very nearly screwed up the whole thing right near the end – I'll tell you all about that on the night.
The project was a success despite doing many things which some niave but enthusiastic agilists say cannot or should not be done in "agile" projects. For instance:
- My team were working on an old legacy system made up of COBOL, ancient Oracle and rubber-bands;
- Our customer consisted of around 50 people spread across five sites, based in three countries.
- We promised (and then delivered) to an aggressive, fixed-scope, fixed-price, fixed-date contract.
- How to use fear, intimidation and genuine concern to force your customer to collaborate so that they can be successful (I am serious about this: this project would have failed if I hadn't spoken one very calculated, very sincere, sentence just at the right time);
- How to build trust with your team by being lazy and getting them to do your job;
- How to do TDD with COBOL;
- And (as a special bonus!) I'll share with you the one rule we used to deliver more work in each iteration than anyone had ever thought possible. Seriously.
www.clarkeching.com
