Scrum.org

NOVEMBER 24, 2021

Sverrisdottir, Ingason & Jonasson (2014) interviewed Product Owners from different organizations that there are often multiple Product Owners for the same product, even though the Scrum Guide prescribes against this. . Sverrisdottir, Ingason & Jonasson (2014) also found no standard for how much time Product Owners spend with teams.

2014 219

2014 2008 Technical Review 2019 219

Scrum.org

OCTOBER 19, 2022

Is it really that important that they are autonomous, able to release frequently, interact closely with stakeholders and spend all that time on continuous improvement? However, the sheer effort involved is so gargantuan that this is close to impossible. 2014 ; Young & Jordan, 2008 ; Russo, 2021 ). Or is all that just hype?

Agile 213

Agile 2010 2013 2008 213

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. 1, March 2014.

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. 1, March 2014.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

FEBRUARY 9, 2019

This is a closed loop system optimization process applied to all the projects we work. 1] "Systems Engineering Strategies for Uncertainty and Complexity," MITRE Corporation, Systems Engineering Guide. [2] 6, No 5, October 2014. [3] Rarely are software engineers working on science experiments. Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42