University of Minnesota
Software Engineering Center

You are here

Tomo Lennox, Keys to a Successful Project

Date of Event: 
Thursday, November 4, 2010 - 6:30pm
University of Minnesota, Minneapolis, MN


  • 5:30-8:00 p.m. at The University of Minnesota
  • 5:30 start for networking, 6:15 start of meeting


Keller Hall (EE/CS Building) Room Keller 3- 111 (Look for signs) Minneapolis, MN


We have reserved parking at the Washington Avenue Ramp! If there is event parking, tell the parking attendant when you enter that you have a reservation with TwinSPIN. If there is no event parking, take a ticket and tell the parking attendant when you leave that you have a reservation with TwinSPIN


Directions can be found on the map of the Electrical Engineering/Computer Science Building. Check out the detailed map by clicking the “close up” button.

This Month’s Meeting

Program Manager: Paul Kraska Topic: Keys to a Successful Project Speakers: Tomo Lennox


The presentation proposes that there exists fundamental laws from which successful software development methodologies can be developed. An attempt will be made to show that existing methodologies succeed where they support the fundamental laws and fail where they don't. Rather than propose yet another methodology, a dozen practices will be presented consistent with both the fundamental laws and successful projects. The practices are consistent with Lean Development, but oppose some Agile and traditional practices, and support some very old idea about software. These practices can be added to existing project structures to make them more effective.

Speaker Bio

After completing a degree in physics, Tomo Lennox came to the Twin Cities to start his first job out of college at Honeywell. Since then, he has worked for thirty some companies in all combinations of full-time, contract, engineer, manager, development, testing and marketing. In these projects, Tomo has used the full spectrum of methodologies from raw hacking to proof of correctness. Tomo was an early pioneer of Agile practices, before XP or Scrum were documented. After trying everything, Tomo started to develop opinions on what worked and what didn’t. He was looking not just for best practices, but an underlying theory that explained why things work.