Herding Cats

MAY 10, 2019

requires making estimates) ? 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. 3, March 2002. 11 November 2002. Dorofee, et.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

requires making estimates) ? Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. 3, March 2002. 11 November 2002.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

APRIL 13, 2018

Estimation locks down choices early through upfront t decision making, #NoEstimates preserves options. Real Options can be used to address the gap found in traditional capital budgeting methods. Managing Requirements for Business Value," John Favaro, IEEE Software , March/April 2002. 72, 2nd Quarter, 2008, pp.

2008 32

2008 2002 Estimate Software Engineering 32

Herding Cats

APRIL 4, 2019

All making things smaller dos is show that you're late, over budget, and what you're building (Technical Performance Measures) doesn't work faster. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. No References?

Risk Management 43

Risk Management Risk 2003 2011 43

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. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. It’s often considered good practice to involve security specialists early in each project, rather than waiting until most of the time and budget have been used up before they have a chance to perform a review.

Software Review 78

Software Review Software Technical Review Development Team Review 78