-
Notifications
You must be signed in to change notification settings - Fork 25
yShip (WIP name) - Product and Frontend Coordinator #257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
End of Q1 yShip ReportHey all, the first BR period for yShip is complete and here is the report: Listed Goals
|
Scope
This budget request proposes creating a new role: a Product Coordinator/Owner. This role will be responsible for ensuring clear goals, priorities, and effective communication across the various yTeams at Yearn, with an initial focus on the yVault products and their front-ends. The coordinator will collaborate with teams working on Yearn’s backend elements (smart contracts and strategies) and the frontend components (e.g., the Yearn.fi website and its supporting infrastructure).
Key responsibilities include:
Given the changes to MOM's budget requests as seen in their latest BR, any front-end project work outside of bug fixes and maintanence will require separate BRs. This moves the relationship between Yearn and MOM much closer to that of a client/agency relationship, which requires management on both sides to be successful.
I will also help coordinate a search for development and design talent to continue working on and improving the front-end, assessing internal and external options.
Plan
Infrastructure/Setup
To enable this role, certain infrastructure will need to be established or adapted. This may involve creating a new GitHub repository or other product management tools, or repurposing an existing system. The chosen infrastructure will facilitate day-to-day management of issues, feature requests, bugs, projects, and long-term strategy.
Unless alternative suggestions are made, the initial implementation will use a GitHub repository and project for these purposes. Setup costs are essentially 0.
Fixes/Low-Hanging Fruit
A priority for this role will be coordinating a comprehensive list of outstanding feature requests and bug reports for the Yearn.fi website. These tasks will be categorized based on their importance. While this effort will be distinct from similar work conducted by MOM, alignment and collaboration with MOM will be essential.
Given the scope changes to MOM's front-end work, defining and agreeing on fixes and other requests will need to be coordinated with MOM and categorized separately if they do not fall under MOM's scope.
Upon approval of this budget request, I will:
This process will provide an opportunity for broad input, including from community members, to identify and address the most pressing needs.
Strategy
A key objective will be developing a long-term comprehensive strategy for Yearn’s frontends and products. This will involve analyzing competitors and the market to identify Yearn’s strengths and areas for improvement. Given the decentralized nature of the DAO, this strategy will require thorough presentations and discussions to secure buy-in, enabling downstream decisions to align with a shared vision.
Mockups
To complement strategy work and and feature requests/fixes, I will work (independently or alongside MOM) to provide mockups of important changes and flows as needed to get buy in. I have a unique opportunity to use the DevDocs as a test bed for new ideas and UX flows and I hope to craft work around the docs to better support Yearn's needs.
Deadline
05/01/2025 (3 months), although the role is expected to continue until yBudget determines it is no longer needed.
People
@rossgalloway
Money
Coordination with MOM on Bug fixes and "low hanging fruit" improvements:
Strategy, Coordination, design around Yearn's front-end and product offerings:
Amount (Total)
$6,000 * 3 months = $18,000
Wallet address
0xA7b6f3d18db39F65C8056d0892Af76c07d15Fc5a
Reporting
Monthly
The text was updated successfully, but these errors were encountered: