Hey, guys. How's things? >> Vince. How are you? >> Hey, Vince, how's it going? >> Good, good. Dan, you look a little different. >> Yeah, grew the beard out. Trying a different look. >> Looks nice. >> I appreciate that. >> You guys have been busy. What's this whole thing here? >> It's a story map, actually. It kind of gives us a good idea of what we want to implement for the customer. So, I see our storyboards we've been making up here. We get a call, dispatcher gets the specifics and schedules a tech. And updates the customer. The tech gets the work. Heads out, knows where they're going. Where's the technician, okay. Technician needs to diagnose. They find they need to replace a part. They find it, order it. It gets scheduled. It comes. They go back out. They finish. We invoice. We get paid. Yep, well looks pretty good, yeah. It starts with we get a call, it ends with we get paid. So we definitely got it bracketed. What else did you want me to do with this? >> Yeah, so we feel like our core narrative is starting to come together, but we wanted a third-party perspective, and wanted to see if you saw anything that was missing. So if you could take a close look and tell us if we're missing any parts of the dispatcher activities. That'd be awesome. >> All right, so what's all this different stripes and stuff here on the board? >> This is a priority list actually. We got our higher priority stories up here and our lower priority stories down here. >> Okay, so these look looks like there's a lot more detail up here than down here. How come? >> Yeah, these are actually way more detailed. These stories are product backlog and we're going to be moving them to our sprint backlogs when we're doing our sprint planning meetings. >> Okay. Product backlog, you said your sort of the same thing as what at the moment we've decided is our minimum viable implementation to see if we're on the right track, we're doing something valuable. Is that- >> Absolutely. >> Is that right? >> And these lower stories are less necessary to the actual narrative. >> All right, so a nice idea you put on the board but you put it down here, okay. All right, so is anything missing? Well, you know what, it's a little embarrassing but there's kind of an important thing here. Between when we order the part, and when it comes and we go back out is, what happens is parts are supposed to come on a Wednesday. We're going to dispatch on a Thursday, so tech has the thing, but actually the part doesn't come on a Friday. And the issue is the part comes two days late, we don't really have a systematic way of making sure we handle that properly. Some dispatchers are better than others but it kind of creates a whole mess between the dispatcher, the tech, the customer that I actually spend a lot of time with. So that, that whole business might be a good candidate for our project here. >> Yeah Vince I think that's a good point. Just spit-balling here, but how about an email alert for a solution? What do you all think about that? >> That could be a good idea, but I feel like we shouldn't settle on a solution just yet. >> Okay, and then also I think the solution that we come up with is going to depend on our approach. So Sheree have you given any thought to whether or not you think it's going to be best for us to build our own infrastructure for parts ordering or whether we should go for the supplier option we should go with the wholesaler option for supplier consolidation? >> I actually think that both are pretty viable right now. >> Okay. >> I've added some time in the spring to evaluate which option will be better. But I'm almost ready to pick a solution, but I'm going to make that final decision at our next break. >> Okay. >> It's a really good thing you got in here, though, Vince because we didn't think of that issue during our initial problem description. >> Yeah, well, look, I was in there, too. And it's very helpful to see all this stuff laid out here sequentially and with the stories, so you guys did a good job. It's good you did this. >> I appreciate it. Sheree, I'm thinking maybe we just jump into an impromptu user story writing workshop. And that way we'll be ready for the sprint planning meeting next week. >> Yeah, absolutely. Sounds like a great idea. >> Cool.
