article thumbnail

Top 10 Scaled Agile Framework (SAFe) Tools [2022]

Agilemania

SAFe is a knowledge base of proven, integrated principles, practices, and competencies for attaining business agility using Lean, Agile, Systems Thinking, and DevOps. The core of SAFe is based on four bodies of knowledge which are agile software development, lean product development, systems thinking, and DevOps.

2022 91
article thumbnail

The Roles and Responsibilities of a SAFe Agilist You Never Knew

Agilemania

Be it monitoring and control, collaboration, stakeholders onboarding, change management, and governance methods, the problems only keep increasing. SAFe is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, Systems Thinking, and DevOps. Conclusion.

Lean 98
Insiders

Sign Up for our Newsletter

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

article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. 12, 2008. “A

2003 46
article thumbnail

Risk Management Resources

Herding Cats

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Project Risk Management: Lessons Learned from Software Development Environment,” Y. Recent trends of Risk Management in Software Development: An Analysis,” Raghavi Bhujang and V.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. 255, April 2010. 920, November 2004. Kwak and J.