Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. Kirkeboen, G., &

2003 46

2003 2014 2015 2011 46

Wrike

MARCH 14, 2018

These results aren’t surprising given the recent surge in attention to gender issues in workplaces, from the #MeToo movement over the past few months to Sheryl Sandberg’s 2013 bestseller Lean In. But they still hit a nerve. I have to go to extremes to prove myself every single time I walk into a new setting.”

Underperforming Technical Team 36

Underperforming Technical Team 2018 Engineering 2013 36

Herding Cats

MAY 7, 2019

“Effort Estimation of Use Cases for Incremental Large-Scale Software Development,” Pareastoo Mohagheghi, Bente Anda, and Reidat Conradi, Proceedings of the 27th international conference on Software engineering. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. 5, October 2013.

Estimate 40

Estimate Software Review Software 2012 40

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.

Estimate 64

Estimate 2005 2006 2013 64

Herding Cats

MAY 10, 2019

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. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

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. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Leading Agile

JUNE 20, 2018

I can imagine some software engineers taking umbrage at that comment. In 2013 I described a conference session Pelrine facilitated in which we explored this concept in 2009. Even if they were invited to the table, they would have relatively little to contribute.

Agile 103

Agile 2001 Defining 2009 103