Truth, Lies, and Scrum

I enjoy when people contribute their knowledge about agile software development to other humans living on planet Earth. The wisdom I’ve gained from such mentors aside, I think it’s terrific people are passionate, engaged, and excited enough to share their insights with others. As the most popular way to put agile values and principles in play, Scrum is arguably the subject most frequently written about in the agile community. Again, these articles and discussions about Scrum (and inferences about agile) are intended to assist, educate, and inform others in improving their careers and/or perspectives. This is terrific, too. Unfortunately, much of what is written tends to be misguided, misunderstood, or flat-out wrong

With respect and kindness for all those who take time to contribute, especially those cited as examples of problems, I’d like to share some truths of what Scrum is, what it isn’t, and how you can improve as a practitioner. This isn’t an all-inclusive list; just a handful of topics which I see misrepresented often.  Continue reading

Scrum Guide Sliders

It was Monday afternoon on her first day of work at a new company and Sarah was feeling anxious. Having studied Scrum over the last few months, Sarah had been hired to serve as a Scrum Master and she was eager to begin applying her new skills, however nothing she had been told today seemed congruent with her lessons. As Sarah listened to her new manager explain why the company’s software required the organization to field a “UI team,” “service team,” and “back-end team,” she felt especially troubled by the phrase she’d heard multiple times on this day: “No one does Scrum by the book.”

“If no one actually follows the design of Scrum,” she wondered to herself, “why did my Scrum trainer teach it to me?”

Continue reading