|
|
The Lean Product Playbook:
Most of the time, software development tasks take longer than estimated.
|
203 |
|
|
The Lean Product Playbook:
When the risk of failure or the cost of making changes is too high, it’s better to spend more time gaining a higher level of confidence before starting implementation.
|
204 |
|
|
The Lean Product Playbook:
The idea of hard launch dates is tenuous with any Agile methodology.
|
217 |
|
|
The Lean Product Playbook:
When… organizations transition to Agile, many still hold on to a waterfall mindset regarding their product backlog.
|
217 |
|
|
The Lean Product Playbook:
If your organization would have a hard time letting go of the security blanket of hard deadlines, then Scrum is probably a better fit than Kanban.
|
217 |
|
|
The Lean Product Playbook:
There is significant value in everyone on the team hearing the same thing at the same time about how the product development process should work.
|
218 |
|
|
The Lean Product Playbook:
…product development is a team sport.
|
219 |
|
|
The Lean Product Playbook:
Having your product backlog rank ordered makes it clear which item should be done next. The trick is to be both rigid and flexible when it comes to prioritizing your backlog.
|
220 |
|
|
The Lean Product Playbook:
Finding defects as soon as possible is a Lean principle that helps reduce waste.
|
222 |
|
|
The Lean Product Playbook:
A major bug that you don’t detect until after you launch your product is much more costly than one found during development.
|
222 |
