Scrum.org

JANUARY 27, 2021

For many people, the traditional project management methodologies (see PMI / PRINCE2) are the root of the problems that birthed Waterfall. This was the birth of the Agile movement with the Scrum Framework (1993), the Agile Manifesto (2001), and later Kanban (2004). I assert that this is the tip of the iceberg.

2001 222

2001 Software Review Technical Review Underperforming Technical Team 222

Herding Cats

MARCH 11, 2017

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.

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 920, November 2004. 3 September 2004, Heiot Watt University, Association of Researchers in Construction Management , Vol. 255, April 2010. Talat Birgonul, and A. 85 1 Feb 2019. “An

Risk Management 38

Risk Management Risk Technical Review 2004 38

Herding Cats

MAY 11, 2019

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. 920, November 2004. 255, April 2010. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2004 35