Objective Thoughts

Subscribe to our blog Net Objectives Thoughts Blog

Iteration versus Iteration-less Scheduling

August 22, 2011 — Posted by Ken Pugh

In both Kanban and Scrum, there is an emphasis on developing software in small increments of requirements (stories). However the different approaches to scheduling between iteration-based Scrum and iteration-less Kanban can cause different behaviors to emerge from teams. These behaviors do not exist on all teams, but have been observed on many. One cause is that with iteration-less development, metrics and estimates can impose less overhead for the same net result.

Share this:


The Importance of Mindset

July 26, 2011 — Posted by Al Shalloway

I have been doing Agile for over a decade. During this time, I have seen many different ways of thinking about what Agile is. One way is to think that there is only one kind of Agile and that there is a large collection of methods to choose from as you feel appropriate. Another way is to realize that there are many different mindsets in the Agile community and that these mindsets are what give rise to the different methods.

Share this:


Kanban – An Integration of Deming, Ohno, TOC, Satir and Nonaka

July 14, 2011 — Posted by Al Shalloway

My alternative title to this blog was "If You Say Kanban Isn't About People, then You Don't Know What Kanban Is." But that sounded too much like a rant. However, I have to admit, much of this blog is a rant. Smile

Share this:


Kanban in a Nutshell

June 25, 2011 — Posted by Al Shalloway

I assert the following (please verify with your own evidence from your past):

  1. Time from getting information until using it creates new work (one has to redo the information or one works from old information which results in rework)
  2. Time from making an error until detecting it creates new work (e.g., a bug found immediately takes little time to fix compared to a bug found weeks later – that additional work is created by the delay)
  3. Shortening the feedback times will shorten these delays and therefore lower the amount of work to be done

Share this:


Reflections on the SQE Better Software/Agile Development Practices Conferences

June 14, 2011 — Posted by Al Shalloway

I had a great time at the Better Software/Agile Development Practices West in Las Vegas last week.  I gave 7 of the 9 talks/courses/tutorials Net Objectives presented. I would say the most interesting thing about the conference was the large number of companies using Scrum who's progress had somewhat plateaued and the number of companies who wanted to go Agile that couldn't see how to use Scrum to do it. I call these patterns of failure. Not that they hadn't had success, but were failing to maintain it.

Share this:



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
Guy Beaver
Business and Strategy Development, Executive Management, Change Management, Lean Implementation, Transitioning to Agile, Lean-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, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Marc Danziger
Business and Strategy Development, Change Management, Team Agility, Online Communities, Promotional Initiatives, Sales and Marketing Collateral
Scott Bain
Analysis and Design Methods, Agile Design and Patterns, Software Design, Design Patterns, Technical Writing, TDD, Coaching, Mentoring, Online Training, Professional Development, Agile