An Oracle blog about Unified Method

The Eating Contest - How a software project is like an eating contest

Guest Author

It may be hard to imagine, but there are some similarities between software projects and eating contests. No, I'm not implying that both are messy  and leave you feeling ill. Done properly, only an eating contest will produce those results.

What I am talking about is that both eating contests and software projects should employ an iterative and incremental approach. In other words, smaller chunks are better whether you're eating or implementing.

Click here to hear about a guy named Steve, his eating contest exploits, and how my sleeping brain made a connection between Steve's approach and successful software projects. This brief video describes OUM's principle of iterative and incremental and how it should be used to create success in eating contests and on software projects.

Whether it's an on-premises implementation or enabling a customer in a public cloud environment, businesses expect very rapid time to value for all of their IT investments. An iterative and incremental approach helps implementers live up to those expectations.

Once you're finished viewing the video please leave a comment or go to the "Oracle Unified Method" group on LinkedIn to give us your thoughts.

Join the discussion

Comments ( 1 )
  • guest Thursday, May 23, 2013

    Hi Tom, I liked the analogy which if you may allow will use it in the OUM Level 3 training delivering in the region and the Partner PM Community days we have started to organize. Partner understand the concept and the approach but are reluctant to put it in practice. Do we have any success stories or references internally within Oracle or partner community that have been able to adopt this approach? I am working on the SKI NOW case study and prepare few iteration plans as samples. However any additional samples will be of great help.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.