Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. 3, March 2002. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 85 1 Feb 2019. “An 11 November 2002. Software Engineering Institute, January 1996.

Risk Management 38

Risk Management Risk Technical Review 2002 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. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Planio

JULY 22, 2020

If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Published date: 2019 (Updated edition). Published date: 2019 (Updated edition). Published date: 2019.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Leading Agile

FEBRUARY 11, 2019

When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. How can the same principle be a good idea in 2002 and a bad idea in 2019? I’d like to consider the following in this post: Sustainable Pace. Sustainable Pace.

Agile 97

Agile Underperforming Technical Team Software Review Technical Review 97