In our second class we learned about the Software Development Lifecycle (Scope, Time, Quality and Cost). We discussed the dependencies between each and also the problems that the lack of a clearly defined scope can have on time, quality and cost. There were many comments on which scope, time, quality or cost was the most important factor in software development however we could not reach a common conclusion. The group was evenly split between scope and cost as their impact on each other is clearly documented.
The second half of the class was taken up with a group exercise, each tablet was split into teams and asked to construct an electronic Lego robot which had the ability to learn from its surroundings. This proved somewhat of a challenge given the limited time assigned and the complexity of the task. To order to utilise everyone as much as possible we assigned roles to each team member at the beginning this meant the team was able to work as an assembly unit to source, group and construct parts. This entire process was then overseen by a manager to keep us all inline. Our ability to work as a group was somewhat challenged by the fact that our kit did not contain all the required parts to build the robot however our manager saw us through and kept us all cool and as a result we managed to complete our robot with seconds to go before time expired.
Following the task there was a group discussion to reflect on the task and its learning. It quickly became apparent from this conversation that the teams to complete the tasks had clearly assigned roles and worked together as a unit, communicating efficiently and effectively. This meant there was no duplication of effort and each person knew exactly what they were doing.
Full Post
No comments:
Post a Comment