Proposal: Support the development of community version of Opium Finance

What is there to show for the previous grant?
These estimates seem over the top for a website like this.

1 Like

Hello Opium Community!

Let me jump in here and introduce myself and my team.

Iā€™m the CEO and Founder of Codemotion. Iā€™m 37 years old, Kyiv born. I have technical education and background and worked as a software developer for eight years before founding Codemotion in 2011. Iā€™ll be happy if you check my LinkedIn https://www.linkedin.com/in/ygolovach/

On the other hand, Codemotion is a team of 200 developers who have successfully delivered and launched live more than 150 projects for our customers, always sticking to agreements and taking full responsibility for the deliverables and high quality. Most of our clients have been working with us for years with total trust. Please take a look at our Upwork profile with $10m+ earned with excellent reputation Codemotion Ninjas šŸ„‡ Upwork Awarded | Upwork and please search for our Clutch page (canā€™t put another link here due to forum rules for new users)

Iā€™m astonished by the situation here as our main principle is complete transparency at every stage of any cooperation. And we applied this principle while building a community version of Opium Finance from the first step. Now I feel that our team is fully unsynchronized with the respected community members.

This weekend, Iā€™m thoroughly checking through the issue and investigating all the reports and communication.

Let me get back to you early this week with my investigation results and address every community remark.

Iā€™m glad our company has the opportunity to collaborate with the Opium community, and my goal here is to preserve this collaboration for the long term making Codemotion a trusted vendor when you need any extra help.

Have a great weekend!

Yaro

Hi Opium Community.

Getting back to you with my analysis results. It took a while for me to investigate everything.

Let me go through the topics one by one.

Dropping tokens on the market

I totally understand you as holders of Opium tokens and understand how important to keep high liquidity of it.

Still, Codemotion is a classic outsourcing software development company with hired in-house developers as employees. We have an obligation to pay wages to our employees in a timely manner in FIAT.

Therefore, weā€™ve been transparent with you all the time, that we need to receive payments in stable coins (at least). All our invoices from the beginning of our cooperation (from Nov 21) have been represented in the United States dollars. When we posted proposals for pre-payments and payments we were always indicating the amount of Opium that is equal to the amount of the United States dollars on the posting date.

Unfortunately, weā€™ve never considered token exchange as an issue for the collaboration.

Estimation concerns

The very detailed estimate with breakdown, budget, and timeline was posted on the 2nd of March. Everyone had access to it and we were fully transparent from the beginning on all numbers. We received 100% approval via signal voting.

Regarding the concern about possible changes in the estimation. Itā€™s our mistake we didnā€™t use IPFS to store the PDF version. Anyway, weā€™ve made the estimation document with full edit access for everybody so you can check the versions history and see no changes were made after March 2 (you should be logged with any google account to see versions history, itā€™s not visible for anonymous access, unfortunately). You can find the link to the file in this post Proposal: Support the development of community version of Opium Finance - #23 by Codemotion

Budget reports and project duration

Regarding project duration, we want to pay your attention that we have almost met our deadlines. According to the 29 of May, we had already spent 11 weeks (with included public holidays) instead of 9. We admit that the timeline was gone beyond 2 weeks, taking into account that there was some unexpected time for us with finding solutions and with consultations on the already operating Opium Finance that were tightly connected with ā€œOh My Opiumā€.

When you ask anybody about the alternative quote make sure they study the whole specification with all details to make sure they are aware of every small piece of functionality from the specs posted on the 2 March in this topic. Personally, I also like to give very optimistic numbers before digging into details. But specification stands to put everybody on the same page - what is expected and what should be delivered.

Project management hours

A good project manager takes control of a project from beginning to end, ensuring that the initiatives and goals are strategically aligned and everyone is on the same page. He is the main person who ensures and guarantees the budget and timeline fit for the project.

Eventually, we delivered the project with high quality, and we fitted into the budget and deadline, which was done successfully according to all criteria.

We admit that for some tasks there was a reallocation of resources and overspending. This was compensated by speeding up on other tasks.

