Monday, 16 March 2015

Sprint #2 reflection - Donal Murphy

Applied embedded Operating System 

For the second sprint, the teams were kept the same to maintain cohesion, this team being myself, Sam, Dii and Tony. There were 5 main deliverables outlined in the brief for the second sprint:

1. mbed running minimum of 4 threads and using IPC.
2. Cone part of lamp design tracking ball and faces in 2d space...think pan/tilt
3. Roborealm running on pc communicating with mbed.
4. Combine cone pan/tilt movement with sonar in/out movement of body.
5. Client wants to see a video plus demonstration of functionality at the end of sprint.

With regards the teams work management in the first sprint, it was quite poor. So, taking this into account the team began by dividing up the work for sprint two evenly so that we'd always be working on something. For this sprint I began looking into serial communications between for the mbed application board to receive information from the Roborealm software. Dii began by reconstructing the servos and then once that was complete Dii and I started looking at serial communications together. Dii and I got the serial comms working by the end of the first week; this allowed us to receive information from Roborealm in which Tony and Sam collaborated on. Sam was designated to work upon Roborealm software and Tony worked upon the IPC (inter-process communications) for the threads running upon the mbed board. During the first sprint, where the teams were quite apprehensive to share knowledge, the teams have begun to collaborate and share information when they achieved milestones ahead of each other during the second sprint.

During this sprint I decided to raise an issue I had, this was the fact there was a distinct difference in skills between team members. As Sam and Tony are from a computer science background and myself and Dii are of an Electronics background. I found during the second week that the tasks were in fact more inclined towards the programming side of the project. As Tony and Sam are more experienced in programming, they have the capability to complete programming tasks quickly and efficiently, this meant that there may not have been enough work for Dii and myself. From this I asked the question, why have myself and Dii in the loop? Working on the programming aspect of the project which Tony and Sam could find “easy” whereas Dii and I might struggle with. From a brief team meeting I found that from an educational point of view its beneficial for myself to try it ourselves and learn but in industry, things might work a bit different, teams of coders working in parallel and teams of Electronic engineers working in parallel.

Donal Murphy.

Keep moving forward.

No comments:

Post a Comment