Hrm/531 Week 1 Sprint Review

573 Words2 Pages

At the initial sprint review we did not have anything to demo since our first sprint tasks had merely been to set up a development environment for ourselves and produce a commit message to our git. A task of which all of us had accomplished. Our review of this task was simply "Great job!". After the first sprint we were informed that several groups have had difficulties with the server, and therefore reformed to a Python based solution instead of Java. By the second week we had had a few complications with the server, which led to us not being able to attain all our sprint goals for the week, thus did not have anything to demo and came to the realization that we might need an alternate solution. By this period, we also had difficulties starting out with developing our ACC since no data could be obtained from the sensor and we were suggested to continue our development and in the need of data, send fake data until further notice. After the third week we felt something could be sampled, since we decided not to apply the server for our plugins. This week we could show that data could be sent to the MOPED to remotely steer and "start" the motor via a laptop. The review this week was a 6.5 in a satisfaction scale from 1 to 10 where 1 means that we have no chance of achieving the final demo, and …show more content…

Our review for this week was a 10 out of 10. As of this we felt we now had accomplished our task and did not feel motivated to further develop our solution, primarily since numerous MOPEDs were out of function. Although, we still felt we needed to implement an ALC and decided to hereby modify nearly all our meetings to work-meetings, where instead of chatting, worked on our MOPED, to advance it. This being the first week we felt we had accomplished

Open Document