I haven't seen a serviceprovider go to the lengths that You_Source goes to
We are very pleased with this progress; and we believe that this is primarily because all aspects of the development work have been carried out in a working ethos of excellent technical skills, constructive ideas, good communications, and goodwill.
With You_Source, we have about 50% more output than with our previous Australian partner.
I have been responsible for the development of software systems several times in my life, but I would finally say that, for goodwill, cheerfulness, and a great working relationship, your company stands out as exceptional.
I would also like to add, I am consistently impressed with the service we are receiving from you and the team at you_source. Thank you.
On the back of a strong release with good features, we're looking pretty good! Now we need to get heads down and do it all again. Keep up the great work!
Honesty + thinking from end user's perspective + design quality + dev team's speed & responsiveness. Some good problem solving + inputs to roadmap + planning for post - MVP ongoing ops.
Considering the current quarantine/lock-down situation, the team maintained the same work ethic, dedication and commitment to project deadlines. Well done to the team.
1 word, GLORIOUS!
Felt like the team was firing on all cylinders; very productive.
Thank you so much for your effort to support road safety.
Feeling like I just launched a space shuttle
My name is Owuor Otet. Founder of Road safety and safe driving practices. Thank you so much for your continued support and improvement on the application. My team is very much glad as we now have a platform not only to talk but to see our performance. As the founder of Road Safety and Safe Driving Practices, am i at a position to know who picks calls, who speeds under my organisation?
Thank you so much for your effort to support road safety.
We break down scope in bite size chunks, and deliver these new features every cycle. A typical development cycle (or sprint) is one to two weeks. Since the latest version of the software will be available as soon as developers check-in, you can provide feedback as soon as minutes after the last update.
Our teams are equipped with all roles required to deliver successful software. A typical team consists of Experience Design Engineers (UI/UX), Software Engineers, Quality Assurance Engineers, Project Management, Solution Architects and CTO hours where necessary.
Software requirements always leave a lot of room for interpretation. At You_Source we cover most of these by our DoD (Definition of done). This not only improves the process but also speeds up the development cycles. The DoD covers topics from user experience to coding standards and from the security to process.
We like to demo what we have as often as we can, as this helps us iterate and improve on the solution. After every development cycle we have a demo. We will ask you for feedback and apply that as soon as the next development cycle.
All our projects are unit tested to a coverage of at least 80%. These tests are automatically run when a developer submits new code. When any test fails, the code will be rejected and requires the developer to fix any mistakes or merging issues so that the source code will only contain running and tested code.
Application Lifecycle Management is crucial to the overall success of a software development project. We manage this lifecycle in the most applicable tools for your project, using tools like Azure DevOps, Slack, Jira and others. We are fully transparent using these tools and you have access to your source code, requirements and infrastructure from day 1.
We invest early on in a 3 stage environment that gives you full visibility in the progress of your project or team. The development environment contains the latest features, the staging environment the latest features ready for testing, and these get pushed to production when approved.
Software development contains a lot of problems that are usually solved with similar patterns, that work on code, architectural or infrastructure level. We have established a set of patterns that solves most software engineering problems and we train our developers to understand, build and maintain these patterns. This improves overall maintainability and helps developers build structured code in a familiar fashion, allowing them to be more productive and deliver software that they can be proud of.
Backend code will always be unit-tested to a minimum of 80% coverage. Unit tests can be executed fast and often, and gives the developer the confidence that his changes or contributions did not break any dependencies. We also measure the maintainability index, which ensures that the code is of readable complexity.
Security is non-negotiable, and is hard to define using just requirements. We have a standard set of security requirements that we implement in all projects which covers the requirements set by law. We are also skilled at going that extra mile to deliver applications where we as developers of the application would not even have access to the data involved.
Static code analysis is leveraged both on the developer machine as well as during the check-in process. When a developer submits his code to the code repository, the system will run an automated code review, and when warnings or errors are found, the code will be rejected. This keeps your source code consistent with standards and helps keeping the code clean, even when the deadline comes close.
In development more often than not the user is completely overlooked. Systems are designed by committee and not for a good User Experience. We help you through the process of converting your ideas in the usable User Experiences. We do this with the help of rapid Prototyping and by making interaction designs. We test those and make implementation plans based of them. While implementing we expose the results as early as possible to user through user testing. Iterating often gives great results with minimal efforts.
When we design systems or part thereof, we keep a strong focus on the architecture and scalability. In principle we design all components fore the cloud that are easily and highly scalable. Where we make concessions, we do this while keeping you informed.
When we develop software, we get quick/interim results to you by developing the frontend fist. We do this because when the frontend starts to become real better feedback and real-world testing and validation can be done. This early feedback will save a lot of time in development because changes at that stage only have effect on the frontend and not the backend since that will simple not be working yet.
Most of our architectural designs are based on a microservice concept ore a slight variation thereof. Making a system out of small components working together create a lot of advantages like, easier scalability, mixing and matching of technologies, improves testability, easier fault isolation and much better reusability.
Seeing is believing, we like to show what we got as often as we can. We iterate quick and often. After every development cycle we have a demo, sometimes only internal but most often you will be included. We will ask you for specific feedback and apply that in the next iterations.
Let’s make sure we are all on the same page to start this journey. We will ask some healthy questions, like should we be doing this project to begin with? Is prototyping the correct tool for your problem/situation? Do we have all the information that is needed for us to make a prototype?
Get acquainted with everyone involved and their roles. Confirm the understanding of the project based on the initial documentation and clarify all the assumptions & targets. Being on the same page is key before we start doing the work.
We’ve designed a cadence where the design team will work for 2 days and have a meeting on the 3rd day. The meeting will be about progress presentations, problem solving, and planning our next steps. We’re co-creating this product and
By the final meeting, we’ve already come up with a prototype that tells us the best possible experience of the app we’re looking to build. We create our final notes to do, then we wrap up and turnover the deliverables.
Our architects and developers will estimate the efforts for the entire project based on the prototype and the other information we have collected during the process. We will propose a fixed price for a high quality solution that you will be proud to be the owner of.
We can provide you with a truly fixed price for software development services. This means that we take full risk for the output and you will not have to worry about rising development costs, as our guarantee applies.
We believe that we are the right partner for any software development project. And we are so convinced of our ability to help you that we can guarantee you our promise. “If we do not deliver what we promise, we do the rest of the work for free. No questions asked!”
You_Source was born out of a passion for building quality software. We take pride in our practices and deliver easy to use and well architected software that is built to scale. Metrics don’t lie.
hr@you-source.com
5F, PHINMA Plaza, 39 Plaza Drive,
Rockwell Center, Makati City
359 Rivonia Boulevard
Edenburg, Sandton, 2191
Johannesburg, South Africa
Unit 3203-4 No. 69 Jervois St., Sheng Wan
Hong Kong China
If you have a passion for high quality standards,
and collaborative software development, get in
touch with us.
