User story 0 : Reskin and Upload to Appstores

Reskin and reinstall the application( For documentation see :

https://apps.iqonic.design/docs/product/handyman-service/) and upload it to the Cpanel,
Firebase, Android and iOS app stores using GitHub CI/CD integration so that it can
quickly and easily release new versions of the application with a fresh look and feel.

Acceptance Criteria

● TheDeveloper is to update the branding assets, colors, naming to the application

repository.
● The CI/CD pipeline automatically reskins the application using the uploaded
branding assets.
● The CI/CD pipeline automatically builds and tests the reskinned application.
● The CI/CD pipeline automatically deploys the reskinned application to the staging
environment.
● The system administrator can review the reskinned application in the staging
environment.
● The developers can promote the reskinned application to production.
● The reskinned application is released to the Android and iOS app stores.

Business Rules

● The system administrator must have the appropriate permissions to upload

branding assets to the application repository.
● The branding assets must be in the correct format.
● The CI/CD pipeline must be configured to use the correct branding assets.
● The system administrator must approve the reskinned application before it is
promoted to production.
User story 1: Service Addon

As a provider, I want to be able to add service addons to my services so that I can offer
additional services to my customers for an additional fee.

Acceptance criteria

● Provider can add service addons to their services.

● Service addons can have a name, description, and price.
● Provider can specify whether a service addon is required or optional.
● Customers can see the list of service addons for a service when they are booking
the service.
● Customers can select the service addons they want when they are booking the
service.
● The price of the service is updated to include the price of any selected service
addons.

Business rules

● Only Provider or Admin can add service addons to their services.

● Service addons must have a name, description, and price.
● The price of a service addon must be a positive number.
● Required service addons must be selected by customers when they are booking
the service.

Examples

● Service: Painting - $59

● Service addons:
○ Additional coats of paint - $3
○ Wall repair - $ 4
○ Furniture removal - $5
○
● Service: Plumbing
● Service addons:
○ Leak repair - $3
○ Faucet replacement - $8
○ Pipe installation - $5
User story 2: “Handyman” to “Associates”

As a system administrator, I want to be able to change all references of "handymen" to

"associates" in the whole application so that the application uses consistent terminology.

Acceptance criteria

● All instances of the word "handyman" are changed to the word "associate" in the
application code, database, and user interface.
● The change is made in a way that does not break the application.
● The change is documented in the application's change log.

Business rules

● The change must be made in a timely manner.

● The change must be communicated to all users of the application.
● The change must be tested to ensure that it does not break the application.

Examples

● The "Handymen" tab in the navigation bar is changed to the "Associates" tab.
● The "Handyman profile" page is changed to the "Associate profile" page.
● The "Handyman availability" calendar is changed to the "Associate availability"
calendar.
User story 3: Google Calendar Sync

As a customer or provider, I want to be able to sync my bookings with Google Calendar

so that I can have a centralized view of my schedule.

Acceptance criteria

● Customers and provider can enable booking syncing with Google Calendar.
● When a booking is created or updated, it is automatically synced with Google
Calendar.
● When a booking is canceled, it is automatically removed from Google Calendar.
● The booking title in Google Calendar includes the customer name, service name,
and date and time of the booking.
● The booking description in Google Calendar includes the booking details, such
as the address and any additional notes.
● Customers and provider can view their synced bookings in Google Calendar.

Business rules

● Only customers and providers who have enabled booking syncing can see their
synced bookings in Google Calendar.
● Synced bookings cannot be edited or deleted in Google Calendar.
● If a booking is edited or deleted in the application, the corresponding booking in
Google Calendar will be automatically updated or removed.

Examples

● A customer books a make-up service for Monday, September 12, 2023, at 9:00
AM. The booking is automatically synced with the customer's Google Calendar.
●
Userstory 4: Referall

As a customer or provider, I want to be able to refer my friends and colleagues to the

application so that I can earn rewards and they can get a discount on their first booking.

Acceptance criteria

● Customers and providers can generate unique referral links.

● When someone uses a referral link to book a service, the referrer earns a
reward.
● The person who used the referral link gets a discount on their first booking.
● The amount of the reward and discount can be configured by the system
administrator.
● Customers and providers can track their referrals and rewards in the application.

Business rules

● Only customers and providers who have been referred to the service can
generate referral links.
● Referral links can only be used for new bookings.
● Rewards are only earned for bookings that are completed.
● Discounts are only applied to the first booking made by a new customer.

Examples

● A customer refers their friend to the application. The friend uses the customer's
referral link to book a painting service. The customer earns a reward for the
referral. The friend gets a discount on their first booking.
● A provider refers their colleague to the application . The colleague uses the
provider's referral link to book a plumbing service. The provider earns a reward
for the referral. The colleague gets a discount on their first booking.
User story 5: 100% Advance Payment (Update)

As a system administrator, I want to be able to allow and force 100% advance payment
for the whole system so that I can reduce the risk of non-payment.

Acceptance criteria

●
● When a customer books a service that requires 100% advance payment, they
are required to pay the full amount before the booking can be confirmed.
● If a customer does not pay the full amount for a booking that requires 100%
advance payment, the booking is canceled.
● The system administrator can view a report of all bookings that require 100%
advance payment.

Business rules

● Only the system administrator can configure the system to require 100%
advance payment.
● Customers cannot book services that require 100% advance payment without
paying the full amount.
● Bookings that require 100% advance payment cannot be confirmed without full
payment.
●
●
User Story 6: Service Zones

As a system administrator, I want to be able to define service zones (countries and

cities allowed) so that I can restrict the availability of providers/services to certain
geographic areas.

Acceptance Criteria

● The system administrator can define a list of countries and cities that are allowed
for each provider/service.
● When a customer books a service, the system checks if the customer's location
is within the allowed service zones.
● If the customer's location is not within the allowed service zones, the customer is
not allowed to book the service.
● The system administrator can view a report of all services and their allowed
service zones.

Business Rules

● Only the system administrator can define service zones.

● Service zones must be defined at the country and city level.
● A service can be available in multiple countries and cities.
● A service cannot be available in a country or city that is not defined as an allowed
service zone.
User story 7: Distance Calculation

Prerequisite : Force the customer to have location on or choose which address (saved
addresses they booking the service from)

Prerequisite: Force the provider to select which saved address they will be operating
from.

As a customer, I want to be able to see the distance between the provider/service and
my location so that I can make an informed decision about whether or not to book the
service.

Acceptance criteria

● The system calculates the distance between the provider/service and the
customer's location.
● The distance is displayed to the customer when they are viewing the provider or
service details.
● The distance is calculated using the customer's current location or the address
they have entered.
● The distance is displayed in the customer's preferred unit of measurement.

Business rules

● The distance is calculated using the Google Maps Distance Matrix API.
● The distance is calculated as the driving distance between the two points.
● The distance is rounded to the nearest whole number.

Examples

● A customer is viewing a listing for a hair service. The distance between the
customer's location and the hair salon location is displayed as 3 km.
USerstory 8: Zoho SalesIQ SDK Api Integrate

I want to be able to integrate the Zoho SalesIQ API SDK (chat for customer support) so that
customers can get real-time support from our team.

Acceptance criteria

● The Zoho SalesIQ API SDK is integrated into the application.

● Customers can initiate chat conversations with support agents.
● Support agents can view and respond to chat conversations.
● Chat conversations are logged and can be viewed by support agents.
● Chat conversations can be assigned to specific support agents.
● Support agents can be notified of new chat conversations.

Business rules

● Only support agents can respond to chat conversations.

●
●

Examples

● A customer visits the application and opens the profile page and clicks on the "Help and
Support” button and a chat is opened.
User Story 9: Chat Attachments (Update)

As a customer or provider, I want to be able to send and receive attachments, images,

and videos in chat conversations so that I can provide more context and information for
my inquiries and requests.

Acceptance Criteria

● Customers and providers can send and receive attachments, images, and videos
in chat conversations.
● The maximum file size for attachments is 10MB.
● Supported file formats for attachments include:
○ Images: PNG, JPEG, GIF, BMP
○ Videos: MP4, AVI, MOV
○ Documents: PDF, DOCX, XLSX
● Attachments, images, and videos are displayed in chat conversations.
● Customers and providers can preview attachments before sending them.
● Customers and providers can download attachments.

Business Rules

● Customers and providers are responsible for the content of the attachments they
send.
● The system administrator can configure the maximum file size for attachments.
● The system administrator can configure the list of supported file formats for
attachments.
User Story 10 : Job Postings (Feature Update)

As a customer, I want to restrict my job postings to only be seen by providers who are within a
certain distance of my location so that I can be sure that I am hiring someone who is local and
can easily come to my home or business.

Acceptance Criteria

● Customers can specify the maximum distance from their location that they are willing to
consider providers from.(Service Radius in Admin Panel)
● Only providers who are within the specified distance are able to see the job posting.
● The distance between the customer's location and the provider's location is calculated
using the Google Maps Distance Matrix API.
● The distance is displayed to the provider when they are viewing the job posting.

Business Rules

● The maximum distance that a customer can specify is according to service radius
specified by admin
● The distance is calculated as the driving distance between the two points.
● The distance is rounded to the nearest whole number.
Userstory 11 : User Interface Design Customisation for Home , Booking and Profile Screen on
Customer App

Home Screen (New Profile Screen (New Booking Screen (New

Look) Look) Look)
User story 12: Internationalization

As a system administrator, I want to be able to internationalize the application and

admin panel to cater to different locales, currencies, and other internationalization
features, with different admin panel instances for different countries, so that the
application can be used by users in multiple languages, with different currencies,
and with content that is localized for their specific locale.

Acceptance criteria

● The application and admin panel are translated into multiple

languages(Already available).
● The application and admin panel are able to display dates, times, and
currencies in the correct format for the user's locale.
● The application supports multiple payment gateways, and the available
payment gateways are displayed to the user based on their location.
● The application displays content that is localized for the user's locale.
● The admin panel has separate instances for different countries.
● Admin panel users can only access the instance for their country.
● Admin panel users can manage content for their country in their own
language.

Business rules

● The system administrator can configure the list of supported languages.

● The system administrator can configure the default language for the
application per location.
 ● The system administrator can configure the list of supported payment
gateways.
● The system administrator can configure the default payment gateway for each
country.
● The system administrator can assign admin panel users to specific countries.

Examples

● The application is translated into English, French, Spanish, and German.

● A user in the United States sees the application in English and is able to pay
with PayPal or Stripe.
● A user in France sees the application in French and is able to pay with Paylib
or Carte Bancaire.
● A user in the United States sees content that is localized for the United
States, such as references to American holidays and events.
● A user in France sees content that is localized for France, such as references
to French holidays and events.
● A system administrator creates a separate admin panel instance for the
United States and a separate admin panel instance for France.
● A system administrator assigns a user to the United States admin panel
instance.
● The user can only access the United States admin panel instance.
● The user can manage content for the United States in English.

Additional considerations

● Internationalization will allow the application to be used by a wider range of

users.
● Internationalization will make the application more user-friendly for users in
different locales.
● Internationalization will help to increase the adoption of the application.
 ● Content localization will ensure that users are seeing content that is relevant
to them.
● Separate admin panel instances will allow for localized content management
and administration.

User Story 13 : Payment Gateway Integration (Paystack)

As a system administrator, I want to be able to add the Paystack payment gateway to

the application so that customers can pay for services using their preferred payment
method.

Acceptance Criteria

● The Paystack payment gateway is integrated into the application.

● Customers can select Paystack as their payment method when booking a
service.
● Customers are redirected to the Paystack website to complete their payment.
● Once the payment is complete, the customer is redirected back to the
application.
● The booking is confirmed and the customer receives a confirmation email.

Business Rules

● The system administrator must have a Paystack account.

● The system administrator must configure the Paystack API keys in the
application.
● The system administrator must test the Paystack integration before making it live.
●