export-nov-2018 - Yeret Agility

Uncertainty & the Scaled Agile Framework (SAFe™)
Gallery
Uncertainty & the Scaled Agile Framework (SAFe™)

Export, Export dec 2022, Scaled Agile

Uncertainty & the Scaled Agile Framework (SAFe™)

By Yuval Yeret|2016-02-05T14:44:40-05:00February 5, 2016|Export, Export dec 2022, Scaled Agile|

What is the connection between Uncertainty and the Scaled Agile Framework? Uncertainty is one of the core reasons we need to be agile. Different modes of Business/Requirements/Technology uncertainties impact our economic costs in product development - especially the potential impact of risk. The first principle of SAFe™ is “Take an economic view”. I frequently use my “uncertainty filter glasses” to take an alternative economic view. I find it helps Scaled Agile/SAFe™ practitioners/leaders understand both the need for Agility as well [...]

2

Risk-aware Product Development (a.k.a. Agile)
Gallery
Risk-aware Product Development (a.k.a. Agile)

Export, Innovation

Risk-aware Product Development (a.k.a. Agile)

By Yuval Yeret|2015-02-05T21:47:45-05:00February 5, 2015|Export, Innovation|

"There's no predictability/commitment in Agile" Over the years I've heard my share of these kinds of statements from various levels of executives: "When my guys run a product development release I really want to know what I will get at the end so I can make business plans accordingly" "In the old days when we ran projects we knew the timeline, we knew the scope, there were no surprises. These days it seems like the inmates are running the asylum. [...]

Comments Off

Guest Post – Is starting with Kanban really easier than with Scrum?

By Yuval Yeret|2012-05-08T03:57:07-04:00May 8, 2012|Change Management, Export, Guest Posts, kanban, Scrum|

Today I'm proud to host a guest post by another AgileSparks coach - Yael Rabinovitz. Yael has been working with several clients on Scrum implementations and has recently started using the Kanban Method (I wonder who gave her that crazy idea…) and is sharing her thoughts about the first steps into both approaches. Without further ado, here's Yael: Is starting with Kanban really easier than with Scrum? Kanban is often described as a way to achieve evolutionary change in [...]

Comments Off

Lean/Kanban approach to Teams

By Yuval Yeret|2011-10-22T08:38:42-04:00October 22, 2011|Agile, Blog, Export, kanban|

To Team or not to Team? If you look at the definition of Kanban or Lean, you wouldn't find teams anywhere there. If you look at the Agile Manifesto, you can find "The best architectures, requirements, and designs emerge from self-organizing teams" Scrum is quite clear about the topic (Quoting the Scrum Guide 2011) "Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams [...]

11

My thoughts on how Kanban and TOC Critical Chain relate

By Yuval Yeret|2011-10-10T21:25:58-04:00October 10, 2011|Blog, Export, kanban|

Background I recently had a short twitter chat with Catherine Swetel and Steven Holt about the relation between TOC Critical Chain and Kanban. This post will try to sum up my thoughts in a way that is a little bit more persistent, as well as add a bit more color and depth that is not possible in 140 characters. To start with, lets just make clear - I'm no expert at TOC or Critical Chain. I've done my share of [...]

3

Patterns for getting to a lower WIP level in a system – The Freeze, No New Work, Limit Later, and some Mashups…

By Yuval Yeret|2011-07-30T08:59:45-04:00July 30, 2011|Blog, Export, kanban|

Some of us have the luxury of designing processes for greenfield systems meaning there is no history/legacy to deal with. Typically though, we are dealing with Brownfield/Legacy systems - This usually means there is some work in the system already, there are outstanding commitments, and some existing queues between steps in our processes. I'm working with several clients that decided to start using a Kanban system to manage their work, and believe Limited Work in Process is key to improving [...]

3