James Martin was European IT COO at Lehman Brothers when the investment banking giant collapsed in 2008. Now in August 2011, James has created a company called Firmrater to provide online performance benchmarking for UK firms. As they began development, he wrote a very compelling article on how they build the company and system, based on Scrum software development.
- Produce fully detailed functional specifications before starting development – Interesting…
- Create minimal administrative documentation: focus on the product
- Use online collaboration tools with a minimum of meetings and phone calls
- Carry out rigorous testing based on the specifications
- Use written change requests which include time and cost impact
- Provide a “low distraction, high freedom” working culture for the whole team
Some more quotes from James’ paper:
“If your own money is tied up in a development project you clearly need to do everything you can to make sure the time and cost stays under control and you get the product you need to launch your business.”
Nobody has a crystal ball so producing a traditional project schedule in advance is fraught with risk. Why not abandon the detailed schedule altogether? You can’t slip interim milestones if you don’t have any and you can’t add padding into them either.
To give ourselves the best chance of producing the application in the shortest possible time and at the lowest cost, experience dictated that we produce detailed specifications describing all functions along with a mock-up of each web page.
Overall we spent about 5 months (48% of total project duration) producing the specifications, which was time very well spent. To accelerate the start of development, placeholders were left for text content as this could be dropped into the application later. This enabled us to work on the website content in parallel with development of the application and cut the launch timescale by several weeks.