Remove 2010 Remove Prince2 Remove SCRUM Remove Software Developers
article thumbnail

Risk Management Resources

Herding Cats

255, April 2010. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 24, 2010. “A Project Risk Management: Lessons Learned from Software Development Environment,” Y. 920, November 2004. Kwak and J. Yamamoto, and K.

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. 24, 2010. “A Kwak and J.

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.

2003 46
article thumbnail

Complete Collection of Project Management Statistics 2015

Wrike

3% use PRINCE2. [4]. Most Popular Agile Tools and Processes: Scrum – 43%. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. 66% of organizations use PM software to communicate with clients. [17]. Between 2010 and 2020, 15.7

2015 60
article thumbnail

Webinar Recap: Agile Series Part 1 – Understanding & Incorporating Agile Project Management

MPUG

So a lot of times people are like, “Oh my gosh, I’m a waterfall guy or I’m an agile girl,” or, “Hey, listen, I’m a Prince2 person.” And so this is where agile kind of fits in and isn’t just necessarily only for software development. But it is clearly not limited to just software.

Agile 40