Our Hedera - Use Cases
Onboarding Process
As a Digital Platform, the success of our product depends on our success to identify the needs and pains of our community and transform those into services to be delivered by our producers.
Onboard Customers. Bringing work to our platform
Onboard Producers. Providers of products and services for customers
Onboard Partners. Stakeholders interested to grow with us
Onboard Ambassadors. Leaders of communities with similar mindsets and values
Hedera: We will release HBars for our Ambassadors and supporters.
Symbiosis Implementation
Symbiosis is a change of paradigm of traditional work. We need to work shoulder with our customers to understand the model, adapting harmonically their actual processes to a new process using the advantages of our model, sharing experiences, tools, and knowledge with users to accelerate the adoption, supporting them to create their own resources and expertise.
Hedera: HBars for our consultants.
Task Disaggregation
Customers understand and domain their own business… they don’t need to understand tech concepts to define their business requirements. We will create a business requirements database to identify patterns and abstractions of business requirements, supporting our customers to identify how “looks like” the requirement they expect and customizing with iterations until getting what they need. We will gain estimation accuracy, reducing the deviation risk for our customers and producers.
The business requirements will be disaggregated into simple Work Units, easy to estimate, and track. The work units will be assigned to one professional with the skills required to release the work.
Hedera: Tokens to track Requirements and Work Units.
Backlog Maintenance
The Work Units will be stored n a Global Backlog, available to our global community of professionals. The platform will assign the work according to the skills required, and the fee selected by the customer. The fee is determined by the Service Level Agreement defined by the customer, a more comprehensive service would require more services or best-qualified providers.
The customer will prioritize the Work Units to be released in the next sprint. Every customer will manage their own sprint and will see just the Work Units of their project. The customer would accelerate or deaccelerate the speed of Work Unit releases according to their budget and operative capacity.
Hedera: Smart Contracts to track Service Level Agreements per Work Unit.
Work Unit Execution
The platform will assign in a transparent and equitable way the work unit according to the skills required to release the task. Smart Contract would be in place to clarify Service Level Agreements and the release of the work. Information regarding the type of task, quality, time, and technologies will be collected as part of the Work Unit tracking.
Hedera: Smart Contract to track Service Level Agreements.
Work Acceptance
Once the Work Unit is released, a peer review will be involved to accept the work completed and qualify the technical release of the producer. The peer-review would release the user of the technical validation, and the technician that approves will be tracked as part of the smart contract and evaluated. A peer review task is by itself a Work Unit for the technician that executes the peer review.
Hedera: Smart Contract to track Service Level Agreements
Release Payment
In the same way that the requirements were disaggregated, the Work Units released and approved will be integrated as part of the release of a Business Requirement. Complex Business requirements will involve expert support for a Technical Architect in task disaggregation and also in Work Unit Integration. Task Disaggregation and Integration will be registered and assigned as any other Work Unit, including the peer review of the work completed.
Once the business requirement is integrated and deployed, the customer review and accept the product released to be paid, or rejected to be completed. The customer will pay just for the Work Units and features accepted. To reduce the natural risk for producers, we will keep as simple as possible the tasks through task disaggregation.
The customers pay for the Work Units accepted and a new sprint starts.
Hedera: HBars to pay producers.