Remove 2013 Remove Agile Remove Software Engineering Remove Strategy
article thumbnail

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

Scrum.org

What is the business case for Agile teams? We think we do well to base our beliefs about Agile more on evidence. This post is our attempt to bring an evidence-based perspective to the business case of Agile teams. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams.

Agile 210
article thumbnail

What Makes A Good Product Owner?

Scrum.org

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. What strategies make them more?—?or Van Waardenburg & Van Vliet (2013) offer a case study in a large organization and conclude that “The Project Manager focuses on the ’how’ of a project, the Product Owner focuses on the ’what’”.

2014 216
Insiders

Sign Up for our Newsletter

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

article thumbnail

Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. 4, 2013.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

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.