Ann Wong Hi Ann, no I think as mentioned the users just loves 'coin' so gets utility from the very first coin and each coin after. But you raise a good point and you could replay this with an MVP of several coins all stacked followed by a number of increments and see who comes out top. Also this system allows faster user feedback of deliverables, I've played it where halfway through the market shifts and copper coins aren't wanted anymore, try that and play again! Etc. Etc.

He he, yes agile teams defo need to be prepared to pivot/spin/be agile right, and that then affects tool-choice and everything like that. I think that's David who said it, he's pretty clued up chap, and I think he was playing devil's advocate. There is some truth in what he says though, and having stories/spec/requirements change too much can break a team's morale. Hopefully a sensible PO and Scrummaster can give some level of stability. Even if the product is based on fickle Hollywood celebs or something there should be some continuity that can be abstracted. Easier said than done, I've observed and even been in Scrum teams that have let the Sprint Backlog get changed and added to as we thought we were doing a favour. Sometimes with hindsight we'd have pushed the discipline and forced the pain on them until the next Sprint Planning when they'd have hopefully learnt their lesson and refined the backlog well and brought their A-game to sprint planning. What's your experience Carl?

While change is inevitable and often desirable, changes at the iteration boundary are less wasteful. A little disciple and good will by all parties can keep value flowing

Thanks Hugo, I am going to make some more live coaching game videos in the near future... meanwhile I'm just going through some Product Owner perspective videos, team/organisational change, and then a video questioning the evidence of agile/waterfall/other methodologies. Please Subscribe for notifications.