In this informal walkthrough, Mike Lyons and Michelle demonstrate how to use the AskMe wizard within the Canvas LMS to create drag‑and‑drop assessments that teach Scrum events and core Scrum concepts. Mike explains how he instructed the wizard to generate clear, unambiguous items for each Scrum event (Sprint Planning, Daily Scrum, Sprint Review, Refinement, Retrospective) and how to enforce outcome counts (e.g., “drop 2 outcomes here”) so students can only place the correct number of items. He highlights practical UI challenges such as limited real‑estate on the left‑to‑right layout and the need to specify placement constraints. Mike also shows a playful feedback idea—triggering fireworks when a student matches an item correctly. Finally, he walks through a second activity that maps Scrum Guide principles (Transparency, Inspection, Adaptation) using a top‑to‑bottom drag‑and‑drop, emphasizing the importance of clear statement wording. Throughout, he shares tips learned the hard way, like explicitly telling the wizard which statements to use and how to handle Canvas’s participant spot UI element.
Chapters
I don't know. I'm not, I'm not very creative either, Michelle. So I hope I'm not like, like, don't, don't get your hopes up. But what, but like, let's see. So this is one that is on the Scrum events.
Okay.
And so I get, I asked it to create a series of items That, and Michelle, I was probably like you, I was using the wizard and I was saying, now clear beats clever. We're not trying to trick our students. So the things on the left, they should not be like, oh, well, it could be either. It's like, no, the team agrees on a shared sprint goal. That is very clearly a sprint planning option.
Mm-hmm.
And then, you know, the team surfaces blockers before they stall progress. That smells like the daily scrum.
Yeah.
Anyway, my point in this is it's a drag and drop left to right, but a couple things I want to call to your attention that I've learned kind of the hard way. I also had to tell it, you know, tell the students how many outcomes live here. So see where it says drop 2 outcomes here? So that's like, that's a little, little tip. 2 items come here. And if you try to put, let's see, the team and stakeholders inspect the increment to determine next steps. Well, that's sprint review. Story complexity is reduced. That's going to be refinement. A process change to improve, retro. So, so now, now that, okay, let's see what happens when I drag a second one. Self-organized daily, daily scrum. But if I try to drop this one here, like it won't let me. It won't let you. So that's another one. You got to tell it like you can only have 2, 2 and only 2. So let's finish, but the product backlog may be adjusted to meet new opportunities, product backlog adjusted. That's going to be at the review. Developers plan to create an increment. That's going to be planning. Almost done. Upcoming work is understood well enough as refinement. And then root cause retro. So, so now they're done. And, and also you'll notice it was a drag left to right. That's a real estate issue I have here. So, so now, uh, when they click submit, we'll try to get rid of that. Anyways, look at the gas mic. I also said I'd like it to have fireworks if they got it right.
Oh, that's cool. I didn't know you could do that.
I don't know. It was silly. And Greg was like, what? They got it right. They get a little— so that's one. And then, oh, and then this, I'm, I'm in the higher ed tool called Canvas is why you see this little participant spot. That's all that is. And then let me just show you one more. I've got a drag and drop Uh, I think it's Scrum Guide First Look. Yeah. So this one, they go read the Scrum Guide just to the, um, just the first part. And then they've got a statement bank. Now it's a drag from top to bottom. I've already done it. So it's done. Um, but these were up here.
Yeah.
And they, and it was like, well, again, I had to tell it the statements I wanted. I had to read them each and make it clear, not clever. Um, and then they drop them into the things and then they submit. So that was a, you know, I was just thinking when I read the Scrum Guide, it's like, well, what, there are 3 things, transparency, inspection, adaptation, that might work. And so I guess I'm backing up to like, for you and I, as we're creating these things, it's like, what, you know, and I guess this is probably what the wizard's trying to help us do, Michelle.
Mm-hmm.
Like, what, what do I want them to do? Well, I want them to think Like logically about this idea of transparency. What, you know, and I'm chatting with the wizard. I'm like, I don't really know what to do here, but, and, um, anyway, so that, uh, there you go. There's a couple ways. I hope that helps.
