Skillabi Postgres Transition Part 2
Created Date | Feb 1, 2023 |
---|---|
Target PI | PI 2 |
Target Release | |
Jira Epic | |
Document Status |
|
Epic Owner | @Caleb Bray |
Stakeholder | @Taylor Rogers @Tori Przybyl |
Engineering Team(s) Involved | SKILLabi SKILLFIT |
PART 1
Customer/User Job-to-be-Done or Problem
The Scope of the user problem should be narrowed to the scope you are planning to solve in this phase of work. There may be other aspects you are aware of and plan to solve in the future. For now, put those in the Out of Scope section.
When [user situation/context/mindset], I want to [user need/goal], so I can [expected result/outcome].
When the curricular skills api was first created, we built it using a no sql database despite the data being completely relational. This has made it very difficult to increment and add new features to the API. We want to move our data to a postgres database so that we can add more features and functionality for our customers and application.
Value to Customers & Users
In the JTBD framework, these are the “pains” and “gains” your solution will address. Other ways to think about it: What’s the rationale for doing this work? Why is it a high priority problem for your customers and how will our solution add value?
Based on conversations that I have had with product owners and other teams, there is a demand to leverage the API more than in the ways we are currently doing. The first step in this process is to migrate to a database that allows us to scale better.
Value to Lightcast
Sometimes we do things for our own benefit. List those reasons here.
Additional teams can leverage a more flexible version of the API in the future.
Target User Role/Client/Client Category
Who are we building this for?
This will primarily benefit the Skillabi team, but SkillFit has also expressed value coming from the changes being made to the API.
API Client’s have expressed interest in the API, but the current implementation is a little too rigid for their needs.
Delivery Mechanism
How will users receive the value?
Success Criteria & Metrics
How will you know you’ve completed the epic? How will you know if you’ve successfully addressed this problem? What usage goals do you have for these new features? How will you measure them?
Measuring success for this epic is pretty simple. The API should work exactly as it does now after the database transition. The Skillabi app should not have to make any changes when this new implementation is finished.
Aspects that are out of scope (of this phase)
What is explicitly not a part of this epic? List things that have been discussed but will not be included. Things you imagine in a phase 2, etc.
The new Database and data structure opens the door for many more uses of the curricular skills api. However, that will likely require new endpoints to fully leverage those possibilities. Those new API endpoints are not in the scope of this epic.
PART 2
Solution Description
Early UX (wireframes or mockups)
<FigmaLink>
Non-Functional Attributes & Usage Projections
Consider performance characteristics, privacy/security implications, localization requirements, mobile requirements, accessibility requirements
Dependencies
Is there any work that must precede this? Feature work? Ops work?
Legal and Ethical Considerations
Just answer yes or no.
High-Level Rollout Strategies
Initial rollout to [internal employees|sales demos|1-2 specific beta customers|all customers]
If specific beta customers, will it be for a specific survey launch date or report availability date
How will this guide the rollout of individual stories in the epic?
The rollout strategy should be discussed with CS, Marketing, and Sales.
How long we would tolerate having a “partial rollout” -- rolled out to some customers but not all
Risks
Focus on risks unique to this feature, not overall delivery/execution risks.
Open Questions
What are you still looking to resolve?
Complete with Engineering Teams
Effort Size Estimate |
---|
Estimated Costs
Direct Financial Costs
Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?
Team Effort
Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.
Team | Effort Estimate (T-shirt sizes) | Jira Link |
---|---|---|
Skillabi | XL | |
|
|
|