Remove 2011 Remove Cadence Remove Lean Remove Risk Management
article thumbnail

Comprehensive Guide to Becoming A SAFe Agilist

Agilemania

Added to this is the complex problem of managing multiple agile teams. It was, for this reason, Dean Leffingwell decided to conceptualize SAFe® in 2011. SAFe® is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, Systems Thinking, and DevOps.

Cadence 98
article thumbnail

Disciplined Agile & SAFe

International Institute for Learning

They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM.

Agile 59
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Mastering the (new) Agile Coaching Mindset for the 4th Industrial Revolution (4IR)

International Institute for Learning

For the Agile community practitioners, managing change and uncertainty to deliver on strategic goals is nothing new. The former grows by adding scale and complexity, which must be managed. Today’s, and tomorrow’s, market-makers are more like living organisms.

article thumbnail

Product Discovery Anti-Patterns Leading to Failure

Scrum.org

And this is precisely the point: The Product Owner miraculously identifies what is the best way to proceed as a Scrum Team by managing the Product Backlog. I do believe that a separation between product discovery on the one side (product management), and product delivery (Scrum teams) on the other side is no longer a viable approach.