Remove Case Study Remove Innovation Remove Software Engineering Remove Technical Review
article thumbnail

Five reasons why Scrum is not helping in getting twice the work done in half the time

Scrum.org

It is not only because the book is good, but I felt connected with one of the case studies. They got the idea of increasing the complexity of dependency management and longer lead time due to the handoffs having individual accountability. Bad technical practices. I went through the book and loved it.

article thumbnail

5 Agile Methodologies for Project Managers that are not Scrum Framework

Project Pulse Journal

Each methodology is relevant in its own right, unlocking potential, driving innovation, and ensuring that your projects meet expectations. Feedback Loops – Incorporate regular meetings to review and adapt your workflow based on feedback. Agile methodologies offer a path to mastering these challenges. What Makes Kanban Agile?

Insiders

Sign Up for our Newsletter

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

article thumbnail

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

Scrum.org

What do scientific studies have to say about the business outcomes of Agile methodologies, as well as the factors we just mentioned? 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. Cardozo et.

Agile 198
article thumbnail

Risk Management Resources

Herding Cats

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.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

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.

article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

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
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.