Following the estimation link mentioned above, you can find described Project Management Routine (please, skip the lines with Daily client update / Client daily grooming / Sprint grooming with the client as itā€™s not applicable to our cooperation)

Team composition and qualification

Regarding the team composition which is shown in our proposal (attached to our first post Proposal: Support the development of community version of Opium Finance Nov 21 ) is the possible team for the project.

We started our development phase on the 28th of February. Since 3 months after posting the proposal, the development team was changed as there could be lots of reasons such as an allocation of resources on other projects. We can keep the same team in case the project starts immediately. Otherwise, we allocate similar resources.

Budget Optimization

Weā€™ve made steps towards budget optimization during the development. This was possible thanks to the more experienced front-end developer assigned to the project.

You may notice that the time dedicated to technical management (48-64h) was almost not spent. This is due to the fact that we were able to optimize the team and not involve a much more expensive specialist there because our front-end developer has such competence. Accordingly, our front-end developer, in addition to his planned tasks, was also involved in refactoring, optimization, acceptance of work from himself and the HTML developer, and conducted a code review. Due to this, his hours of work have increased, but his rate is lower than the rate of a Tech lead.

DevOps hours (10-12h) were also taken over by our front-end developer, so we skipped the additional time of the team on onboarding and further communication with a new team member. Therefore, these hours also moved to the spent time of the main front-end developer.

Going Beyond Task Evaluation

We understand all your concerns about tracked hours, and exactly that you are confused by front-end development hours, which basically really looks like something that went beyond the original estimate. But we are open to you and ready to go through some technical issues more clearly in order to analyze them in more detail.

  1. Wrap/Unwrap
    During the development, it turned out that this feature is not stable, we additionally added new texts and interdependencies with networks, which also tracked into this task (additional 23h). Anything small that appeared on the wOpium convert page due to edits or style conflicts was also included in this task.

  2. My stake filtering
    In the process of work, the developer found two bugs there and, accordingly, tracked them in the same task (33,5h). Also, the time for searching for staked pools is tracked here, they have not been displayed and the developer was searching for a reason, and the time for developer tests when working with pools has also gone here. The thing is that there was no separate call in the system to simply make a request and get all the pools that should appear in the My Stake section and only after testing, searching, and consultation it turn out that this data should be obtained by referring to the balance.

  3. IPFS investigation
    This includes time both for investigation and for some test work related to the deployment. And here we did not take into account many moments that were not known to us at the evaluation stage, so this task was stretched out because of the risk of working with a technology that was new to this developer. At first, the developer tried to build through the desktop app, but it didnā€™t work, and only then did he manage to do it through fleek.co

Yes, the time spent here really looks inefficient and we admit it. We agree that it is fairer to take part of hours (30h) as our risk because it is our fault that we did not conduct this investigation more thoroughly in the BA phase and that we spent additional time during development.

  1. Stepper
    This task is also not as easy as it looks at first. There were 2 options to implement such component - slider or stepper. At different points in the implementation of the task, the team had new edits and had to rewrite some elements, as the developers changed the component several times. And of course, they made it up and changed the functionality several times. Because it was difficult to decide in which of the components all design elements can behave as they should. Ir was regarding filling in the points of the current phase, showing the correct date, showing the progress of the line, and the possibility of a slider in the mobile version of each of the phases.

Here, too, we agree that we must take out this time that the HTML developer additionally spent (20h) due to incorrect team decisions made at the beginning.

In total, the overall picture looks like some tasks really took longer than expected, and some really could have been done more efficiently like IPFS and Stepper (part of Details of pools). But this did not affect the budget negatively due to the reorganization of work on other tasks.

We deduct 50 hours of inefficient work (30 hours of front-end and 20 hours of HTML developers) which is equal to $2,150.00.

As a result, the project total amount spent of $34,607.00 is close to the original Optimistic estimate of $33,397 instead of $42,687 in a Realistic scenario.

Conclusion

I canā€™t find any critical mistake from our side.

