Remove Estimate Remove Manufacturing Remove Risk Management Remove Software Development
article thumbnail

Kanban vs. Scrum: What’s the Difference?

ProjectManager.com

Kanban and scrum are agile project management methodologies that can be used for similar purposes, but each has its unique pros and cons. As a project manager, it’s important to understand the difference between kanban and scrum so you can determine the best approach for your team. What Is Kanban?

SCRUM 413
article thumbnail

Basis of Estimating Software Development

Herding Cats

The estimating of software development is both straightforward and complex. When it is suggested that estimating is hard, of no value, and unnecessary, always ask what principle is used to support that claim? Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Principles of Cost and Schedule Estimating

Herding Cats

One of the 4 summary root causes of project performance failures is Unrealistic Cost and Schedule Estimates based on inadequate risk-adjusted growth models. Managing in the presence of uncertainty is standard business practice. If you have no uncertainty, then estimates provide no value. This is how business works.

article thumbnail

When to Estimate and When Estimates aren't Needed

Herding Cats

Paul Boos has a post about estimating and makes a case for the Principles of when NOT to estimate. This struck a cord around a bigger topic - the inversion of estimating. When should we NOT estimate? Then on to the original conjecture for No Estimates from Paul's post. That is, to make decision with “No estimates”.

article thumbnail

Risk Management Resources

Herding Cats

Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. requires making estimates) ? Risk Management Papers. “A

article thumbnail

Small Batch Sizes are NOT Risk Management

Herding Cats

There is a popular fallacy in the Agile community that small batch sizes are Risk Management. What small batches do is provide information that informs risk management at a fast rate. This analog signal is the underlying dynamics of the software development process. Small batch sizes answer the question.

article thumbnail

Aleatory and Epistemic Uncertainty in Software Development Projects

Herding Cats

All software development projects operate in the presence of uncertainty. The design and development of software must rely on estimation, forecasts, and predictions based on an idealized understanding of what is an unknown (but knowable) understanding of reality. This is a Risk Communication issue.