Remember that you only have six weeks for the project work. It is hence essential that you get started immediately, and that you organize your group collaboration and design and development process in the best possible way. Your group is to select one of the two provided cases. Beyond a few fundamental requirements provided in the cases, it is up to your group to ideate, prototype, and decide how you will design and develop a solution that best addresses the selected case.
How you organize the collaboration within your project group, and the design and development process will often have a large impact on the result. In the design and development process, the following “design toolkit” contains methods that might support you in activities such as defining needs and requirements, ideation, prototyping, and usability testing. Further, the following tips may be useful when organizing the overall aspects of your project work.
You can use the following instance for the project work: https://verify.dhis2.org/in5320/
We encourage you to work through several iterations. In the first iteration, the focus should be on designing and developing a minimum viable product that addresses what you see as the most fundamental aspects of the case. Consecutive iterations of design and development can focus on improving or adding additional features that you argue are relevant given the challenges or workflows of the end-users described in the selected case. Such an iterative approach ensures that you have a solution that, at least, provides a minimal solution at the end of the project. An important part of the process is to identify how to best divide the work among your group members to work as efficiently as possible while making sure that everyone is part of all of the major decisions. To this end, it is important to have frequent meetings and to do all larger ideation and requirements-definition-related activities together as a group.
You will also find that it is important to iterate between creative ideation and prototyping of potential features that may be relevant to support the end-users in your case, and investigating and testing what is feasible given the technical limitations of the DHIS2 APIs and platform resources. Often, one needs to balance between what would be the “ideal” features to support the end-users, and what is possible given technical limitations and the limited time you have for the project.
You can get help with the technical aspects of your project (e.g., APIs, DHIS2 app platform, UI library) on the seminar groups.