Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. De Meyer, C.

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

The IIL Blog

JANUARY 24, 2024

Most of these roles were based on aspects of IT operation, such as mainframe operation and maintenance, which later evolved into software development and commercialisation. ITIL v2 followed this in 2001, ITIL v3 in 2007, and ITIL 4 in 2019. Service Integration and Management, aka SIAM, was developed in 2005.

2001 78

2001 2007 2024 Information Technology 78

Leading Agile

JUNE 27, 2018

The Joke, as recounted in this blog : Milk production at a dairy farm was low, so a farmer wrote to the local university to ask for help. In 2012, I wrote a blog post entitled “Delivering provably-correct code.” This is not an isolated case, and most of what passes for research in software engineering is horrible.

Software Review 88

Software Review Technical Review Underperforming Technical Team 2007 88

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. 153, 2007 “Overspend?

Estimate 40

Estimate Software Review Software 2012 40