Our project part II

Zendayalovers team:

• Oscar Fabián Ramírez González A01630024
• Victor Jaret Guido Alvarado A01630603
• Francisco Mariano Amezquita Ramos A01634495

Obtained knowledge

Different perspectives are good! Once we get started with the project, it is kind of complicated to listen to other point of views due to the approach and acknowledge the team project management has taken and also taking in mind that the team fall in love with the project (because it is theirs, obviously). In a way, it’s always good to listen to different feedback because even though we think the product might be complete or perfect, this can be seen from different angles that may say the opposite. In general, the project itself has been approved by most of the future users, of course with some functional improvements.

What about the process?

The process of interviewing can be complex, in terms of tolerance and durability (time speaking, how much can it take). This process can be considered as the first approach to human interaction within the project. Something to take in mind is that the process of interviewing can help in such way that it can be, in certain way, a prototype that will tells us if the product itself can whether work out or not.

More than one interview!

This is about a project, a project that must fulfill some requirements in order to became a good project, so doing one interview is just not enough, this because the amount of information that you can obtain by doing interviews grows with the ammount of interviews you do, the more interviews the more points of opinion you got about your project, so this is why decided to make as much as interviews as the softwared required it.

With the first interviews we tried to obtain a little bit of information about the opinion of the users about the software, this because we wanted to know their opinion about it, as soon as we realized that the software was interesting to the users we decided to change the objective of the interviews and focused them on the user experience, questions like: How would they like to see the software?, What would they like about the software?, How to make the software more attractive? and If they were willing to use the software.

At the end all the information collected by the interviews made us realize that the software was a little bit more complex than just developing a software, like nobody would use it if it is not attractive and interactive, this is why we decided to change the objective of the interviews as time progressed, because we needed more information from the users that would help us to make a good software.

A small change for the process

Through the interviews made with our clients, we specified first to our promotor that we will be calling main client, and eventually he will be selling the systems to clubs that require this kind of services because they want to improve the use of their courts, with have been specified previously on our first deliver.

The short story for out connection with the clients is that at the beginning the first presentation we were able to present the problem and our system solution at the same time we were very technical about it and we could just have answer him lightly, but we do not know at the time. We concluded that we have to know to who we are addressing, because no clients are equal. We consider that we have many types of clients, but at the end we want to provide them a service and the way that we get them is up to us and our previous research.

Current use cases

Diagrams

The following diagrams are different looks for our system, the way we see it it is more easier to look and explain it with this, they even work for explaining to our clients.

• 

•