HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2011T2 IMATEAM Teamreflections"

From IS480
Jump to navigation Jump to search
(New page: 180px|left <br> <Br> <Br> <br> <div style="text-align: right;"><span style="font-family: 'Arial Rounded MT Bold'; font-size: 35pt; letter-spacing:-0.1em; line-he...)
 
 
(3 intermediate revisions by 2 users not shown)
Line 29: Line 29:
 
{| style="background-color:#4c4942; color:#000000 padding: 5px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
 
{| style="background-color:#4c4942; color:#000000 padding: 5px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
 
| style="padding:0.3em; font-size:90%; background-color:#4c4942; border-bottom:4px solid #ffffff; border-top:10px solid #ffffff; text-align:center; " width="12%" | [[Image:Imaaarrow2.png|15px]]<font color="#ffffff">Learning Outcomes</font>
 
| style="padding:0.3em; font-size:90%; background-color:#4c4942; border-bottom:4px solid #ffffff; border-top:10px solid #ffffff; text-align:center; " width="12%" | [[Image:Imaaarrow2.png|15px]]<font color="#ffffff">Learning Outcomes</font>
| style="border-bottom:4px solid #ffffff; border-top:10px solid #ffffff; background-color:#6d6960; " width="2%" | &nbsp;
+
| style="border-bottom:4px solid #ffffff; border-top:10px solid #ffffff; background-color:#4c4942; " width="2%" | &nbsp;
| style="padding:0 .3em;  font-size:90%; border-bottom:4px solid #ffffff; border-top:10px solid #ffffff; text-align:center; background-color:#4c4942; " width="12%" | <font color="#ffffff"> [[Image:Imaaarrow2.png|15px]] [[IS480_Team_wiki:_2011T2_IMATEAM_Teamreflections |<font color="#ffffff">Reflections</font>]]
+
| style="padding:0 .3em;  font-size:90%; border-bottom:4px solid #ffffff; border-top:10px solid #ffffff; text-align:center; background-color:#6d6960; " width="12%" | <font color="#ffffff"> [[Image:Imaaarrow2.png|15px]]<font color="#ffffff">Reflections</font>
 
| style="border-bottom:4px solid #ffffff; border-top:4px solid #ffffff; border-top:10px solid #ffffff; background-color:#4c4942; " width="2%" | &nbsp;
 
| style="border-bottom:4px solid #ffffff; border-top:4px solid #ffffff; border-top:10px solid #ffffff; background-color:#4c4942; " width="2%" | &nbsp;
 
| style="padding:0 .3em;  font-size:90%; border-bottom:4px solid #ffffff; border-top:10px solid #ffffff; text-align:center; background-color:#4c4942; " width="12%" | <font color="#ffffff"></font>
 
| style="padding:0 .3em;  font-size:90%; border-bottom:4px solid #ffffff; border-top:10px solid #ffffff; text-align:center; background-color:#4c4942; " width="12%" | <font color="#ffffff"></font>
Line 42: Line 42:
 
| style="padding:0 .3em;  font-size:90%; border-bottom:4px solid #ffffff; border-top:10px solid #4c4942; text-align:center; background-color:#4c4942; " width="12%" | <font color="#ffffff"> </font>
 
| style="padding:0 .3em;  font-size:90%; border-bottom:4px solid #ffffff; border-top:10px solid #4c4942; text-align:center; background-color:#4c4942; " width="12%" | <font color="#ffffff"> </font>
 
|}
 
|}
<font face="century gothic" size="1">
+
<font face="century gothic" size="2">
=='''Learning Outcomes'''==
 
  
<table border="1" cellpadding="1" cellspacing="1">  
+
=='''Reflections'''==
 +
===<div style="color: #ffffff; font-size:0%">Team</div>===
 +
{| border="0" cellspacing="0" cellpadding="0" width="100%"
 +
| style="background-color:#000000;" width="0" |
 +
{| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0"
 +
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" |  <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Team</font></div>
 +
|}
 +
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | &nbsp;
 +
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| &nbsp;
 +
|}
 +
{| style="width:100%; margin-bottom:.5em; font-size:100%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0"
 +
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" |
 +
<div style="padding:10px; text-align: justify;">
 +
<font color="#000000"><font size ="2px">
 +
Together as a team of four, we’ve learnt so much on this incredible journey, and we’re only a little past the midway mark. Aside from the technical aspects that we’ve gathered, we’ve also learnt the following:
  
<tr bgcolor="404040">
+
• Teamwork and communication – Being a small group has its pros and cons. One of its pros however, is that we’ve grown closer, and learnt to depend on one another and improve on our communication in the process. One of the initial challenges was that we were not communicating enough, which led to delays since some aspects of the development required the completion and coordination of another team member.
<th> <font color="white">S/N</font></th>
 
<th> <font color="white">Description</font> </th>
 
<th><font color="white">Actions to Realize Learning Outcome(s)</font></th>
 
<th><font color="white">Method(s) of Assessment</font></th>
 
</tr>
 
  
<tr bgcolor="cccccc">
+
• Scope Manageability – As a team, we were full of ideas and brimming with confidence about our project. However, we also learnt to manage both our client and supervisor’s expectations, and how to be selective and realistic about additions or changes to the scope of the project. Nevertheless, the biggest learning point has been how as a team, we’ve learnt to consistently adapt our own expectations and goals to the various additions and changes to our project scope.
<td><b>1</b></td>
 
<td  colspan="3"><b>IT Architecture Design and Development Skills</b></td>
 
</tr>
 
  
<tr>
+
• Finding the middle ground – Even though we’re a small of team of four, each of us has incredibly strong opinions and capable personalities, which would ultimately more often than not lead to disagreements. However, a good thing is that we’re comfortable with each other and as a group, and disagreements instead led to even better ideas when we all ultimately try to find a middle ground.<br><br>
<td></td>
+
|-
<td>1.1 System Requirements Specification Skills</td>
+
| colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div>
<td>
+
|}
*Gather and propose functional and non-functional requirements of IMAPAC Connect.
 
*Analyze business requirements and propose infrastructure and applications needed to complete project.
 
</td>
 
<td>
 
*Feedback from client and supervisor</td>
 
<tr/>
 
  
<tr>
+
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2011T2_Imateam_midterm#Top|Back to Top]]</u></font></div>
<td></td>
 
<td>1.2 Software and IT Architecture Analysis, Design Skills</td>
 
<td>
 
*Design the solution architecture based analysis from gathered requirements.
 
*Develop a social media suite based on proposal requirements and integrate with IMAPAC’s back end systems and services.
 
</td>
 
<td>
 
*Feedback from client and supervisor</td>
 
<tr/>
 
  
<tr>
+
===<div style="color: #ffffff; font-size:0%">Iskandar</div>===
<td></td>
+
{| border="0" cellspacing="0" cellpadding="0" width="100%"
<td>1.3 Implementation Skills</td>
+
| style="background-color:#000000;" width="0" |
<td>
+
{| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0"
*Implement system, develop and integrate all customized modules and third party functionalities.
+
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" |  <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Iskandar</font></div>
*Deploy prototype in every iteration and resolve bug from tests within proposed schedule.
+
|}
*Conduct User Acceptance Test (UAT) at every milestone for the developed product.
+
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | &nbsp;
</td>
+
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| &nbsp;
<td>
+
|}
*Feedback from client and supervisor
+
{| style="width:100%; margin-bottom:.5em; font-size:100%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0"
*Team Review at end of iteration (Internal)
+
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" |
*Bug Metric
+
<div style="padding:10px; text-align: justify;">
</td>
+
<font color="#000000"><font size ="2px">
<tr/>
+
This FYP has been an incredibly long, hard journey but one that I thoroughly feel proud and elated to be a part of. I’m sure every one of us in IMATEAM has learnt so much beyond our wildest dreams, but the best part for me has been to have gone through it with this team.
 +
I’ve learnt so much in terms of project management, both in terms of project scheduling and managing the team. Despite this only being the mid-point reflection, I’ve developed a tremendous amount of respect and admiration for my team-members and the amazing things they’ve been able to do for this project.
  
<tr>
+
Learning Drupal is so very hard, but very rewarding in my opinion. Our team took a leap of faith with Drupal because of its potential in offering robustness and awesome websites, but also the potential opportunities it provides us in the team as individuals. After all, there is an incredibly huge demand for Drupal developers, but few in supply.<br><br>
<td></td>
+
|-
<td>1.4 Technology Application Skills</td>
+
| colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div>
<td>
+
|}
*Research, learn and apply Drupal APIs and Framework.
 
*Ability to utilize appropriate PHP, jQuery, JavaScript, Ajax and Drupal Framework for implementation.
 
*Integrate geo-spatial functionality into social media suite for both web and mobile platform.
 
</td>
 
<td>
 
*Feedback from client and supervisor
 
*Team Review at end of iteration (Internal)
 
</td>
 
<tr/>
 
  
<tr bgcolor="cccccc">
+
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2011T2_Imateam_midterm#Top|Back to Top]]</u></font></div>
<td><b>2</b></td>
 
<td  colspan="3"><b>Project Management Skills</b></td>
 
</tr>
 
  
<tr>
+
===<div style="color: #ffffff; font-size:0%">Felix</div>===
<td></td>
+
{| border="0" cellspacing="0" cellpadding="0" width="100%"
<td>2.1 Scope Management Skills</td>
+
| style="background-color:#000000;" width="0" |
<td>
+
{| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0"
*Manage scope of the project and work distribution by taking into consideration the team’s technical capabilities and the team’s proposed implementation schedule.
+
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" |  <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Felix</font></div>
*Ensure project scope is on schedule and can be promptly delivered by monitoring schedule and bug metrics.
+
|}
</td>
+
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | &nbsp;
<td>
+
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| &nbsp;
*Feedback from client and supervisor
+
|}
*Team Review at end of iteration (Internal)
+
{| style="width:100%; margin-bottom:.5em; font-size:100%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0"
*Schedule Metric
+
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" |
</td>
+
<div style="padding:10px; text-align: justify;">
<tr/>
+
<font color="#000000"><font size ="2px">
 +
I have learnt a lot so far for this FYP. When we first decided to choose Drupal as our main framework, we did not realize that the learning curve for this particular technology is very high. Initially, my team and I were concerned that we would not be able to deliver best product to our sponsors. But we, as a team, worked together and helped one another. Subsequently, I learned that with hard work (and enjoyed the fun time I spent with my groupmates) and having full confidence in my groupmates’ abilities, we are able to face the challenges and resolve any problems we encountered along the way.
  
<tr>
+
As a lead developer, I have acquired some knowledge of the Drupal modules. One of the major difficulties that I came across during the development process was not knowing how to start to custom code the 3rd party modules. First, I had to understand and be familiar with the codes of these modules so I know which part to modify to fit our project’s requirement. Some of the codes were very complex that it took me hours to just grasp what the codes are about. The other difficulty that I encountered was modifying the codes. In order to accomplish the task, I had to change the codes from a few files within the module.<br><br>
<td></td>
+
|-
<td>2.2 Risk Management Skills</td>
+
| colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div>
<td>
+
|}
*Evaluate various project risk(s) and devise mitigation plans to address and reduce impact on implementation schedule.
 
*Monitor and update Risk Metric regularly.
 
*Execute mitigation plans where necessary.  
 
</td>
 
<td>
 
*Feedback from client and supervisor
 
*Team Review at end of iteration (Internal)
 
*Schedule Metric
 
*Risk Metric
 
</td>
 
<tr/>
 
  
<tr>
+
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2011T2_Imateam_midterm#Top|Back to Top]]</u></font></div>
<td></td>
 
<td>2.3 Project Integration and Time Management Skills</td>
 
<td>
 
*Allocate adequate timeline and ensure new functionality is well integrated in each iteration.
 
*Adhere to proposed implementation schedule with schedule metric.
 
</td>
 
<td>
 
*Feedback from client and supervisor
 
*Team Review at end of iteration (Internal)
 
*Schedule Metric
 
</td>
 
<tr/>
 
  
<tr>
+
===<div style="color: #ffffff; font-size:0%">Alicia</div>===
<td></td>
+
{| border="0" cellspacing="0" cellpadding="0" width="100%"
<td>2.4 Configuration Management Skills</td>
+
| style="background-color:#000000;" width="0" |
<td>
+
{| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0"
*Maintain code repositories, proper audit trails and revision of codes of project source using tortoise SVN
+
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" |  <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Alicia</font></div>
</td>
+
|}
<td>
+
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | &nbsp;
*Tortoise SVN
+
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| &nbsp;
*Programming Task Tracking
+
|}
*Feedback from project manager
+
{| style="width:100%; margin-bottom:.5em; font-size:100%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0"
</td>
+
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" |
<tr/>
+
<div style="padding:10px; text-align: justify;">
 +
<font color="#000000"><font size ="2px">
 +
The FYP journey has been a challenging but fruitful one for me so far. I have learned a lot throughout the duration of the project, both on the business and IT side of things. I assume the role of Business Analyst in the team, thus it is my responsibility to be in constant communication with our sponsors and supervisor. As our team is a small one, it is especially important that we manage client's expectations well to ensure that our scope is manageable. It is also important that we all take on more than one role and help each other out whhenever we can to ensure that the workload is evenly distributed. As a B.A., I also helped out with the technical side by developing the admin functions of our application.
  
<tr>
+
This project has taught me to be patient and resilient. As we are tackling Drupal 7, a new framework that none of us had prior experience with, it was important that we got our foundations right. It was also crucial that we found the determination to try again whenever a function did not work as planned. A lot of effort had to put into research but they paid off in the end. Working on both the business side and technical side of things also taught me more about the importance of reconciling the needs and differences of these two aspects.<br><br>
<td></td>
+
|-
<td>2.5 Quality Management Skills</td>
+
| colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div>
<td>
+
|}
*Develop test cases for UATs and evaluate the feedbacks given and responses from IMAPAC.
 
*Perform necessary changes derived from the evaluation of feedbacks and responses from IMAPAC to further enhance the proposed application.
 
</td>
 
<td>
 
*UAT every milestone
 
*Feedback from client and supervisor
 
</td>
 
<tr/>
 
  
<tr bgcolor="cccccc">
+
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2011T2_Imateam_midterm#Top|Back to Top]]</u></font></div>
<td><b>3</b></td>
 
<td  colspan="3"><b>Learning to Learn Skills</b></td>
 
</tr>
 
  
<tr>
+
===<div style="color: #ffffff; font-size:0%">Stephenie</div>===
<td></td>
+
{| border="0" cellspacing="0" cellpadding="0" width="100%"
<td>3.1 Methodology for Group Learning</td>
+
| style="background-color:#000000;" width="0" |
<td>
+
{| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0"
*Regular group sharing sessions and practice pair programming with devised schedule.
+
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" |  <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Stephenie</font></div>
</td>
+
|}
<td>
+
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | &nbsp;
*Team review at end of iteration(Internal)
+
| style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| &nbsp;
</td>
+
|}
<tr/>
+
{| style="width:100%; margin-bottom:.5em; font-size:100%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0"
 +
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" |
 +
<div style="padding:10px; text-align: justify;">
 +
<font color="#000000"><font size ="2px">
 +
So far, this FYP journey has been a mixture of pain and happiness. To begin with, we are a really small team. Being a small team has its pros and cons. It’s really easier to communicate within a small team; we have no time to hold grudges with one another. We voice out our opinions and discuss everything as a team cause we know that we need everybody support in doing the project. Honestly, I am really happy to be in this team. Although we are really close friends and know each other strengths and weaknesses inside out, we are not afraid to step out of our comfort zone and volunteer to help one another. It’s really important to have a good, hardworking team that understand and support one another especially when we are working on a totally new language, which has a really steep learning curve, and have to manage client expectations at the same time.
  
<tr>
+
As a lead designer, I am really stress at times because I am afraid that I am unable to meet clients or my team members’ expectations. Besides, designing in Drupal is not as easy as designing in Photoshop. It’s so much more challenging. The video tutorials I’ve watched for the past 2 months way surpassed the total number of tutorials I’ve watched in my poly and university years. And I really thank God for those nice people who posted up those video tutorials! As tired and stressful it may be, I still feel accomplished after I am able to improve on the design week after week!
<td></td>
+
<br><br>
<td>3.2 Search Skills</td>
+
|-
<td>
+
| colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div>
*Research, learn and apply knowledge and techniques to resolve issues in assigned tasks.
+
|}
</td>
 
<td>
 
*Team review at end of iteration(Internal)
 
</td>
 
<tr/>
 
 
 
<tr bgcolor="cccccc">
 
<td><b>4</b></td>
 
<td  colspan="3"><b>Collaboration (or Team) Skills</b></td>
 
</tr>
 
 
 
<tr>
 
<td></td>
 
<td>4.1 Skills to Improve Effectiveness of Group Processes and Work Products</td>
 
<td>
 
*Share and give constructive feedback on overall and individual performance and suggest improvements.
 
</td>
 
<td>
 
*Team review at end of iteration(Internal)
 
</td>
 
<tr/>
 
 
 
<tr bgcolor="cccccc">
 
<td><b>5</b></td>
 
<td  colspan="3"><b>Communication Skills</b></td>
 
</tr>
 
 
 
<tr>
 
<td></td>
 
<td>5.1 Presentation Skills</td>
 
<td>
 
*Present prototype and project plan to client and supervisor regularly.
 
*Conduct interactive presentations for clients, supervisor and reviewers during project acceptance, midterm and final presentations.
 
</td>
 
<td>
 
*Feedback from client and supervisor
 
*Team Review at end of iteration(Internal)
 
</td>
 
<tr/>
 
  
<tr>
+
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2011T2_Imateam_midterm#Top|Back to Top]]</u></font></div>
<td></td>
 
<td>5.2 Writing Skills</td>
 
<td>
 
*Produce proper documentation of entire project implementation which includes
 
**Meeting minutes
 
**Reports – proposal
 
**User manual
 
**Wiki page
 
*Develop final deliverables, documentations and write individual and group self-reflections.
 
</td>
 
<td>
 
*Feedback from project manager
 
</td>
 
<tr/>
 

Latest revision as of 03:37, 20 February 2012

ImaLomsIsk.jpg






Our Thoughts.
"Follow effective action with quiet reflection. From the quiet reflection will come even more effective action."




Imahome.jpg Home   Imastake.jpg Team / Stakeholders   Imaover.jpgProject Overview   Imadocumentation.jpg Project Documentation   Imamanagement.jpgProject Management   Imaresources.jpgResource & Reference   LOMS & Reflections
Imaaarrow2.pngLearning Outcomes   Imaaarrow2.pngReflections          

Reflections

Team

Team
   

Together as a team of four, we’ve learnt so much on this incredible journey, and we’re only a little past the midway mark. Aside from the technical aspects that we’ve gathered, we’ve also learnt the following:

• Teamwork and communication – Being a small group has its pros and cons. One of its pros however, is that we’ve grown closer, and learnt to depend on one another and improve on our communication in the process. One of the initial challenges was that we were not communicating enough, which led to delays since some aspects of the development required the completion and coordination of another team member.

• Scope Manageability – As a team, we were full of ideas and brimming with confidence about our project. However, we also learnt to manage both our client and supervisor’s expectations, and how to be selective and realistic about additions or changes to the scope of the project. Nevertheless, the biggest learning point has been how as a team, we’ve learnt to consistently adapt our own expectations and goals to the various additions and changes to our project scope.

• Finding the middle ground – Even though we’re a small of team of four, each of us has incredibly strong opinions and capable personalities, which would ultimately more often than not lead to disagreements. However, a good thing is that we’re comfortable with each other and as a group, and disagreements instead led to even better ideas when we all ultimately try to find a middle ground.

Iskandar

Iskandar
   

This FYP has been an incredibly long, hard journey but one that I thoroughly feel proud and elated to be a part of. I’m sure every one of us in IMATEAM has learnt so much beyond our wildest dreams, but the best part for me has been to have gone through it with this team. I’ve learnt so much in terms of project management, both in terms of project scheduling and managing the team. Despite this only being the mid-point reflection, I’ve developed a tremendous amount of respect and admiration for my team-members and the amazing things they’ve been able to do for this project.

Learning Drupal is so very hard, but very rewarding in my opinion. Our team took a leap of faith with Drupal because of its potential in offering robustness and awesome websites, but also the potential opportunities it provides us in the team as individuals. After all, there is an incredibly huge demand for Drupal developers, but few in supply.

Felix

Felix
   

I have learnt a lot so far for this FYP. When we first decided to choose Drupal as our main framework, we did not realize that the learning curve for this particular technology is very high. Initially, my team and I were concerned that we would not be able to deliver best product to our sponsors. But we, as a team, worked together and helped one another. Subsequently, I learned that with hard work (and enjoyed the fun time I spent with my groupmates) and having full confidence in my groupmates’ abilities, we are able to face the challenges and resolve any problems we encountered along the way.

As a lead developer, I have acquired some knowledge of the Drupal modules. One of the major difficulties that I came across during the development process was not knowing how to start to custom code the 3rd party modules. First, I had to understand and be familiar with the codes of these modules so I know which part to modify to fit our project’s requirement. Some of the codes were very complex that it took me hours to just grasp what the codes are about. The other difficulty that I encountered was modifying the codes. In order to accomplish the task, I had to change the codes from a few files within the module.

Alicia

Alicia
   

The FYP journey has been a challenging but fruitful one for me so far. I have learned a lot throughout the duration of the project, both on the business and IT side of things. I assume the role of Business Analyst in the team, thus it is my responsibility to be in constant communication with our sponsors and supervisor. As our team is a small one, it is especially important that we manage client's expectations well to ensure that our scope is manageable. It is also important that we all take on more than one role and help each other out whhenever we can to ensure that the workload is evenly distributed. As a B.A., I also helped out with the technical side by developing the admin functions of our application.

This project has taught me to be patient and resilient. As we are tackling Drupal 7, a new framework that none of us had prior experience with, it was important that we got our foundations right. It was also crucial that we found the determination to try again whenever a function did not work as planned. A lot of effort had to put into research but they paid off in the end. Working on both the business side and technical side of things also taught me more about the importance of reconciling the needs and differences of these two aspects.

Stephenie

Stephenie
   

So far, this FYP journey has been a mixture of pain and happiness. To begin with, we are a really small team. Being a small team has its pros and cons. It’s really easier to communicate within a small team; we have no time to hold grudges with one another. We voice out our opinions and discuss everything as a team cause we know that we need everybody support in doing the project. Honestly, I am really happy to be in this team. Although we are really close friends and know each other strengths and weaknesses inside out, we are not afraid to step out of our comfort zone and volunteer to help one another. It’s really important to have a good, hardworking team that understand and support one another especially when we are working on a totally new language, which has a really steep learning curve, and have to manage client expectations at the same time.

As a lead designer, I am really stress at times because I am afraid that I am unable to meet clients or my team members’ expectations. Besides, designing in Drupal is not as easy as designing in Photoshop. It’s so much more challenging. The video tutorials I’ve watched for the past 2 months way surpassed the total number of tutorials I’ve watched in my poly and university years. And I really thank God for those nice people who posted up those video tutorials! As tired and stressful it may be, I still feel accomplished after I am able to improve on the design week after week!