Whats In A Word – Overhead
Daybreak Over Lake Eire Is All About What Is Overhead A brief interlude to our focus on meetings in agile frameworks to discuss the use of the word overhead. Once upon a time, my grandfather wanted...
View ArticleToo Much Meeting Time? Antipatterns Not To Try
Storms on the horizon! In whatever flavor of agile that you are doing, meetings and ceremonies are lightning rods for resistance. In response, numerous approaches for improving the scenario have sprung...
View ArticleToo Much Scrum Meeting Time: Summary
Poking at any entrenched framework always elicits a response; almost all of the responses are well thought out and reasonable. In the past five essays, we have explored two major questions: Do the...
View ArticleOur Stories Aren’t Getting Done: Taking More Work Into A Sprint
Over the years I have gravitated towards the idea that work entry issues are the single clearest indicator of problems in an organization. My first job after getting my Bachelors’s degree was for a...
View ArticleOur Stories Aren’t Getting Done: Hitting Roadblocks You Should Have Expected
Fitting The Pieces Together Getting the work you commit to getting done in an iteration or sprint is not constrained to a conversation about Scrum or Scrumban. Timeboxing is common in almost all work...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 1, Logistics and Front Matter
Today we begin the re-read of Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller, published in 2020 by The Pragmatic Programmers. I interviewed Ryan and...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 2, A Brief Introduction To Scrum...
Today we dive into the main part of Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller, published in 2020 by The Pragmatic Programmers. In this...
View ArticleChapter 3 – Breaking Bad Scrum with a Value-Driven Approach
Today we dive into Chapter 3 of Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller, published in 2020 by The Pragmatic Programmers. You can make a good...
View ArticleSPaMCAST 640 – Communities of Practice Goals, User Stories, Essays and...
Play Now! The idea of Communities of Practice is thrown around a lot in organizations, often without thinking about the goals of a CoP. Why? Organizations are increasingly becoming more diverse and...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 4: Chapter 4 – The Product Owner
Today we dive into Chapter 4 of Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller. I have argued that the role of the Product Owner is the hardest in...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 5: Chapter 5 – The Product Backlog
Chapter 5 of Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller addresses the product backlog. The authors start this chapter with a great story about the...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 5: Chapter 6: The Development Team
This week we tackle the second role in Scrum, the development team. The development team covers the people that aren’t the scrum master or product owner — the group of people that actually takes an...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 7: Chapter 7: Embracing The Scrum...
In SPaMCAST 642 Vasco Duarte made the startling statement that a Scrum Master will be your next CEO. Chapter 7 in Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 9, Chapter 9: Thinking In Sprints
Chapter 9 in Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller, tackles the sprint. To paraphrase the Beach Boys Everybody’s gone sprintin’ Sprinting’...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 10, Chapter 10: Sprint Planning
Chapter 10 in Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller, dives into planning.. Sprint planning one of the major events in Scrum. All sprints...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 11, Chapter 11: The Sprint Backlog
The sprint backlog is the work teams do on a day-to-day basis. A sprint backlog is a tool that the team uses to guide their activities. The backlog is a combination of outputs of other activities such...
View ArticleRe-read Saturday, Fixing Your Scrum, Week 12, Chapter 12: Reclaiming The...
This chapter deals with one of the crux issues that almost every Scrum master or agile coach faces at some time. The daily meeting has become an almost ubiquitous signal to the world that a team or a...
View ArticleRe-Read Saturday, Fixing Your Scrum, Week 13, Chapter 13: Deconstructing The...
At the end of every sprint, a team should have a deployable product increment. There are a ton of ideas packed into that single phrase. In this chapter, Mr. Ripley and Miller focus on the concepts of...
View ArticleSPaMCAST 650 – Work Entry Patterns, Many Types of User Stories, Essays and...
Work entry, in its simplest form, is the steps needed for work to be triaged to ensure that it is the right work, that it is ready to be worked on, and the priority of the work. This week we talk...
View ArticleRe-Read Saturday, Fixing Your Scrum, Week 14, Chapter 14: The Sprint Review
I have heard the sprint review called everything including a demo, demo day, show and tell and sprint review. If teams and organizations do the sprint review well, I don’t care if you call it jello....
View Article