##Retro
- Identify 3 things went well. Why do you think these were successful?
Mark- when I would get lost, Jeneve would help me get back on track, Jeneve was on top of testing. Working together on one machine went better than working separatly. Jeneve- It was a boon when we were under the gun, that Mark was able to work so quickly, whereas I could never have finished. Mark's knowledge of excel came in super handy when we needed to look at the data. Mark was very flexible about my schedule constraints and always available when I was.
- Identify 3 things that didn't go well. Why do you think these were unsuccessful?
Divide and conquer approach didn't work because we both took different routes in the beginning. This caused problems later on, and could have been avoided if we'd looked ahead together and really planned out an approach. We shouldn't have wavered about creating the fixtures. when it became obvious that it was neccessary, we didn't have enough time left to build all of them.
- Identify 2 things that were supposed to happen but didn't. What did happen instead? Why was there a difference between what you expected to happen and what did? (Our method was supposed to work but didn't is not a good answer. Look for things about your process or collaboration)
We were excited to implement our own feature, but we didn't have time Identify 2 organizational constraints or we faced? How did we overcome them or did we?
- What existing techniques or approaches from past projects enhanced or enabled our performance on this project?
Event Manager helped with managing CSVs, DTR was good for us to coordinate schedules. Ruby Enumerables lessons helped. >The Stack.
- Did the team meet sufficiently often and work productively together? Could time pressures have been alleviated by organizing the work differently? Could we have taken another approach to reach our goals more efficiently and effectively?
Given the time constraint, we worked as much as we could. Fully understanding the project before starting would have helped
- Was the goal always clear? no
- Were the instructions always clear? no
- How can we do better next time?
More clear description of what a method should do would have helped. Sometimes we were sure that we were getting the right answer, only to find that the spec harness was testing something else entirely.