A slight spin on that assumption that I've seen in some lean startup materials is to assume that "software delivery is constant and guaranteed" - which is used to help move the identification of risk away from technology and towards the business viability.
In that case, I think it is somewhat useful, but speaking as a software developer - it is very rarely the case that a software project goes as smoothly and reliably as a fancy pitch deck makes it out to be. It is easy to say things like "small iterations", "continuous delivery", "move fast", etc but much harder to, you know, do them. Any old team thrown together off the street is not going to have that skillset to achieve that.
I don't think it entirely discounts the ideas or concepts, but I certainly gives me pause.
In that case, I think it is somewhat useful, but speaking as a software developer - it is very rarely the case that a software project goes as smoothly and reliably as a fancy pitch deck makes it out to be. It is easy to say things like "small iterations", "continuous delivery", "move fast", etc but much harder to, you know, do them. Any old team thrown together off the street is not going to have that skillset to achieve that.
I don't think it entirely discounts the ideas or concepts, but I certainly gives me pause.