Confirmation of discussed subjects of second demo

Subjects we discussed during the second demo:

1. Creating a demo version of our application. Deploying the application on a hosting service. This is done, we did this on 14 march.
2. Visit the lab for a tour and to present our product. We scheduled this for 25 march.
3. The product owners promised to provide us with better data & role definitions. They did this.
4. Navigating our application. The product owners prefer scrolling over clicking. Does the product owner agree with this summary?

Answer: The product owners agree with this list. They do not have any comments.

Confirmation of project structure 2

This project lasts until 22 march. We have now entered our final week. We might not be able to deliver a complete application. We are limited to our schedule. Is the product owner aware of these restrictions?

Answer: The product owners again understands the project structure. They would like to use this software, but did not expect that we deliver a completed project. They also understand that we probably cannot provide maintenance after completion of the last project week. If the product owners choose to use this software, they will take responsibility for any further development.

Clarification of project definitions 2

Definitions are important for this project. Different definitions lead to different implementations. We asked the product owners to clarify the following definitions:

1. How many departments can an analyst be a member of? Is every analyst member of the general department? How does this work for team managers?
2. Can an analyst view all tasks or only the tasks of their department. How does this work for team managers?
3. Can an analyst check off all tasks or only the tasks of their department. How does this work for team managers?
4. Can team mangers only edit & create tasks within their department, or also for other departments?

Our thoughts: We think that an analyst should initially only see and be able to check off tasks that are relevant for them, otherwise the meaning of a department would be neglectable in this application. Same for team managers, they can only edit and add tasks within their own department. Users can see other tasks, but not by default.

Product owner:

1. Every Analyst is member of the general department.
2. Analysts can be member of multiple departments.
3. Analyst can view tasks of their own departments, but also of other departments.
4. Analyst should only check off tasks of their own department, however, it is not required that we restrict access. Analyst will handle this themselves.
5. Team managers can view, check off, and edit/create tasks for all departments. They will probably only manage their own tasks in real life.

Clarification of additional requirements

During our meeting we discussed five other requirements:

1. Notes after check off.
2. Email notifications.
3. Excel import & export.
4. Calendar integration.
5. Version history of tasks.

We did not discuss this requirements in detail yet. Can the product owners provide more clarifications of these requirements? We might not be able to implements all these requirements, due to time constraints. Which requirements have priority?

Product owner: Notes after check of and version history are the most important requirements. Integrations are nice to haves. They understand that we might not be able to implement all these requirements. Explanation per requirement:

1. Notes after check off: for noting down observations.
2. Email notifications: mail once per week with upcoming tasks per department.
3. Excel import & export: export data to excel to be able to make backups.
4. Calendar integration: can be combined with 2, more ways to see upcoming tasks.
5. Version history of tasks: important for keeping proper records. Would like to have.

Any other questions or comments?

No additional questions or comments.