You can take the exam right after you successfully complete the in person 2 day Scrum Alliance® Certified ScrumMaster® (CSM®) class delivered by a Certified Scrum Trainer® (CST®). The exam is not taken during the class but can be taken immediately after the end of day 2 if you like. I however do not recommend that…
To become a Certified ScrumMaster® (CSM®) you have to Take the in person 2 day Scrum Alliance Certified ScrumMaster (CSM) class delivered by a Certified Scrum Trainer® (CST®).Pass the Scrum Alliance administered CSM exam within 90 days of taking the class. To pass, you must correctly answer 37 out of 50 questions within 60 minutes.Accept the…
Check out the video below of Michael Spayd and Michele Madore presenting on "Has Your Agile Transformation Hit a Wall? Understand Why and What to Do Next" at the Washington DC Scrum User Group (DCSUG). Michele and Michael look at what might be missing from a transformation: Culture has not changed, leaders do not yet fully…
In my previous post, I talked about establishing a debt payment plan. On a Scrum team, there are several approaches a team can take to pay down the debt. Debt Limit Trigger – Whenever our debt limit is reached, the team focuses the next Sprint on technical debt reduction (better than nothing).Release Trigger - After every…
The classes described here lead to certifications issued by the Scrum Alliance®, a nonprofit association with more than 1 million practitioners worldwide. Scrum Alliance was founded in 2001, and is the largest, most established and influential professional membership and certification organization in the Agile community, guiding Agile practitioners through every step of their journey, and providing…
Check out the video below of Rob Jolles presenting on "How to Change Minds: The Art of Influence Without Manipulation" at Washington DC Scrum User Group (DCSUG). Rob explores why people are resistant to change. Why? Because people fundamentally fear change. In this fast paced, and spirited keynote participants are forced to focus away from the…
In the previous blog, we looked at how when we don’t actively manage our debt, it can lead to a vicious cycle we can’t get out of. We want to make prudent and deliberate decision on debt and have a plan to service the debt and make our payments. So to do that, we need a…
Check out the video below of Dan Davis presenting on "So You Want to Go Faster" at Washington DC Scrum User Group (DCSUG). Dan explores how frequently does a good agile team deploy to production. Not every team is capable of deploying "on every commit". What does it take for a team to even start deploying…
In my previous post, we looked at the difference between good technical debt and bad technical debt and highlighted the importance of keeping our debt low. Unfortunately, the typical scenario that most teams face is that they eventually reach a point where their output is lower then what it used to be. Instead of stopping and…
Check out the video below of Mike McGarr presenting on "Productivity Engineering - Scaling a DevOps Culture" at Washington DC Scrum User Group (DCSUG). Mike talks about how the software industry has seen an influx of technologies and techniques, including DevOps, cloud, Agile, microservices, machine learning, big data, containers and more. Organizations are becoming flatter and…
In my previous post, we defined technical debt and saw how not all technical debt is bad. Just like in the financial world, some type of debt is considered ok as long as it is paid back. Consider a house loan or a car loan for example. Those are generally considered acceptable types of debt in…
Check out the video below of Lisa Adkins presenting on "We are the Leaders we have been Waiting For" at Washington DC Scrum User Group (DCSUG). Lisa asks if we Agilists value individuals and interactions over processes and tools, why do processes and tools so often run the show? In this talk, Lyssa offers two good…
In my previous posts we looked at symptoms of bad code and reasons we write bad code. And bad code leads to technical debt. The Technical Debt Metaphor Ward Cunningham introduced the Technical Debt metaphor by stating: “Shipping first time code is like going into debt. A little debt speeds development so long as it is…
In my previous post, I discussed symptoms of bad code. Here I’m going to look into some of the reasons we end up writing bad code: Top 5 Reasons For Writing Bad Code 1. Deadlines You’ll hear excuses like we have a deadline to meet so we don’t have time to test or to make the…
Check out the video below of Jeff Gallimore presenting on "Decoding Culture: Beyond the Fluff and Back to Business" at Washington DC Scrum User Group (DCSUG). Jeff explores how culture connects to organizational performance, vocabulary for how to describe culture, research about the effects of culture, and tactics you can use to change your culture for…