Scrum.org

FEBRUARY 4, 2022

This post is for anyone who wants to inspire, change or influence others through their efforts as professionals, with emphasis on the latter. I think you should read this post, and take it to heart when you write content that is aimed at influencing others. What is the optimal size of a team? Is scaling always a bad idea?

Agile 181

Agile Software Review Underperforming Technical Team Technical Review 181

Scrum.org

OCTOBER 19, 2022

Another approach is to track many organizations over time as they adopt Agile methodologies, while also measuring anything else that could influence their results other than agility itself. Hoda, Stuart & Marshall (2011) interviewed 30 Agile practitioners over a period of 3 years. Journal of systems and software , 81 (6), 961–971.

Agile 198

Agile 2010 2013 2008 198

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. The Future of Systems-and Software Development. Laplante, ACM SIGSOFT Software Engineering Notes , Vol.

Estimate 64

Estimate 2006 2005 2013 64

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. 9, Issue 3, No.

Estimate 40

Estimate Software Review Software 2012 40

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. 5, September/October 2011. Software Engineering Institute, January 1996.

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. 5, September/October 2011. Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2018

If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

Software Developers 34

Software Developers Software Development Risk Management Risk 34