Mitch Lacey is an agile practitioner and trainer. Mitch has been managing projects for over fifteen years & is credited with many plan-driven & agile projects. He is the author of "The Scrum Field Guide", a book targeting teams adopting Agile and Scrum practices.
Mitch honed his agile skills at Microsoft Corporation, where he successfully released core enterprise services for Windows Live. Mitch's first agile team at Microsoft was coached by Ward Cunningham, Jim Newkirk & David Anderson.
While at Microsoft, he transitioned from Program Manager to Agile Coach, working hand-in-hand with groups throughout their transition to Agile practices. After Microsoft, Mitch was the Agile Practice Manager at Ascentium Corporation where he practiced agility on the projects he ran every day while coaching customers on agile practices and lessons on agile adoption worldwide.
As a Certified Scrum Trainer (CST) and a registered Project Management Professional (PMP), Mitch shares his experience in project and client management through Certified ScrumMaster courses, agile coaching engagements, conference presentations, blogs & white papers.
He has authored “Adventures in Promiscuous Pairing” presented & published at the Agile 2006 conference, “Transitioning to Agile: Key Lessons Learned in the Field” presented and published at the Fall 2007 PMI Global Congress in Atlanta, Georgia and "The Impacts of Poor Estimating - & How to Fix It" presented & published at the winter 2007 SQE Agile development conference in Orlando, Florida.
He has presented at Agile Alliance Agile 2006, 2007, 2008 and 2009 conferences, the 2008 Better Software Conference and the 2008 - 2013 SQE Agile Development Practices conferences. He was the stage producer for the Organization and Culture track for Agile 2009 and continued that trend by producing the Leadership and Organizations track for Agile 2010 and 2011, was the Agile2012 conference chair and is the Agile2014 conference chair.
Articles I've written
"Four"warned Is Forearmed
We all know the three questions of Scrum: What did you do yesterday? What will you do today? What blocking issues do you have?
We all do our best to answer these questions. So how come so many of our initial demos turn up problems we didn't catch? Maybe it's because, at least at the beginning, we need to add a fourth question to our daily standups.
How Do We Know When We Are Done?
Last week, two practitioners of Scrum shared ways in which their teams have defined done. This week, CST and CSC Mitch Lacey gives his own definition, one he argues is more in line with agile principles, both in its structure and in its formation.