TechEd Europe 2010 Recordings and Downloads

in Agile - 0

You can grab all sessions here:

http://www.msteched.com/Speakers/Mitch-Lacey

Here are links to my specific talks with slides and audio. Enjoy!!

http://www.msteched.com/2010/Europe/ARC208 - Architecture in Agile Projects – How to do it right

Architecture: Big design up front, or cowboy ‘design-it-as-you-go’ coding? In agile projects we hear that BDUF is evil. Does that mean that agile requires no architecture? Is there no more need for architects in agile projects? Neither could be farther from the truth. In this talk, Mitch Lacey, former Microsoft Program Manager, will walk you through a case study of one of his projects to show you how they architected a system that required 99.999% uptime and supported 5 million users – all while using Scrum and XP.

http://www.msteched.com/2010/Europe/ARC207 - Working Software is Not Enough!

The true measure of project progress is working software - or is it? Our team thought it was, and we were wrong. This is the story of our team, a team that set out to build a new order tracking system for a worldwide vehicle manufacturer and failed. So, what are the factors necessary for a successful project? In this session you will get insights into our team’s key-learnings on critical success factors - insights you can definitely use to ensure your project’s success.

http://www.msteched.com/2010/Europe/ARC206 - Scrum for Managers

The role of the manager in a software company is changing. No longer is it about driving people to achieve results. Now it is about enabling teams to be hyper-productive. But how can this be accomplished? Scrum, an agile framework, has been used successfully to build hyper-productive teams. What is Scrum? How can a manager build hyper-productive teams that outpace everyone else? In this talk you will hear exactly what Scrum is, its base components, and the traits required to help ensure success. Mitch Lacey, former Microsoft program manager will share his experiences helping teams adopt the Scrum framework. In the course of his work he identified four patterns that were present in teams that succeeded, but were absent in teams that failed.