I was watching Moneyball this weekend for the first time and was riveted by the story of Billy Beanes and the Oakland A’s miracle of 2002. I’m not much of a baseball fan (I grew-up and live in the heart of ”tobacco road” where college basketball is king) so I was only superficially aware of Billy’s bold, perhaps reckless move in 2002 to pursue an unproven, unorthodox approach to building a championship baseball team.

I won't recount the film's entire storyline, but the basics go like this--Team wins big one year, loses talent the next, due to free agency, and “rich teams” like the

Virtually all Agile developments project will eventually meet the user experience design process. It's inevitable. Unless you're working on something that will run unseen by anyone -- some middleware, perhaps, or an application that integrates data flow between two existing systems -- someone has to interact with the software being designed and built. Even the most compelling UX design will literally do nothing without