Collaborate with your software developer
Posted: Sun Dec 22, 2024 8:52 am
2. Make sure that everything is legally checked off
From the contract, the editing agreement to who owns the intellectual property, for example. We started off very enthusiastically and these kinds of things had not yet been sufficiently ticked off. Arranging an editing agreement afterwards is quite difficult, because this affects new developments and/or expansions and it can cause delays. In the end, we managed to arrange everything quickly, but the process took longer because of this. I would definitely recommend looking at this carefully at the beginning of the process and having everything contractually in scope . This ensures clarity regarding the process for all parties.
Dare to make choices. Only in this way you will reach your goal.
3. Make sure you have the editing agreement ready
This is crucial, because otherwise it will hinder software development. Especially if you work for a corporate organization, it is worth paying attention to this in advance and involving the right people in the project. In view of the GDPR, a processor agreement is necessary if you want to link systems or use privacy-sensitive information.
4. Do not put a robot on the floor until the basic software has been installed and tested
Otherwise, there is a robot and nothing more. We really chose to first test and fine-tune in the marketing department and only when we were satisfied, we added Pepper to the hospitality team and put it on the floor with basic software. Pepper was immediately deployable and delivered the added value we had in mind from minute 1.
5. Adding a robot to a workplace has an incredible impact and generates a lot of feedback
We got responses like: “Wow, is this robot going to replace your job?” or “A robot, wow cool! What can it do?” The right communication in advance to everyone who comes into contact with the robot is crucial. That way everyone knows the goal, the why and the result that it should ultimately deliver. We did not expect that a robot would have such an impact, despite the fact that we already use a lot of new technologies.
We informed all directly involved colleagues extensively in advance and after Pepper's arrival informed all colleagues from the head office. What I would do differently now is that I would also have sent this last group an information mail before Pepper's arrival. I think that would have allowed us to answer questions that were now being asked to the reception team in advance.
So, is this robot going to replace your job?
6. Give someone from the team the space to just listen and observe for a period of time
This ensures that the person really has time to experience what users say and what answer is given by the robot and what reactions it produces. With this information, the software developer can get to work to provide the robot with the correct and necessary input.
That sounds obvious, but this is a project where you really have to work together. Together you create the perfect product if you are open and honest with each other and listen well. Define the sprints together and evaluate them together. Determine what has been achieved, what has not, what is going well and what still needs attention. Every two weeks we sat together with the team to discuss the sprints and share experiences with each other. We went through all the points using a fixed checklist. In this way everything was also discussed and we were able to quickly make progress together.
8. Be open to opinions
For the positive, but certainly also the negative opinions. If you clearly have the purpose of the robot in mind, you can also answer both opinions. Our goal was and still is very simple. We are curious about how adding a robot to professions in which the human aspect is central works. We understand that not everyone is positive about that. Negative opinions have also been valuable to us, because they provide insight into what people find important and how they view new innovations within our industry.
We responded to all of these comments. We gave people the opportunity to see Pepper at work. Some people actually did. Burying your head in the sand and not responding to negative comments is dangerous. Take it and respond to the best of your ability.
9. Realize that when it comes to example of whatsapp number in philippines deploying a robot host, you are often entering the management domain
This affects much more than just welcoming and receiving guests. It is often an innovation. Adding a robot as an employee has an impact on the image of your organization. This type of process often requires more time and more explanation that leads to concrete decision-making.
Do you have experience with the use of robots? I'm curious about that! Feel free to leave a comment.
Many of the principles of the new privacy law (GDPR or AVG) have to do with the correct documentation and lawful conduct. However, one of the principles also requires support from technology. You must be able to give the consumer insight into the data that you have about him and also give him the opportunity to adjust, delete or move this data. This is difficult for many organizations, because personal data is spread across multiple tools. A simple solution for this, in my opinion, is the use of a data management platform (DMP).
It is no longer news: it has been in force since May 2016, but from May 2018 organizations are accountable for compliance: the GDPR. There is already a lot of blogging about it, especially to summarize the 156-page document in clear language.
y with the new legislation. There are undoubtedly other solutions and I am curious how you approach it. How do you ensure that you comply with the GDPR in May 2018.
From the contract, the editing agreement to who owns the intellectual property, for example. We started off very enthusiastically and these kinds of things had not yet been sufficiently ticked off. Arranging an editing agreement afterwards is quite difficult, because this affects new developments and/or expansions and it can cause delays. In the end, we managed to arrange everything quickly, but the process took longer because of this. I would definitely recommend looking at this carefully at the beginning of the process and having everything contractually in scope . This ensures clarity regarding the process for all parties.
Dare to make choices. Only in this way you will reach your goal.
3. Make sure you have the editing agreement ready
This is crucial, because otherwise it will hinder software development. Especially if you work for a corporate organization, it is worth paying attention to this in advance and involving the right people in the project. In view of the GDPR, a processor agreement is necessary if you want to link systems or use privacy-sensitive information.
4. Do not put a robot on the floor until the basic software has been installed and tested
Otherwise, there is a robot and nothing more. We really chose to first test and fine-tune in the marketing department and only when we were satisfied, we added Pepper to the hospitality team and put it on the floor with basic software. Pepper was immediately deployable and delivered the added value we had in mind from minute 1.
5. Adding a robot to a workplace has an incredible impact and generates a lot of feedback
We got responses like: “Wow, is this robot going to replace your job?” or “A robot, wow cool! What can it do?” The right communication in advance to everyone who comes into contact with the robot is crucial. That way everyone knows the goal, the why and the result that it should ultimately deliver. We did not expect that a robot would have such an impact, despite the fact that we already use a lot of new technologies.
We informed all directly involved colleagues extensively in advance and after Pepper's arrival informed all colleagues from the head office. What I would do differently now is that I would also have sent this last group an information mail before Pepper's arrival. I think that would have allowed us to answer questions that were now being asked to the reception team in advance.
So, is this robot going to replace your job?
6. Give someone from the team the space to just listen and observe for a period of time
This ensures that the person really has time to experience what users say and what answer is given by the robot and what reactions it produces. With this information, the software developer can get to work to provide the robot with the correct and necessary input.
That sounds obvious, but this is a project where you really have to work together. Together you create the perfect product if you are open and honest with each other and listen well. Define the sprints together and evaluate them together. Determine what has been achieved, what has not, what is going well and what still needs attention. Every two weeks we sat together with the team to discuss the sprints and share experiences with each other. We went through all the points using a fixed checklist. In this way everything was also discussed and we were able to quickly make progress together.
8. Be open to opinions
For the positive, but certainly also the negative opinions. If you clearly have the purpose of the robot in mind, you can also answer both opinions. Our goal was and still is very simple. We are curious about how adding a robot to professions in which the human aspect is central works. We understand that not everyone is positive about that. Negative opinions have also been valuable to us, because they provide insight into what people find important and how they view new innovations within our industry.
We responded to all of these comments. We gave people the opportunity to see Pepper at work. Some people actually did. Burying your head in the sand and not responding to negative comments is dangerous. Take it and respond to the best of your ability.
9. Realize that when it comes to example of whatsapp number in philippines deploying a robot host, you are often entering the management domain
This affects much more than just welcoming and receiving guests. It is often an innovation. Adding a robot as an employee has an impact on the image of your organization. This type of process often requires more time and more explanation that leads to concrete decision-making.
Do you have experience with the use of robots? I'm curious about that! Feel free to leave a comment.
Many of the principles of the new privacy law (GDPR or AVG) have to do with the correct documentation and lawful conduct. However, one of the principles also requires support from technology. You must be able to give the consumer insight into the data that you have about him and also give him the opportunity to adjust, delete or move this data. This is difficult for many organizations, because personal data is spread across multiple tools. A simple solution for this, in my opinion, is the use of a data management platform (DMP).
It is no longer news: it has been in force since May 2016, but from May 2018 organizations are accountable for compliance: the GDPR. There is already a lot of blogging about it, especially to summarize the 156-page document in clear language.
y with the new legislation. There are undoubtedly other solutions and I am curious how you approach it. How do you ensure that you comply with the GDPR in May 2018.