We have talked about Scrum and Agile.  However, some guidance helps us improve our odds or success.  That is an essential part of becoming a better developer.  In this episode, we look at scrum master anti-patterns and position the team for improvement and success.

No Retrospective

Everyone needs a plan to be productive in pursuit of a goal.  Our goal of improving with each sprint will be impossible to achieve without assessing how we are doing.  That is what a retrospective provides.  When we skip the retro, we are embracing the worst of the scrum master anti-patterns.  There are situations where we are pressed to skip over this “additional meeting.”  However, it is a key factor in our improvement and should be viewed as a requirement that cannot be removed.

Learn More About Scrum

Challenge of The Week: Which of these do you see in your team?  How will you fix it?

Rob Broadhead

Rob is a founder of, and frequent contributor to, Develpreneur. This includes the Building Better Developers podcast. He is also a longtime student of technology as a developer, designer, and manager of software solutions. Rob is a founder and principle of RB Consulting and has managed to author a book about his family experiences. In his free time, he stays busy raising five children (although a few have grown into adults). When he has a chance to breathe, he is on the ice playing hockey to relax.

Leave a Reply