Blog

Agile

Iterating faster with SAFe

Here’s a frequently asked question in the SAFe community: I wanted to understand what SAFe says about someone who wants to go faster than 2 weeks of iteration? I mean the whole PI concept is based on 5 iterations worth of planning. What if a team/organization wants to develop and synchronize faster than 2 weeks? Is speed going to be compromised by following the standards of PI cadence?

Here’s my take:

Adjusting Cadence Length in SAFe – Can you? Should you?

Read More »
Kanban

Avoiding the GanttBan

Using Kanban to help organizations evolve means we frequently use it in situations where predictability is important BUT good flow is not immediately attainable, where

Read More »
Agile

Scaling Agile Reading List

Scaling Agile Reading List Dave Snowden “Put brutally SAFe Implementation Roadmap – Scaled Agile Framework Implementing – Scaled Agile Framework portfolio+kanban Here Be Dragons –

Read More »
Agile

Lean/Kanban approach to Teams

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

Read More »
Kanban

Kanban Service Level Expectations and how to use them in Scrum

One of the new concepts we introduce in the Kanban Guide for Scrum Teams is the Service Level Expectation, defined as:

An SLE forecasts how long it should take a given item to flow from start to finish within your workflow. The SLE itself has two parts: a period of elapsed days and a probability associated with that period (e.g., “85% of work items will be finished in 8 days or less” which can also be stated as “8 days with 85% confidence/probability”).

Read More »

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience