There is certainly a need to take priorities into account in each job so that you can set the correct order of tasks during the time required to complete the project. Therefore, it is important to determine what is relevant to our overall understanding of the work done. Are they necessary things, or are they just part of the vision of the ‘perfect’ project? Creating a hierarchyof prioritiesis definitely the best solution for organizing our future goals. Then I recommend dividing our ideas into separate categories. First, get to know what comments are.
What are notes for VR / AR/XR / MR apps?
They represent a set of any inconveniences observed in the target application. Whether they are specifically problems related to the operation of the application itself or, perhaps, the implementation of the presented vision itself, does not matter here. It’s just all of our observations that we/the customer think currently deviate from what our final product should look like. They include all errors, suggestions, and so on.. Anything that catches your eye that we/the client thinks should be added/corrected / changed. Making a list of comments is very important. We all want our apps to look their best, and making a list like this will certainly help us do that. Creating a satisfactory target product is, after all, a kind of business card for our company, and every satisfied customer confirms our reliability in proving valuable products. Therefore, we never downplay any comments from our partners. However, it should be borne in mind that how we approach their implementation is a matter of some limitations. Therefore, it is important to establish them first, and then assess the actual need for their implementation, taking into account the implementation time frame, expected result, and costs associated with their implementation. This allows us to effectively compare the needs of our partners with the real opportunities that arise from these limitations, and come to a common compromise related to the implementation of the tasks set. The smooth operation of the app and the fulfillment of its tasks is always the number one priority for us. But in order to realize this priority, We need full cooperation with our client. We must clearly understand what is included in the established assumptions and what part of the written comments exceeds them. Therefore, at such moments, we review the list of comments together and divide them first of all into certain categories.
Errorsinthe VR / AR / XR / MR app
This is a category of comments that is part of the inconvenience associated with the operation of the application on the customer’s side. An error was found, the application freezes, or the requirements that follow from the documentation are not met. These are comments that the customer takes upon himself, the repair of which is primarily due to incorrect implementation of assumptions related to the implementation of the project. Of course, such corrections are in no way associated with any additional costs on the part of the customer, and the customer assumes full responsibility for correcting them. Despite application tests, it sometimes happens that some error eludes us or occurs infrequently enough that we can’t detect it in the process. Therefore, we check each such remark by checking the cause of the given error, and then enter the solution. It also happens that an error may be caused not so much by incorrect operation of the application itself, but, for example, by incorrect calibration or processing of equipment. In such cases, we simply inform the customer about the cause of the error and tell them how to handle the vr headset so that the problem doesn’t occur again. Working with VR glasses every day, you get into a certain routine, forgetting about the problems that for people who often encounter this technology for the first time, may not be obvious. So we check every attention and always presentsolutions that will not only make it easier to use your glasses, but also allow you to fully use the potential of the app we are creating.
Suggestionsfor VR / AR / XR / MR software
They are an element of the list of recorded comments that arise from assumptions that go beyond the scope of the agreement being implemented, to which both parties have committed themselves. They are often part of a concept that develops during the implementation process, but the assumptions of which were not taken into account in the process of creating the project estimate. We consider them as so-called good ones, which, depending on the cost of execution and priorities, we introduce into our application with the consent of both parties. When making such proposals, it should be taken into account that they were also not taken into account at the stage of determining the deadline for submitting the application. Each additional change is a part of the previously unplanned costs and time that we have to spend additionally on the implementation of the project. Therefore, when deciding whether to make these changes that increase the complexity of our team, we always suggest a specific cost or time period associated with their introduction. Depending on the amount of time we would have for a given proposal, we decide together whether it is really important enough to be included in a given project. We then take into account the benefits that may affect the user’s acceptance of our application and the relevance of this patch to the intended purpose of our product. If we have come to the conclusion that the offer is marked with a high priority, then we evaluate time its implementation, and we find out how its implementation will affect the cost and delivery time of the project. Sometimes fixes are really insignificant, and their implementation can take just a few minutes – then we try to go to our customers ‘ hands. However, if there are really a lot of such minor fixes, then you need to take into account the amount of time spent on their implementation. Sometimes it may take 10 minutes to make one small suggestion, but if there are 10 of these small tasks… this time increases. Also, you should keep in mind that making each change involves an additional number of tests that we have to run.
Summary: so what is there to improve in our app?
This is the last stage related to the analysis of written comments. By breaking them down into suggestions and mistakes, we already know what we need to focus on and what priority a particular focus has for us. Then we also know whether its implementation is really necessary, what costs it entails, and how its introduction affects the project’s deadline. This allows us to know with what emphasis and what to pay attention to. The client, on the other hand, is aware of how his additional intervention in the concept of they affect the grounds established when signing the contract. I always believe that such an open conversation allows you to better understand the position of each of the parties. It is only through it that we can come to a common agreement and create stronger ties that are linked to mutual respect for our time and business. Thanks to it, we can satisfactorily realize our common goal-to create a fully valuable end product that can facilitate further cooperation in subsequent projects.
Maciej Fiałkowski,
EpicVr
