Explaining To Stakeholders how Agile will help

As a part of my recent CSM course, i have encountered a great term for dealing with huge projects.

 

Sashimi slicing.... like thinly cut sushi. geoff burns article  mark monster article also rowan bunnings article about sashimi smells (!)

but i just finished reading this article by Mike Griffiths

A great explanation with diagrams of why you are better off with your agile team all on the same page, without your BA running ahead with the customer to get through the product backlog, meaning that when your dev and QA team run into problems with what they've received, the customer and BA don't have to backtrack or redo the work they've already done.

also some ideas about getting your velocity sorted out and orientating your team all in the same direction.

the things i managed to gleam out of this article are kind of missing the original point about managing velocity fluctuations. i suppose as i'm an agile beginner these sorts of things will become more visible to me as i get some more scrum mastering time under my belt