User Guides

< Back to Article List

Junari's expectations of customers throughout the project life cycle

Last updated: 25 September 2023 at 16:43:21 UTC by Junari Assistant

QA testing on time and with the right personnel: 


Once we have finished delivering a task for you we ask that ideally within a week you log into the system, check everything we have developed against the acceptance criteria and either sign off the task or provide us with detailed feedback regarding any issues, this will then allow us to then correct bugs. 


Failure to test on time can result in an increased risk of building further features on top of a base system that does not meet your requirements, causing a “chain reaction” of faults. This could then result in not having enough time to test the work later on in the project and going live with a system that does not completely meet your requirements.


We also assign the most appropriate person in your team to test the system, this is usually someone who would use the system on a day-to-day basis. 


Giving us the right requirements 


During requirements gathering sessions we ask that you provide us with the following to allow us to scope out the best requirements possible 


  1. Give us a summary of what you are using now and how you are using it

  2. Explain the full user story of what you need to achieve and who may need it for example as a sales manager I want to be able to manage all the commission due against each sale on one place 

  3. Explain any risk, assumptions, issues and dependencies you may know of, we would also ask you to communicate this throughout a project 

  4. Where necessary share your screen and and show us where you would like to map information from 



Communicating effectively on the portal


You can find a guide on how to use our portal here, some of our expectations when working with Junari are 


  1. You test all user stories based on what is defined in our acceptance criteria

  2. Any completed tasks are signed off or have a comment as to why they cannot be approved

  3. New support tickets are logged in the portal

  4. Communication on a task is done via the “send message feature”