Skip to main content
Question
Anonymous
Asked a question 10 days ago

Does 'measure twice, cut once' work for software?

What are you looking for lately?

I think so. If we look at a typical software development value stream, 

Does 'measure twice, cut once' work for software?

We might be measuring many times before we 'cut' in development, or 'cut' by deploying, or 'cut' by releasing. There are tons of opportunities. We validate specs, designs, review code, run unit tests, run UAT, etc.

In software, it may be closer to measure tons, cut lots :]

 

Related Questions

No related questions.