Scribd
Upload
53 views2 pages

Critique Favourite Presentation From Peers: Reflection

Group 4's presentation on their Easy-Pay project stood out. They built a simple prototype that clearly explained how the financial application would work and its usefulness. All team members participated in the presentation, allowing the roles of each to be understood. While the idea and application workflow were conveyed, more technical details on the technology being used and inclusion of use cases/user stories could have strengthened the presentation.

Uploaded by

Jason Haha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
53 views2 pages

Critique Favourite Presentation From Peers: Reflection

Group 4's presentation on their Easy-Pay project stood out. They built a simple prototype that clearly explained how the financial application would work and its usefulness. All team members participated in the presentation, allowing the roles of each to be understood. While the idea and application workflow were conveyed, more technical details on the technology being used and inclusion of use cases/user stories could have strengthened the presentation.

Uploaded by

Jason Haha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Critique favourite presentation from Peers

My favorite in-class presentation should be group 4's presentation. Their project title
is Easy-Pay. What they need to do in their project is they need to build up a system
that helping people who work in the financial corporation to process transactions by
the IT system.

There are two things that I especially like about their presentation. One is they build
up a simple prototype and include it in their PowerPoint. With the prototype, they can
clearly explain how the application could be used in a financial aspect and why it can
be useful. The other thing I especially like is all of their team members present during
that time. I can know each of their roles via the presentation. 

There are two things that I would suggest they improve. First, I think they need to
include more technical knowledge or theory in their presentation. Although I know
their idea and how the application works, I also prefer to learn more about building
the application. In the presentation, it seems they haven't mentioned the technology
they are preparing to use to develop their application. I would also suggest that they
include some use cases and user stories in their presentation. With the use cases and
user stories, we can better understand the user's scenario and get the idea they bring it
up quickly.

Reflection
 
 
My contribution to the prototype development is drawing the layout of the prototype
of our application. For the presentation, I also build the ppt and represent our team to
speak at that time.

Our capstone project is just building our project, and we have no client in this project.
We still use the prototype with our tutor because we found it very useful to express
our idea. With the prototype, our tutors and other people can what the application is
about and how's it work even we haven't built up the system yet. 

I would be involved more in the coding of our project, and I will include more of the
technical explanation in the presentation next time. Iteration 2 is coming, and we
should build up to something that the application can show to the tutor and professor.
Since the main page prototype is completed, I would build some prototypes for other
systems in our project, for example, the payment system.

By using prototypes, we can express our ideas clearly. Another thing I would like to
comment about using prototypes is it is handy during the project discussion. We can
modify it quickly, and every one is useful to understand it.

You might also like