Introduction
The team has been working hard on the development of the product, Simple Event Planner (SEP). Throughout the process of developing, the team gained and learnt from the various problems encountered, because problems later became learning points. The team learnt that software design was a crucial stage in product development and that for a successful product demonstration, the selling point of the product has to be not only identified but also well analyzed.
Importance of Software Design
A good software design is not easy to achieve as many considerations needs to be taken into account to. Still, the team managed to finish the necessary software designs, such as the architecture diagram, the class diagram and the sequence diagrams. Furthermore, because there was a clear idea and well-timed plan for the implementation of the product, the team was able to proceed with the implementation of various portions of the product at the same time. This maximized the resources that the team had and allowed for a smooth implementation process.
Despite that team already specifying the software design, there were much needed modifications done during the implementation process. Thus, it was important for the team to constantly update the software design, especially the low level designs, such as the product APIs. This was essential towards the wholesome implementation of the product because whenever the team made references to the product APIs and other relevant updated information, the whole team would be at the same stage of progress.
Selling Point of the product
A software demonstration is considered successful only when the targeted audience is left wanting and desperate to purchase the revealed product.
To achieve that, the team must have a complete understanding of the product and the issues faced by prospects and other customers. This aids in connecting with the audience. Well-told stories are always successful with audiences, so the team chose to demonstrate the software with a story-based structure. Finally, as always, practice, practice and more practice for a flawless presentation.
The team must let the audience come to a consensus that the team is a smart, self-aware group of people doing worthwhile things and ‘why’ the product would matter to them. This is crucial in creating a ‘eureka’ moment for at least one member of the audience. This person would then leave with a mission to take part in the product’s success, either by providing a critical feature idea, a hire candidate, potential partnership, or — in the case of a demonstration to investors — the desire to fight to invest.
Conclusion
Given the opportunity to develop a workable product as a team, I was able to put theory into practice. With that, I have a clearer and better understanding of the theory and thus, am able to better appreciate knowledge taught by lecturers. For example, I had previously not realized that software design had such great impact on the developing process. It was this hands-on experience that provided these new insights.
Being an experienced developer, I was able to avoid repeated mistakes, allowing me to save more time on debugging, which is a process that at times seemed to be quite frustrating.
Furthermore, now fully aware of the key points for a successful software demonstration, I am sure to put it into good use and practice hard to achieve my goals for the demonstrations.
Friday, March 23, 2012
Saturday, February 18, 2012
Blog #2: Reflection on CS2103T project
At this point of time, our group basically had a few virtual group discussions and a few physical group discussions. Base on those discussion that our group had together, the areas that our group had identified as challenges are communication, experience and skills, amount of time available & team’s work ability and lastly, team management. I will be discussing on how is experience and skills a challenge to our group and to propose some solutions to tacker the challenge.
Our team is an interdependent-level work group, whereby we rely on each other to get work done. Each member had their own roles and shared the responsibilities. Thus, our group coordinate with one another to produce an overall product. It is important that each member is able to produce the same set of quality outcomes; for we focus on the outcomes of the overall unit rather than an individual’s accomplishments.
However, base on the different background that our team member has, it will be unfair to assume that all member has the set same of experience and skills to produce the same outcome. For example, it would be unfair to expect a member with little or no experience to produce the same outcome as another member with more experience and skills. However, this would cause unfairness in another way round, one could not expect the member with more experience and skills to do more work or to compensate accordingly to the another member. That would certainty affect the overall product adversely. A balance between them is required!
This contradiction impact would be further increased and enlarge during the initial implementation of the product, whereby most of the work will be programming. Though at some stages,there will be certainty be some documentation work and testing to be done. It would be a challenge for our group to allocate the task when our concern is to maximize on the usage of the resource that we had. Which could be the manpower and the amount of time we had.
The proposed solution is to identify the strengths and weakness of each individual member, and each group member should try their best to explore the various areas required for their allocated task. One should not use their weakness as an excuse for not meeting the expectation or dateline. Furthermore, by knowing the strengths and weakness of each individual member, one would know who to seek advice and help from.
In addition, our team should trust each other with important and meaningful responsibility, these clear and meaningful responsibility will allow team members to enhance their trust and confidence. By enhancing the self-confidence and trust within the individual team members, I believe this will motivate individual team members to work hard towards the same goal that we each hold and shared.
To conclude, though each of our team members had different experience and skills or various area, which will be taken into consideration during task allocation for the product. However, we should not blame our weakness for not achieving the outcome. I strongly believe that, our team is capable of overcoming the identified challenges.
Tuesday, January 31, 2012
Saturday, January 28, 2012
Blog #1: Communication and team behaviour
Communication is very important in our lives. Humans, unlike eagles, do not live along; thus being able to communicate well is an important skill that each individual must equip himself or herself with. Humans feel that they are capable to achieve greater task as a group, these concept can be seen through all those traditional childhood stories.
The principles taught during class were especially useful to help me understand more on communication and also, the different types of team behavior. Each teammate will have a unique role to play with, and by knowing which role one’s being assign to; not only could it increase the bonding within the group but it could also gives an identity to each teammate.
During last week’s lesson, our group has been told that our presentation is actually on 27th Jan 2012 instead. We were caught in surprise, as it’s something unexpected. We greatly accept the fact and Terence said that we could start researching on the topic during the weekends and also. There will not be any meetings during Chinese New Year as we feel that it’s a time to be with family. Also, we have all decided to use Dropbox, an online storage application, to store our files.
We had an online meeting on Tuesday night to assign and allocate the presentation slides. We were supposed to use MSN as our communication medium but half way, we decided to switch to Google Documents. For it not only always every one to edit on the document but also, but it also have a function to allow us to communicate with each other. I’s much more convenient.
We use the scope for the PowerPoint presentation and the outline of what each speaker should do as a guideline. The outline was sent to us by Terence days before for he is unable to us on the discussions.
The discussions went well, everyone was greatly involved in the discussion. We manage to divide the presentation into four parts. Though during the meetings, there’s some clarification on the scope of the presentation, we manage to come to an agreement of what it means. Everyone paid attention to each other during the discussion and everyone is very positive and contributes well. At the end of discussion, after task allocation, we decide to meet up the next day (25th Jan) and have rehearsal on 26th Jan afternoon.
After the discussion has ended, I decided to start on my slides so that the next day I will have something on my hand.
During Wednesdays meeting, everyone continue on their slides and clarify the doubts together they encounter during the preparation of the slides. After the meeting, everyone is very confidant on his slides. The last part of the presentation is the script and the rehearsal part.
During the final meeting, I was not fully prepared. My script was not finalize yet and had to make them wait for me. I really appreciate their understanding and that they do not give me pressure while waiting for me to finish my script. Xiang Yun volunteers to collaborate our slides together. After the rehearsal, I realize my slides are too long and I need to shorten it.
Although I tried to shorten my scripts, I still overrun during the actual presentation day. I really want to apologize to my group mate when every one of them tried their best to finish their part within 5 minutes.
Here’s my conclusion about my group mates base on the few meetings and lessons that we had for the past few weeks. Terence, our group leader, he did well in his part as a leader and is very responsible. Joel, though he is not the one who will initiate things but he will be there when you needs him and do what is being told. Xiang Yun, he prefers listening rather than talking and voice out the areas that we might miss out during discussions.
Base on the meetings that we had, I felt that everyone is trying their best to contribute to the group and also, to have a better understanding of each other. I feel comfortable as a part of the group.
Tuesday, January 24, 2012
Monday, January 16, 2012
Important Blog Post
Week 3
Blog #1: Communication and team behaviour
· For your first blog, think about the principles of communication and team behavior and reflect on how they can work for you. Note your observation of individual and team behaviour and how interpersonal communication takes place during meetings. Is there any specific area which you may like to improve? You may also reflect on how intercultural issues affect communication.
· In your responses to the blogs of your group and/or classmates, ask yourself if you agree with their viewpoints? Give your reasons and respond courteously and tactfully.
Post by: 28 Jan (Sat)
Respond to the blogs of your group members by: 1 Feb (Wed)
Week 6
Blog #2: Reflection on CS2103T project
· For this blog entry, think about the project discussions that you have had so far. What are the challenges that your group faces, the problems you encounter and the solutions that you think may work.
· In your responses to your group members’ blog entries, give your opinions on what they have raised focusing on one particular area which has not been covered by the rest of the team.
Post by: 18 Feb (Sat)
Respond to the blogs of your group members by: 22 Feb (Wed)
Week 10
Blog #3: Reflection on software demo preparation or project development
· For this post, describe in detail your learning points relating to the preparation of the software demo or the development of your product. How is what you have learnt applicable to future software demo or product that you may develop?
· In your responses to the blog entries posted by your group members, provide an objective evaluation of their posts. Be diplomatic and considerate in your responses.
Post by: 24 Mar (Sat)
Respond to the blogs of your group members by: 28 Mar (Wed)
Subscribe to:
Posts (Atom)