I'm a Certified Scrum Master, I've read the books, I've read the blogs, I've written articles but more importantly, I've worked with small startups to large billion dollar on training, running, and being successful with Agile. It's not enough to simply read about Agile, those who truly understand do so because they've lived it. They have been in different sized companies, they have seen different situations, and they have worked with different people. Why is that so important

Choosing the proper person to be the Product Owner on your team is a critical factor to success. Scrum.org explains a Product Owner “is responsible for maximizing the value of the product resulting from the work of the Development Team”. A Product Owner needs to be an expert at what you’re building. Not an expert in the technology the application is being built in, not an expert in your organization, but a subject matter expert in what your application does. The value it prov

A Scrum Master needs to KNOW scrum. They are on the hook to ensure you follow it, to ensure your teams understands why, to ensure road blocks are cleared in an Agile manner, as opposed to taking steps backwards away from Agile and more towards Waterfall. If you're investing in Agile/Scrum, do it right. Many organizations who implement Scrum just hand the title of Scrum Master off to someone within the team. In some cases this is ok, but remember, a Scrum Master is supposed to

The misconceptions of Agile and Scrum are amazing in the industry today. You have your Agile fanatics and your old-school waterfall professionals facing off in what seems like an endless fight. I’ve been practicing Scrum since 2003 and a Certified Scrum Master since 2006. I’ve implemented Scrum in many different organizations and industries. I’ve provided training to developers, business analysts, project managers, quality assurance analysts and executives on the concepts of