Category: Scrum

Paradigm shift: Slicing Features

Adventures in slicing features.

Teams need to learn the artful skill of slicing features into stories a related to their business context and domain purpose. A typical anti-pattern is for teams to waterfall their iterations, as described in the next two scenarios.

The first iteration we will gather all the requirements, the second iteration we will design, the third and fourth iterations we will build, and the fifth iteration we will test…and so on…

interwaterfall
This is an inter-waterfall anti-pattern. It is essentially a pure waterfall approach chopped up into smaller time boxes.

Another derivation of this anti-pattern is to order up another form of phony business agility and/or Scrum.

In this iteration we will pull “requirements gathering” stories first. When those are all finished, we will pull the “design stories”, and then “build” stories…

intrawaterfall.png
In this case, it is an intra-waterfall anti-pattern.

The next common anti-pattern related to intra-waterfall is for dev team members to pull stories and work on them independently. This is a siloing ant-pattern, indicating the team is not cross-functional and is simply a collection of silos and individual waterfalls. Continue reading “Paradigm shift: Slicing Features”

Advertisements

The Knowledge Worker Factory

Does it really exist?

Or are we still working in the blacksmith shop? Will it take AI to bridge the gap?

In Lean manufacturing companies that build physical things have been able to improve quality consistently and dramatically since the dawn of the industrial age.

Here many of us are in the post-industrial, Information Technology or Digital Age.

When we change the channel to knowledge work, companies struggle mightily to match the pace of quality and outcomes of physical manufacturers, even to this day. Why?

XP, Agile, Scrum, DEVOPS, Kanban for Software, Scaling Frameworks

Are these practices, methods, frameworks, and guidance really helping the knowledge worker factory catch up with companies that make physical things? Perhaps there is some evidence to support the claim. Continue reading “The Knowledge Worker Factory”

Lean-Agile Team Metrics Starter Kit

The fourth tool created to date by blogagility.com for the community!

This handy starter kit is for Scrum masters that are using the Shu Ha Ri paradigm for team development. Good coaches help new teams avoid the pitfalls of added complexity involved in “Agile Lifecycle Management Tools” and instead push for good old-fashioned manual BVIR’s, Kanbans, Scrum boards, et cetera. Change is hard enough in a CAS without adding to the problem by also complicating the way of working. Continue reading “Lean-Agile Team Metrics Starter Kit”

Walk the Kanban while Scrumming it

Artificial Limitations are not controls

Don’t limit your team to using just Scrum or Kanban. Don’t even limit yourself to using watered down versions of a combination of Scrum and Kanban. High-performance teams master both the empirical process framework and controls called Scrum, and the use of Kanban (system; Lean).

Continuous Learning (The Three Ways) & Empiricism

Continuous learning teams know how to scale these frameworks and systems using the SAFe and other scaling frameworks to suit the needs of the business and customer solution context (value). Learning teams know how to drive DEVOPS culture and practices through self-organization and self-management.

Scrumming it, the next step

If you are practicing Scrum, and using a Kanban to support the process framework it is helpful to walk the board during the Daily Stand-up (Scrum). Do this a few times a week rather than asking the three questions every day.

WalkingtheKanban

#Scrum #Kanban #Agile #Lean #SAFe #scalingframeworks

Scrum 2.0 – The Scrum Manager

The new new new Scrum.

Gone are the days when a Scrum master was the facilitator of a process framework.

New new new Scrum 2.0 brings in a new perception and fallacious understanding of the Scrum master role as a manager. The Scrum Manager. Continue reading “Scrum 2.0 – The Scrum Manager”

The Scrum Song – vlog – Coaching Tip #9

Lot’s of instructors will tell you about the common escape clause for Scrum, “Scrum Is Simple but Not Easy.” I read another article that makes a much more valid point, “Scrum is easy, people are hard.” The latter diving into how people learn and more importantly, how they change. Or not.

Any two-day course is only the beginning. In two days, you are getting exposed to a breadth of knowledge about Scrum. If you are lucky enough to learn Scrum from a provider that includes Bowman’s Back of the Room and/or Gamification techniques then you will also be exposed to a surface level experience of how Scrum is intended to work.

Continue reading “The Scrum Song – vlog – Coaching Tip #9”