If you’re tired of having retrospective meetings greeted with groans and heavy, reluctant sighs or feeling like you’re rehashing the same old problems with no signs of improvement, the advice Mark Levison shares in this book will help make your retrospectives more effective.

There’s no need to have retrospectives that people hate and aren’t even useful – with a few tweaks, you can have meetings your team will look forward to, and start seeing real improvements and results. (More details)

Includes follow-up support emails to reinforce what you learned and help you make real changes right away.

Scrum is a tool for building high-performance teams. Some Scrum Teams achieve this goal almost by magic, while others struggle to get there. So is it magic? Or luck? Or is it far more attainable than that? There is a science to it that makes it possible.

Mark Levison offers insight into the neuroscience of teams with five proven Agile methods to create teams that sizzle, not fizzle.

This Scrum for beginners e-book is an easy to understand introduction to basic Scrum methodology and how it helps teams and organizations. Using a simple case study, you visualize Scrum at work in a marketing company and how its structure leads to many benefits. Scrum terms are explained simply, so you can get in on the conversation from the beginning. This is Scrum made simple. (More details)

Includes a follow-up email learning series to give you even more confidence and skills.

To be successful with Scrum in the long term you need more than the basic framework. This is intentional. Scrum provides the structure as a starting point, but it’s designed to work well when applied with other effective patterns.

Mark Levison’s first book discusses topics including why organizations become Agile, the limits of Scrum, common mistakes made and how to avoid resulting failure, and the benefit of exploring other Agile practices.

(Technically not a book, but a downloadable PDF Cheat Sheet.)

In Mark’s workshops, he’s often asked, “How can I help my team go faster?”, or “How can we deliver this Product sooner?” His answer is always the same. “You must slow down to go fast.”

In software development, the single best way to improve quality, and eventually speed, is writing less code. Most of the time spent writing code should be to understand the problem and then find the simplest solution to it. The practices used to facilitate this in Agile software development are popularly known as Agile Engineering Practices.