Ryan Ripley has worked on agile teams for the past 10 years in development, scrum master and management roles. He’s worked at various Fortune 1000 companies in the medical device, whole sale, and financial services industries.
Ryan is great at taking tests and holds the PMI-ACP, PSM I, PSM II, PSM III, PSPO I, PSD I, CSM, CSPO, CSP, and CAL1 agile certifications. He lives in Indiana with his wife Kristin and three children.
Ryan blogs at ryanripley.com and hosts the Agile for Humans Podcast.
When practiced well, Scrum can empower people, teams, and organizations to solve complex problems and deliver value to their customers. But bad Scrum does the opposite. If team members or leaders don't embrace Scrum values, it can be oppressive and create tension. Here's how you can prevent bad Scrum from taking hold.
The daily scrum was created to help the Scrum team meet its sprint goal. Unfortunately, answering the three daily questions can turn a synchronization and planning meeting into a status report. Here are four ways to make sure your team members are collaborating about their work and are ready to tackle the next day.
Agile is designed to keep failures small and manageable. It’s essential to be able to talk about small failures and ways to improve during the retrospective so that the teams can advance their agile practices. If your teams can’t talk about their small failures openly, there is a great risk of bigger troubles soon.