Sprint 1: Post 4

Sprint 1: Post 4

I'm currently in a meeting with my team. We're all doing our blog posts. It's pretty down to the wire with this one. We need to challenge tomorrow and we still haven't decided what game we're going forward with. We're getting close but we're taking a break right now. It's very stressful so I must ask myself: How did it come to this?

We didn't get prototypes to a point worth testing until late in the week. This left me the weekend to test and I was able to get in the lab but I didn't get to test one of the prototypes in the lab due to technical difficulties related to Git. I got the build working hours after QA but it was too late and then I was stuck with testing informally. I got some good feedback but it wasn't enough to sway the decisions at the end here. This crisis probably won't happen in the future because we'll have builds that are more iterative so we'll get it to the testing stage and then build in that. Overall I think we're doing fine. I'm the only one that seems like they're cramming more than they should be. When we are at a crossroads that each path goes super long it's hard to chart a course that works both ways. I'm excited to actually know what our project is but right now I'm at code yellow. The project overall is code green.