I think Ward hits more fundamental points (e.g. this page suggests the waste lies in not consulting a domain expert, whereas Ward suggests the waste lies in the hand-off it takes to consult a domain expert in the first place, rather than have the development team become domain experts. Or when this page talks about building the wrong product, Ward talks about wishful thinking and being gut-driven rather than data-driven.)
Here are some of the wastes I remember making notes on from Ward's book. If you want more details on any, I'm happy to answer questions.
- Scatter: disruption in communication, communication barriers, changing priorities, distractions.
- Hand-off: essentially when there's a common goal, but different people are in charge of knowledge, responsibility, action, and feedback. Important information disappears into black holes during hand-offs.
- Useless information: reports, updates, analysis, etc. that is created not because it helps the customer, but because someone wants it to feel good.
- Waiting: over-utilised resources cause queues which lengthen feedback, decrease urgency, increase variability of performance, etc.
- Wishful thinking: making gut-driven rather than data-driven decisions, planning further out than you can reliably predict, reducing uncertainty too soon.
- Discarded knowledge: spending time and effort building knowledge, but then filing it away and never reusing it.