Objective Thoughts

Why a Kanban Board is a Value Stream Map but a Scrum Board Isn't - and What This Tells Us

February 22, 2010 — Posted by Al Shalloway

I had an interesting conversation with Masa Maeda of Shojiki Solutions a few days ago. Somewhere in the conversation the observation that a kanban board was a value stream map (VSM) was mentioned. A value stream map shows your workflow as well as the time it takes to do the work. Here is a simple example:


Share this:




  

Going beyond Scrum, Part 2

February 17, 2010 — Posted by Jim Trott

Listen to the webinar audio Going beyond Scrum: Part 2

Chapter 5 of the new book, Lean-Agile Software Development: Achieving Enterprise Agility, discusses "Going beyond Scrum." This is a big chapter, so we are taking it in two parts. Last time, we talked about the importance of optimizing the whole and taking a holistic view of the team if you want to be able to impact the enterprise. Now, we turn to two more key factors: the importance of managing your workflow and the value of accessing and using the good practices that have already been learned by others.


Share this:




  

Going beyond Scrum, Part 1

February 17, 2010 — Posted by Jim Trott

Listen to the webinar audio Going beyond Scrum: Part1

Chapter 5 of the new book, Lean-Agile Software Development: Achieving Enterprise Agility, discusses "Going beyond Scrum." This is a big chapter, so we are going to take it in two parts. First, we want to consider the implications of the maturing and segmentation of the Scrum community and two key factors required for being able to scale Scrum to an enterprise: taking a systemic approach and looking at the team holistically, how it fits with and must work within the organization. Next time, we will look at kanban, managing the flow of work, and using the Scrum clinic to (reusing) good practices learned by others.


Share this:




  

Scrumbutters to Scrumdamentalists - We're Mad as Hell and Aren't Going to Take it Anymore

February 13, 2010 — Posted by Al Shalloway

Before you read on, let me give a disclaimer.  This is not intended to be read by anyone who provides Scrum training or consulting.  If you are a Scrum trainer or coach, please stop reading now.  This is for those of you who have been trying to implement Scrum and are having challenges in doing so. This is especially to those of you who call yourselves (or are called by others) “Scrum Butters” (that is, those who do Scrum but). If you are in this latter category, please read on.  My message has three parts:


Share this:




  

Pages

Free Email Updates!

Sign up for free email updates from
Net Objectives Thoughts Blog

Blog Authors

Al Shalloway
Business, Operations, Process, Sales, Agile Design and Patterns, Personal Development, Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Cory Foy
Change Management, Innovation Games, Team Agility, Transitioning to Agile
Jim Trott
Business and Strategy Development, Analysis and Design Methods, Change Management, Knowledge Management, Lean Implementation, Team Agility, Transitioning to Agile, Workflow, Technical Writing, Certifications, Coaching, Mentoring, Online Training, Professional Development, Agile, Lean-Agile, SAFe, Kanban
Ken Pugh
Software Design, Design Patterns, Technical Writing, TDD, ATDD, Coaching, Mentoring, Professional Development, Agile, Lean-Agile, SAFe, Scrum
Scott Bain
Analysis and Design Methods, Agile Design and Patterns, Software Design, Design Patterns, Technical Writing, TDD, Coaching, Mentoring, Online Training, Professional Development, Agile