Scrum.org

NOVEMBER 24, 2021

This includes training, technical support, and preparation for new releases. How to use these insights in practice. One of the reviewers of this article, Maarten Dalmijn , noted that he missed “product discovery” as a core activity in the work by Bass (2018). It makes me wonder how we can do better.

2014 220

2014 2008 Technical Review 2019 220

Herding Cats

MAY 10, 2019

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 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.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

So in the end, if we are to make a decision in the presence of uncertainty, we MUST make estimates to develop a reliable shipping date while producing an accurate and precise estimate of the cost, schedule, and technical performance of the product shipped on that date. Eggstaff, Thomas A.

2003 46

2003 2014 2015 2011 46

Teamweek

DECEMBER 8, 2023

Common causes for skills mismatches are poorly written job description ads, gaps in the hiring procedures, overemphasizing job experience over skills, and emerging technologies. they have the skills needed to succeed in a tech-focused manager-level position and their employer isn’t using those skills effectively).

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. Why Do Information Technology Projects Fail?” Perry, and Dieter Stoll, ICSE 2000.

2014 45

2014 Aerospace 2011 2013 45

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