In this skit, the team is several cycles in. So they've finished a few iterations, and they're doing a retrospective on their last iteration. You'll hear references to additional members of the team. We didn't have people to be on camera, so you're just going to see these three folks, even though I would normally recommend that you have everybody on your core team in these retrospectives. >> All right team, thanks for getting together again today. We're here to do a retrospective on our last sprint. We want to talk about what we think we should keep doing, what we should change and do better. Everyone makes mistakes, the point of this meeting is not to point the finger and blame each other, we just want to have a productive discussion about our approach. And see if we can refine and improve. I'll start. The product owner role is starting to take up more and more of my time. It's probably 75% at this point. I'm still doing the testing piece. I've been staying pretty late. And I think for more rapid scaling as we move forward, we ought to think about how we're going to add some testing. Further testing capability. So Shri wanted to talk to you about whether or not we should hire someone, whether you think we should maybe go with an outsource option. I found an agency that can do some testing for us. What do you think? >> We definitely want to hire someone, but I think we should do an on-site hire. We really want a tester who is here in person. Testing is pretty complicated, or more complicated than it seems. And we want to test at the lowest possible level, just so, we don't want to catch something too far along during functional testing that we could've caught way earlier during unit testing. And it's pretty good to work with someone who's on-site rather than off-site. >> Okay, but you still want to hire someone? >> Yeah, definitely. Since automation has been up with the one tester that we have, another developer would actually be better than another tester. >> Are you sure about that? >> No, I'm not certain, but we'll have to see. In about two weeks, honestly, I think that when we've gotten a lot more automation we'll probably do fine with just one tester. >> Okay. Gotcha, so another question I have for you. Velocity overall is up, we haven't seen much of an increase in the last two weeks. Do you think we've plateaued at this point? >> No, I don't think so, I think things are actually improving. We've had a lot more bugs in the velocity, but it seems like a lot of them might be due to little refinements or tunings that we need to make. >> Okay. Well, my fault on the tracking. We'll get that fixed. What do you think is causing more bugs in refinements? Is testing struggling? >> I honestly don't know. No, testing is doing pretty well. >> If I had to guess, it's just that that the word's out, more of the techs are using the software, so we're going to get some suggestions, we're going to see more bugs. >> Right. Okay, well that makes sense. We haven't looked at the data recently but we should probably do that at the end of this cycle to validate that hypothesis and track our ratio of bugs to usage somehow. Shri, any issues? >> No, things are going well. I've spent a lot less time as score master and I think that's because everyone's just doing a really good job of working independently. >> Great. >> I can see a lot more potential for our work, though, but I think I"m going to let everyone continue with their self-organizing and independent work before I decide to make any changes. >> Okay, well now that part ordering is looking good, the big thing we'll be trying out our problem scenarios from dispatch. Shri, what do you think there? >> Well it looks like the inputs from dispatch seem a little light and uncertain. It's like the problem scenarios and user stories just aren't as strong as they once were. >> Yeah, no, I totally agree and I think what we should do is get out, do another design sprint, and take everyone out in the field for observation so we can tighten up our problem scenarios. >> That's a good idea. >> Do we take everybody? The whole team? >> Yeah, I think so. I mean the developers could be working on refactoring or they could be helping with the technical debt. But honestly, I had so much like a good experience in the field, so I think everyone should go. >> Okay, cool. Well, that's it for me, are there any other outstanding items? >> Not on my end. >> I don't think so. >> Okay, great.