As I mentioned previously we are a classic outsourcing company with 11 years of history with a proficient team and what is more important well-established delivery processes. We have 200+ in-house developers and delivered more than 150 projects launched live.

We guarantee and take full responsibility for the quality, budget, and timeline fit. And this approach has helped us to grow from a team of a couple to a current team of 200 people without any external funding.

Iā€™d be happy to provide you with references to our existing long-term customers who work with us for years so you can hear direct feedback.

Iā€™m a technical person myself and was coding for more than 8 years. And I understand that obviously, some skilled developers can do the same amount of work faster and cheaper. But the questions are: can he be trusted? can he guarantee the quality? fit in the budget? keep a timeline and properly plan his load? can he overcome accidental sick? can he just get money and do nothing? And in the case of a single developer/freelancer, you take all these risks on yourself.

You make the same choice when e.g. you make an apartment repair work - you either take all risks working with a single construction worker or you hire a trusted company with guarantees. And then you understand the value of why you are paying more.

In the case of working with a trusted company, you avoid all these risks. And when a company makes a mistake it fixes it on its own. We were very clear initially that we are not a company that is cheap or cost-cutting but we are reliable and give a guarantee.

Thatā€™s why for me as a business founder and person who keeps his word itā€™s strange we are facing this issue right now when previously agreed budget and estimation are reconsidered after agreed works are done.

We are focused on long-term and transparent cooperation with Opium Community thatā€™s why if any of the communityā€™s members want to have a call with us and discuss any questions regarding our results, we are open to it.

Additionally, we want to highlight that applying for the development of a community version of Opium Finance means that our work is going to be very transparent and evaluated by senior tech experts as you are. Such kind of cooperation is possible only when an agency has a strong development team and solidly established processes. Also, we work transparently and donā€™t use the ā€œblack boxā€ or ā€œman-in-the-middleā€ model as most agencies do. We publish all reports and provide access to all collaboration tools. Thatā€™s why cooperation with the community is possible for us.

As a next step, our team will send the updated report for works done.

Best,
Yaro

Hi, community!

We supplement the text of our CEO about spent hours, hours for ineffective development, total budget and comparison with initial estimate in the form of a table for greater clarity for you.

Regards,
Codemotion Team

Hi, community!

Since you did not have any comments on our last posts where we answered your questions and provided detailed information on each of your questions, we would like to start the payment process.

Regards,
Codemotion Team

Well, even though you already agreed on inefficiencies from your side, Iā€™m still standing in my opinion that this project doesnā€™t cost the estimated amount.

The original author (@mrnobody) of the project already agrees to implement the same functionality for a 5k$ (vested) grant with the support of the upcoming Opium 2.0 update, letā€™s rather vote for that instead.

Iā€™m still completely against of any additional payment, especially considering that 23k$ was already paid (IMO it was redundant already).

Check other DeFi projects like 1inch for example, they are paying 40k$ for the projects that require R&D and bring innovations, which are being worked on by the most senior people in the ecosystem.

If you still would like to proceed with the payment, feel free to create voting on the Snapshot, post it here and see the token holders opinion on the matter.

1 Like

The situation is that we are not estimating the tasks now and are not asking for money for possible development. We have already done the work and have already spent the time of our developers on this project and have already given people salaries for this.

We have been honest and open from the very very beginning. We provided an estimate, gave time to review it, received approval, and began to work.

Letā€™s imagine that our project is a project of building a house. Initially, we provided you with all the designs, measurements, and documentation. Then we set up the team who did everything and in the end, we gave you the keys to the house. And in response, you answer us that another team would have done everything much cheaper and therefore you are not going to pay us for the rest of the work. But the work has already been done and all prices have been clarified from the very beginning.

It is obvious that there will always be someone who will do it cheaper. But if the community had initially said that our conditions and estimates did not suit the community, we would not have taken up the project.

For our part, we have done everything for a transparent partnership because we have kept what we promised. So we expect the same fair attitude towards ourselves.