Professional Documents
Culture Documents
FREELANCER.COM
YOLOS enhancements
22 May 2020
Employer: [ jon2347]
Freelancer(s): [username(s)]
Technical Project Manager: [ saitechcopilot]
Document Version: v1.0
Foreword
The purpose of this document is to outline the scope of the work required, detail the price and
milestones associated with each, and document the features required.
For the employer, this document will allow you to agree on a set of features at a fixed price. It
will also suggest potential further work - note that this will require additional payment.
For the freelancer, this document will serve as both a reference point, and as a way to prevent
scope creep.
Description
Yolos project completion has resulted in the identification of additional initiatives needed to
optimize the user experience and improve upon certain functionality.
Feature Description
An experienced app developer to update the core functions built on react frontend framework
● Outlined above.
Checklist
❏ Format of the CSV file agreed upon for bulk upload by both employer and freelancer
❏ Onboarding screen designs - Sumit
❏ Onboarding screen copy- Jon
Total:$ 2000
In return for the completion of this work, the employer has agreed to pay a sum of 2000. All
payments must be made through Freelancer.com milestones.
Milestones will only be released if the code adheres to the standards above, and the features
contained within this document have been delivered.
All milestones will be released upon completion of the website.
Milestones will be released by the employer within 72 hours of the above conditions being met.
The freelancer taskmanageryd agrees to provide an additional 3 months of support from the
date of completion of this project.
Coding standards
The employer is technology agnostic - they do not mind which programming languages are
used. That said, the technologies used should be modern, well supported, and the code should
be clean and bug free.
The code should be developed using source control, preferably the “Git” source control
software. The code should be maintainable, and properly structured and commented such that
another developer can build further upon the work.
All user passwords must be hashed using bcrypt and salted, and the code must be free of
security vulnerabilities, including but not limited to SQL injection, XSS and CSRF.
The website must be HTTPS and come with a SSL certificate.
The page has to be mobile responsive and functionally & visually complete across all common
web browsers (Chrome, Firefox, Safari, Edge) and devices (desktop, mobile, tablet).
User roles
● Buyer
● Vendor
● Admin
User stories
Share Trello board
https://trello.com/b/imu20aIe/yolos-issue-list
Technical specifications
Should be available on the Android play store and Apple play store and be approved and built to
standards.
All functionalities should introduce minimal lag and be in real time as possible.
Should leverage the native GPS functionality of devices being used (Android and iOS) if
applicable.
Non-functional requirements
Special requirement for usability/accessibility, security, loading times, legal (GDPR)
SEO
Hosting
Other notes and agreements
The freelancer chosen agrees to provide regular updates to the employer and project manager
at least once every two days.
All communication must be made through the Freelancer.com chat interface, or a phone call
with the project manager.
The freelancer must agree to support the employer if the website should contain bugs detected
after the initial inspection period. This support can be billed separately, should it be required.
No milestones associated with development will be released until the source code is completely
handed over to the employer, and the website or app has been extensively tested in its live state.
Any bugs found must be fixed, and are included in the agreed price.
All hosting and website security credentials (passwords etc) must be handed to the employer,
and it is highly recommended the employer changes these prior to releasing the milestone. All
of the above code standards must be adhered to for milestones to be released.
Any deviation from the requirements may lead to one or more milestones being disputed.
The employer will own the IP associated with the code upon complete payment of the
milestones, or any agreed outcome of a dispute.