SECJ2203-Software Engineering
by LEE BAO YI
Description of leadership levels I have implemented during the brainstorm session.
In my opinion, the overall leadership level I have implemented during the brainstorm session of PR3 is on the extent of medium good.
On the attribute of the written communication, I rated myself as good as I was able to write the brainstorm ideas clearly, coherently, and systematically. While on the attribute of the leadership, I rated myself as fair. I could demonstrate my knowledge and understanding learnt during lectures of Software Engineering in practice but still need some minor improvements to become a better leader in the future. As on the attribute of teamwork, I rated myself between fair and good. Teammate relationship was built among group members, alternate roles of group leader and a group member were interchanged during the project implementation, and opinions were brought to discussions to achieve group goal of succeeding the project.
A self-reflection description on how I conduct the session after the brainstorm session.
As a group leader in the phase of Project Report 3 (PR3) in group AMIGO, I requested for an online meeting for group discussion in the Discord communication platform before the commencement of PR3. The meeting agendas are to sort out the project report requirements of this PR3 phase, to clarify some important concepts for certain points such as the correct way of drawing the component model, the package diagram, the class diagrams, and the data description design, as well as to confirm the doubts with our lecturer, Dr Norsham.
During the meeting, I initiated the discussion by conveying my understanding on the modules requirements and then asked for additional opinions or suggestions from group members. Group members gave their responses and ideas on the project requirements. Before the end of the meeting discussion, the correct procedures and the items needed to be paid attention are confirmed.
After the meeting ended, I made a task distribution list for group members. The task distribution is listed according to the modules where each of us could take the responsibility to help complete a module, starting from Module 3, 4, 5, and 6. While the diagrams and tables required in the subsystems of Module 4 are distributed among group members where each of us took at least one subsystem to complete its corresponding diagrams.
During the implementation of the tasks, group members did post some questions regarding the project in our group message group. Questions were explained by other group members. Lastly, a few days before the submission deadline of PR3, I sent a reminder message in our group to ensure that all tasks could be completed on time. After having all parts from all group members, I checked and compiled the report documentation of PR3 before the submission to UTM eLearning.
In conclusion, I have learnt that it is important to have communication with group members all the time throughout the project. The communication methods are not restricted but are carried out in the form of online meetings and message discussions. This is to ensure that all group members have the same goal which is to complete and succeed the project based on the project rubrics. Besides that, the time management is also a point worth to be mentioned as group members and I have to work together so that the submission of the project report is on time.