Remove 2008 Remove Software Engineering Remove Software Review
article thumbnail

What Makes A Good Product Owner?

Scrum.org

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). The Sprint Review is an excellent opportunity to engage in product discovery. Judy & Krumin-Beens (2008) offer an interesting perspective on this in a case study. is more effective.

2014 233
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. 2014 ; Young & Jordan, 2008 ; Russo, 2021 ).

Agile 225
Insiders

Sign Up for our Newsletter

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

article thumbnail

Assume a Spherical Cow

Leading Agile

In 2012, I wrote a blog post entitled “Delivering provably-correct code.” ” In it, I suggested several approaches developers could use to gain high confidence that their code would be suitable for release. When they talk about the “correctness” of software, they’re talking about two different things.

article thumbnail

How to Start a Career in Project Management: Answers to FAQ

Epicflow Blog

According to PMI’s Job Growth and Talent Gap in Project Management 2017-2027 , organizations’ need for project talent has significantly increased since their previous investigation in 2008. In fact, modern project management software can prevent a project from a lot of issues and ease a PM’s job. .

article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp.

2003 46
article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

Microeconomics is applicable to the development is software systems. 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."

article thumbnail

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

Herding Cats

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. What factors lead to software project failure?” All for the want of a nail.

2014 45