A team was given a new assignment. They would finally start developing a cool new technology that they had wanted to focus on for a while. They were assigned full-time to this new project. What’s not to like? Well… It’s never that simple. Scrum teams don’t exist in a vacuum, and soon enough the “old” work started interrupting the “new and cool tech project”! Listen and learn what happened to that team.
In this episode, we refer to the book: Principles of Product Development Flow by Don Reinertsen.
Featured Book for the Week: Kanban: Successful Evolutionary Change for Your Technology Business by David Anderson
In Kanban: Successful Evolutionary Change for Your Technology Business by David Anderson, Jeremy found that Scrum needs to evolve, and that following Scrum as such may not be the best option for you, or your teams. In Kanban, David Anderson answers the following questions:
- What is Kanban?
- Why would I want to use Kanban?
- How do I go about implementing Kanban?
- How do I recognize improvement opportunities and what should I do about them?
About Jeremy Willets
Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!
You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.
