Thanks for sharing! I know it isn't a product company nor an agency.
I'm not a fan of the terminology hacking, if you want to do your own thing, by all means do it, but don't misuse existing terms that have precise meanings, and get them to mean something else.
I understand then it doesn't sound as cool anymore, but it's far better than teaching people wrong things and saying they are right outside of a business context (which I don't believe is a strong argument because Scrum is defined outside that context too as a framework for solving complex problems).
I am happy to help review your materials for accuracy, but you really shouldn't be teaching these things.
I have had very good success in using the Scrum Facilitators template for exactly the reasons you state.
thanks Deanna!!
Thanks for sharing, I will let Erik know!
Keep up the good Maarten and I can not wait for your Miro template to be out soon. How are we going to get it easily ? On Miro or???
Yes, it will be in the Miroverse! :)
Maarten, this is a very good analysis and it shows your deep understanding of the subject (of course!).
However, I think I missed the link to your Miro template 😉
Not out yet! :) Working on it.
I also read the original SCREAM paper, and it contains quite some Scrum mistakes. Would you want to receive a list of errata?
Could you please point to me where that was written in the original conference paper? I'll happily adjust if I missed something.
30K does not include the costs of the other people who are involved, and the cost of delay of 20 weeks. It's still too slow IMO!
But if you're only using it to provide an alternative pedagogical experience, then cost of delay doesn't matter indeed.
Also, why is it being compared with Scrum and not something like eduScrum then?
One other thing, SCREAM already exists as a parody of poor Scrum:
https://www.agilegothenburg.org/blog/2019-posts/the-scream-guide-is-out
Thanks for sharing! I know it isn't a product company nor an agency.
I'm not a fan of the terminology hacking, if you want to do your own thing, by all means do it, but don't misuse existing terms that have precise meanings, and get them to mean something else.
I understand then it doesn't sound as cool anymore, but it's far better than teaching people wrong things and saying they are right outside of a business context (which I don't believe is a strong argument because Scrum is defined outside that context too as a framework for solving complex problems).
I am happy to help review your materials for accuracy, but you really shouldn't be teaching these things.