2006 Lean Risk Software Engineering 
Herding Cats
MAY 10, 2019
Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.
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. México, 1 al 3 de Febrero de 2006. De Meyer, C.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
DECEMBER 16, 2017
Software Sizing, Estimation, and Risk Management: When Performance is Measured Performance Improves , Daniel Galaorath and Michael Evans , Auerbach, 2006. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.
LiquidPlanner
JUNE 1, 2016
In 2006 I left a great gig at Expedia to start LiquidPlanner with a fellow Expedia colleague, Charles Seybold. We didn’t really realize it at the time, but we built and launched the company using many of the concepts that Eric Ries later elegantly defined in his 2008 book The Lean Startup. Humble Beginnings. See how we do it.
Herding Cats
MARCH 11, 2017
The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.
Herding Cats
MAY 7, 2019
Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. COSMIC Software Estimation Approach,” Alain Abran, ICEAA Workshop, Portland Oregon, June 6?9, Monte Carlo Schedule Risk Analysis,” Intaver Institute, Inc. 61, September 2004.
Herding Cats
NOVEMBER 7, 2016
The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell. Software quality measurement,” Magne Jørgensen, Advances in Engineering Software 30 (1999) 907–912.
Expert insights. Personalized for you.
38 
Let's personalize your content