Remove Books Remove Estimate Remove Software Remove Software Engineering
article thumbnail

Kanban History: Origin & Expansion Across Industries

ProjectManager.com

Kanban history has informed everything from manufacturing to software development. For those unsure what kanban is, we’ll first explain the kanban system and then go into kanban history from its development to its uses in manufacturing, project management and software development.

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? Let's start with some books. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.

Insiders

Sign Up for our Newsletter

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

article thumbnail

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

Scrum.org

When I saw the book “Art of doing twice the work in the half time,” Dr. Jeff Sutherland wrote, my reaction was like how someone can claim that? I went through the book and loved it. It is not only because the book is good, but I felt connected with one of the case studies. You can read the original post here.

article thumbnail

Why Johnny Can't Estimate? (Update)

Herding Cats

I work in a domain where engineered systems are developed for complex software-intensive system of systems. These systems are engineered with a variety of development methods. There is a discussion of the conjecture that estimates are a waste, estimates can't be done, estimates are evil, estimates must be stopped immediately.

article thumbnail

Estimating Accuracy Mathematics

Herding Cats

In the estimating business, like many things in project management, there is confusion about principles, practices, and processes. A good estimation approach should provide estimates that are within 25% of the actual results, 75% of the time. The book this statement comes from is Conte, S. Dunsmore and V.Y.

article thumbnail

Why Johnny Can't Estimate?

Herding Cats

I work in a domain where engineered systems are developed for complex software-intensive system of systems. These systems are engineered with a variety of development methods. Since all risk comes from uncertainty - reducible (Epistemic) and irreducible (Aleatory), estimating is a foundation of all we do.

article thumbnail

How to Estimate Any Software Problem

Herding Cats

ways to make decisions with No Estimates. Uncertainty of course is present in all software development work both reducible and irreducible uncertainty. can we make a decision in the presence of Uncertainty without making an estimate of the impact or outcome of that decision? An estimate is. It's a fallacy.