article thumbnail

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

Scrum.org

Several empirical studies have indeed found that teams with a frequent delivery strategy are more likely to deliver successful project outcomes and satisfy stakeholders than teams that do not ( Chow & Cao, 2008 , Jørgensen, 2016 ). References. SCRUM and productivity in software projects: a systematic literature review.

Agile 206
article thumbnail

What Makes A Good Product Owner?

Scrum.org

Note that Bass calls this “Groom” in reference to “Product Backlog Grooming”. References. In Proceedings of the 40th International Conference on Software Engineering: Companion Proceedings (pp. Groom : The breakdown and clarification of work on the Product Backlog, as well as their acceptance criteria. Beecham, S.,

2014 213
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

Top 3 Essential Technical Project Manager Skills

Wrike

Simply put, a technical PM plans, schedules, and manages IT-related projects – e.g., projects that support software engineering, app development, network security… you get the idea. In fact, a 2016 article in CIO listed technical knowledge as the most in-demand project management skill. Essential project management skills.

article thumbnail

Risk Management is How Adults Manage Projects

Herding Cats

But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. No References? Verlag, 2016. Project Risk Quantification: A Practitioner’s Guide to Realistic Cost and Schedule Risk Management , John Hollmann, Probabilistic Publishing 2016. Alexandre Vidal, Springer?Verlag,

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

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. For instance, an individual having a software engineering degree might not be a great fit for a customer service role.