Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991.

Software Developers 46

Software Developers Software Development Estimate 2006 46

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. 255, April 2010. 24, 2010. “A México, 1 al 3 de Febrero de 2006. 3, March 2002.

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

Herding Cats

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. How to Develop Credible Cost & Schedule Estimate.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. And if the competitor is shipping software with greater value, how does the Cone impact that? 37-48, 2007. 37-48, 2007. Thesis, University of Southern California, August 2012.

2007 34

2007 2012 2009 2010 34

Wrike

AUGUST 14, 2020

Anderson is often credited as being the first to implement Kanban in software development in 2005. His book on Kanban , published in 2010, is still one of the most comprehensive resources out there for technology-focused projects. Features to look out for in Kanban software. Automated workflow capability.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] IEEE Software, March-April 2009, pp.

Technical Review 28

Technical Review 2005 Estimate Software Review 28