Inloox

JULY 1, 2021

Origin and Basic idea The Scaled Agile Framework was introduced in 2011 by Dean Leffingwell with the goal of taking advantage of existing agile methodologies and scaling them across the entire organization. Lean Agile Leadership: Managers are the very core of lean agile development and business agility.

Technical Review 100

Technical Review Lean 2011 Cadence 100

Agilemania

DECEMBER 6, 2021

It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. SAFe is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, Systems Thinking, and DevOps. A SAFe agilist is the person responsible for Lean-Agile transformation.

Lean 98

Lean 2011 Cadence Innovation 98

Agilemania

JANUARY 24, 2022

The cadence of development of multiple teams. These frameworks also encourage you to use Lean principles to optimize your flow. In 2011, Dean Leffingwell codified SAFe, the Scaled Agile Framework , to help bring the success that small teams have enjoyed with various agile methodologies such as Scrum or XP but scaled to the enterprise.

Agile 98

Agile Lean 2011 SCRUM 98

International Institute for Learning

MAY 16, 2022

Operating in a fast-paced world with threats and opportunities requires flexible responses with adaptive strategies, fast performance, and funded innovation. Intuit’s innovation success was also featured in Eric Reis’ book The Lean Startup (Crown Business, 2011). Intuit’s shares also doubled in five years.

Artificial Inteligence 59

Artificial Inteligence Agile Cadence 2011 59

Scrum.org

FEBRUARY 22, 2021

In the attempt to fill Scrum’s product discovery void, product delivery organizations regularly turn to other agile frameworks like lean UX, jobs-to-be-done, lean startup, design thinking, design sprint—just to name a few. Scrum’s Achilles Heel: Product Discovery.

Software Review 139

Software Review Technical Review Cadence SCRUM 139

Digite

MARCH 12, 2018

Starting in 2007 when we moved from being a waterfall shop to 2011 when we adopted Kanban, we have ourselves mastered a number of challenges that the question above presents. I have spoken about our own experience in a number of conferences worldwide and found it resonating with a lot of people – so we are not alone in this.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154