@ledocool431 @Jain IIRC from when i took the lectures from one of the original scrum guys

- the client shows up in the pre-sprint to say these are the things i want done and a relative level of importance for each thing
- the scrum master says 🆗 is this what you want and reminds them they won't be hearing from them again for 1-4 weeks (iteration times vary)
- client is then locked out of the process until the sprint is over
- scrum masters job is mostly to do daily stand-ups (checking in with the work group) and the rest of the time to resolve out-of-band blockages

the work group is really never supposed to be bothered by management or paperwork at all and the requirements are supposed to be moderately stabilized so they can actually write the code before the requirements change.

most companies want the outcome of that (higher productivity) but are unwilling to pay for it (shutting up for 1-4 weeks at a time)