Remove 2016 Remove Reference Remove Software Engineering Remove Technical Review
article thumbnail

What Makes A Good Product Owner?

Scrum.org

Note that Bass calls this “Groom” in reference to “Product Backlog Grooming”. This includes training, technical support, and preparation for new releases. 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). rather than on your own”.

2014 223
article thumbnail

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

So we went to Google Scholar and searched for review articles. 2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. A strength of such a review is that it allows for the identification of patterns across many studies. References. Cardozo et. Cardozo, E.

Agile 217
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Without a Root Cause Analysis, No Corrective or Preventive Action is Credible - Part 1

Herding Cats

Part 2 will take these Root Analysis principles and apply them to actual software problems, and the fallacies that simple and simple-minded corrections will fix anyting - stay tuned. References . When you hear a solution without references - reference that is not self-referenced or simple-minded reference, stop listening or reading.

2014 45
article thumbnail

Skills Mismatch | What Is It & How to Bridge the Gap

Teamweek

That’s what a skills mismatch is — it refers to a noticeable gap between the skills of the employees and the skills actually needed for the particular job. Common causes for skills mismatches are poorly written job description ads, gaps in the hiring procedures, overemphasizing job experience over skills, and emerging technologies.

article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

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.

article thumbnail

Software Estimating Resources

Herding Cats

“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. & Zein, S.,

article thumbnail

Estimating is a Learned Skill

Herding Cats

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Fixed price without fixed specification,” Magne Jørgensen, Simula Research Laboratory, 15 March 2016.