• 6 Software developers:

      brainstorming -> dissatisfiers, satisfier and delighter ✅ 

• International agents:

      questionnaire -> delighters & satisfiers ❌ 

• H. Massar (HZ marketing):

      Interview -> satisfiers & dissatisfiers ✅ 

      Brainstorming -> dissatisfiers & satisfiers ✅ 

      Prototyping -> satisfiers & dissatisfiers ✅ 

• Around 5 close acquaintances/relatives:

      Prototyping -> satisfiers & dissatisfiers ✅ 

      Field observation -> dissatisfier, satisfier & delighters ❌ 

• Teachers:

      Brainstorming -> satisfiers, and delighters ✅                                  

• Previous website  

      Archeology -> dissatisfiers & satisfiers ✅ 

• Laws

      Reuse -> dissatisfiers ❌

• Info.hz.nl website (servers)

      Reuse -> dissatisfiers ❌


Bogomil and Axel – Interview with the client (H. Massar – HZ Marketing)
Jonah – Brainstorming with the client (H. Massar – HZ Marketing)
Andrew - Prototyping with the client (H. Massar - HZ Marketing)
Melvin – Prototyping with close acquaintances/relatives (his parents and sister)
Aadya – brainstorming with teachers (Daan during the first demo)

Result: During the interview, Bogomil was asking the questions that we were prepared and Axel noted down everything that was important about the requirements. Here are the notes from the interview:  

• He wants a website with more structure (categories, clustering of info, ability to sort stuff, etc...).
• But this also depends on us, we can do as we like, how we think it could be better.
• There is a corporate-wide document with guidelines regarding the theme of HZ websites. He should send it at some point. We can base our design on that. But basically:  
  • White: for background 
  • Blue: for the text and front 
  • Orange: for things that stand up like buttons or links. 
• We can also base our design on these websites: info.hz.nl/elise , info.hz.nl/philip & all the HZ websites 

• The website should keep the same domain name and server. But it's not set in stone, we can do it another way if we think it will be better.
• The easier the website is to deploy, the better it is.
• How the deployment will work: we will write some instructions/guidelines, send them along with the project to H. Massar, who will then give it to the HZ IT department (not our teacher, the "real" IT department) who will perform the required steps to deploy the website.
• Again, these are just some guidelines, we can decide to do things in another way. 

• All the existing content from info.hz.nl/webshop should be on the new website. 
• It would be great to have video previews. Example: you upload a link to a youtube video, and it's playable (embedded) on the website. (and there is a way to get the youtube link, like some text under the video) 

• English is the main focus.
• There are English and Dutch content upload on the website, but Dutch can speak English.
• A multilingual website is not really important because there is no content in other languages other than English and Dutch.
• It's a delighter: the ability to sort content by language.
• It's a delighter: going all out, and make a real multilingual website, not just a text translation 

• No time constraint. They already have a working website, there is no need to rush. Obviously delivering it sooner is better but delivering at the end of the 4th quartile is perfect. 

• Multiple accounts for the different administrators (HZ marketing employee).
• Ability to know who uploaded what and when.
• Ability to change account information (password, maybe email, etc...). 

• The website needs to work on all the mainstream websites (chrome, Firefox, edge, maybe internet explorer, etc...).
• Even though the international agent will not really use the website on their phone/tablet, it would be great to make a responsive website.
• It's a delighter: not every international agent has a powerful PC and internet connection, so we need to keep an eye on resource utilization. Ex: avoid displaying high-resolution images.

Results:

• One of the first points H. Massar came to tell us, was that the site primarily must be used as a point of file management. The International Agents need to be able to download the files on there and spread them by doing their work. The site is almost an extension of their business card in that regard.
• The feature we came up with, a chat function with the Agencies Bureau, has been disapproved. This is due to the lack of workers to manage such a task and due to time-zones.
• A main requirement by our client was the quick and easy access to files and data inside of the site. The webpage shouldn’t be hard to navigate, nor difficult to download from.

Results:

• One of the main points undermining many of our requirements is that the client wants the International Agents Portal only to be accessible to the Agents and Marketing Directors themselves, not to any other users.
• A dark and light mode might be a good addition on top of the visibility of the contents of the pages.
• The requirements for uploading files need to be adjusted, so that a Marketing director can easily know the format, size and resolution of brochures and posters.
• The social media links should be on the bottom of the pages, instead of at the top. This looks more professional.

Results:

• Mother: Melvin’s mother indicated that the navbar and content of the site was quite narrow. She would like to see a wider interface that is more weighted towards the center instead of to the left. She also thinks that the photos should be bigger.

• Father: Melvin’s father indicated that he would expect to be able to search for content. He also said that he would want the ‘How to apply?’ link in the navbar inside a dropdown because the other content is also in a dropdown. He would expect a button that changes the site's language as well but from what Andrew gathered in his interview with Hugo we concluded that this would not be a necessary feature. Finally, he said that it should be operable on any device like mobile or tablet and that there should be less white space on the sides of the body of the page.

Results: During the first practice demo of our project, we presented a PPT to Daan in which we addressed the different documented data we had for our project.

In regard to the above mentioned, Daan suggested that we make our ‘ist’ diagram less technical and then discussed on how we could do that to make it better and more relevant. The rest were given a thumbs up.