CP2408 Project Part 2 - Iterations

Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due

CP2408 Project Part 2 - Iterations

Your team will continue the Lean UX process, following and updating your Lean UX Canvas, creating MVPs and running experiments to  complete 3 iterations.  Each iteration must be designed to test your specific assumptions.  Your assumptions should be focused on value rather than implementation. You will also complete an individual report. Use the templates provided.

Team Report

Iterations

Each Lean UX iteration should include an MVP and experiment specifically designed to validate your assumptions. You can choose whatever MVP is the most appropriate for testing your assumptions.

Your final MVP should be a clickable digital prototype with reasonable fidelity. You are not expected to run the experiment for your final iteration, but you must complete up to this point, including planning your experiment. For each experiment, include the following in your report:

•    Your chosen hypothesis and most important assumptions that you want to test

•    A screenshot or photo of your MVP with a clear link or reference to the source/export file for this MVP

•    Testing/interview plan. Your plan should be substantial; something your team can consistently follow.

•    Evidence of appropriate user testing. Provide photos of your testing to show evidence of implementing the GOOB principle.

o You must provide at least one video of a user test. This can be an online video conference recording or a video of a face-to-face experiment. You only need one video in total, not one per iteration.

•    Details about users and test data. Provide an appropriate collection of your 'data', like a table containing the things you recorded for each participant in your test.

•    Analysis of the test results that show lessons and outcome of the tested assumption(s).

Restate your assumption

State the result of your test. Is your assumption True, False or still Unclear?

•    Direct implications for the next iteration (what does this result/learning mean we should do next?)

Lean UX Canvas

As you iterate, you should learn more about both your chosen problem and the Lean UX process. In this section, describe how you updated your Lean UX Canvas and include any newly created or modified box content. For example, you might learn from an  experiment that one of your personas was not suitable and a different one is more appropriate. Discuss this and include the new personas.

Note: It is unreasonable to think that nothing in your canvas needs changing. If you find all your assumptions were accurate, then you probably did not apply the Lean UX process effectively.

Do not simply provide your Lean UX Canvas because then how would we know what you’ve learned and changed? In this section you must explain what you have changed and why. The most appropriate way to present this is to provide 3 things for any change: the original content, the revised content, and the explanation.

Teamwork Summary

Reflection

At the end of each iteration, conduct a team retrospective, and take good notes on your team's experiences. In this section of the report, provide an overall summary of your retrospectives, describing what went well, and how you think you could have worked better as a team and what things you changed about your process. Don't just say you  should have worked harder or started earlier. Be serious and thoughtful. Include at least two of the Lean UX principles (from chapter 2) in your discussion.

Meeting Evidence

Your team should conduct regular meetings to complete this project. In this section, include meeting minutes containing the core details: time, date, attendees, agenda, decisions and action items. This does not need to be extensive, but it must clearly show that fruitful meetings were conducted that each had clear outcomes and actions.

Individual Report

Each team member must complete an individual  report outlining their contributions and demonstrating their understanding of Lean UX. Complete the template provided and submit this individually. Any student who does not complete the individual report will get zero marks for the group component of this assessment item.

Complete the table of team contributions including work % estimate so you can attribute quantity/quality of work. This must be completed and will be used to adjust subject results in cases of inequitable work distribution.

As in your Sprint Reflection assignment, use Gibbs’ reflective model to reflect on and document two significant personal experiences from this project: one related to teamwork, and one more individual.

Describe the ways in which you personally have developed in two of the Lean UX principles. Many of these are team- focused principles, but this section is about your individual improvement and learning. Do not merely describe the principles. Describe how and why your understanding and application of these principles has improved.

Integrity

The work you submit for this assignment must be your own. You are allowed to discuss the assignment with other students and get assistance from your peers, but you may not do any part of anyone else’s work for them, and you   may not get anyone else to do any part of your work. Work that is too similar to another group’s work or work from an outside source will be dealt with promptly according to JCU procedures for handling plagiarism.

Do not use generative AI (GenAI) tools like ChatGPT, Copilot, Grammarly, etc. to produce any of this assignment because this would limit your learning and would mean that you would not achieve the goals of the assignment. You will not receive high marks if your work sounds like it was generated by AI.

Students who “freeload” by letting other team members do an unfair portion of the work will have their marks reduced. Students who do not manage the teamwork aspects effectively (e.g., are unnecessarily difficult to work with) will have their marks reduced even if they do a lot of work. If there are problems in your group that you cannot work out together, please discuss this with your lecturer early on. Do not wait too long to deal with any issues.

Submission

One person per team should submit the team project as separate files:

• project report as a PDF or Word document,

• movie file of a single experiment test,

• zip file containing all the MVPs, which should be appropriate source or export files saved from whatever program(s) your team used. Your MVP files must be named logically and referenced in the report.

Do NOT include the PDF in the zip file!

Each person must submit their individual report individually.

Any student who does not submit an individual report will get zero for the group project component.


发表评论

电子邮件地址不会被公开。 必填项已用*标注