[MUSIC] Okay, so I was thinking it would be good for us as a team to do a quick retrospective. I think we could learn a lot from this process, and it could really benefit us moving forward. Does that sound okay to everyone? >> Yeah, sure. >> Yeah, I guess so. >> Great, so then I think the way we should do this is, we should go through and brainstorm what went well and what went wrong. And then based on what we come up with, then we can kind of discover some ways to help improve for the next sprint. So yeah, let's start with what we did well. >> Well, we've got all the expected user stories complete. >> Yes we did, and that was quite an achievement especially in the first sprint. What else? >> We had a stand-up every day. It might not have been first thing in the morning, but we always found the time to get one done. >> Yup, what else? >> Well, in the end, all of our users' stories met our definition of done. >> Indeed. >> And we have a working product. >> Yes, we do, and an impressive one at that. Anything else? No? What about things that we could've done better? Please remember that this is not an attack. We're just doing this so we can improve every sprint. >> Well, I guess the obvious one is that my unit tests weren't written before I started doing the source code for my feature. >> Yup, but I think that's an easy fix. >> We also should have written our acceptance tests and criteria before we started developing. It's not a big deal, but it's something that we can improve on. >> Definitely, and I think we could improve the use of the task board. There were many times, through the sprint, that it didn't accurately represent the progress of where we were at. I just think we need to be more diligent and update the board when a task has progressed. >> That's a good point. I was bad at that. >> That's okay, no worries! That's what this exercise is for. >> How do we think our story point estimates were? I know we got them all done on time, and with little time to spare, so overall they were fine. But how accurate were they individually? >> I think they were fine, but we'll probably need another sprint to know for sure. >> Yeah, I think they were pretty accurate. >> Okay, so then should we add those to the positives? >> That's a good idea, Josh. >> Does anyone have anything else? >> Not that I can think of. All right, so now let's talk about some ways that we can improve for the next sprint. >> Writing acceptance tests and unit tests early. >> Yup, let's add that. >> Using the task board more. >> Of course. I think we can try to pair program a bit more. >> Yeah, I think that's a good idea. Josh, I'd like to pair programs a bit with you. I'd like to see how you code. I think that would be helpful. >> Yeah, I guess I could do that. >> Wonderful. I think in general we could improve communication and pair programming will help with that, but I think a team can always improve with that, so it's just something to consider. >> Yeah, I agree. >> Does anyone else have anything to add? No? All right well, I think this has been extremely helpful. I'm excited to work on the next sprint and yeah, have a good weekend, everyone.
