Alumni Pathways: Misc. Improvements (in PI 2)
Created Date | Feb 1, 2023 |
---|---|
Target PI | PI 2 |
Target Release | Q1 2023 |
Jira Epic | |
Document Status | Draft |
Epic Owner | @Lendl Meyer (Deactivated) |
Stakeholder | @Kirti Mishra (Deactivated) @Dave Wallace (Deactivated) |
Engineering Team(s) Involved | Analyst RED, Micro (new API endpoints) |
PART 1
Customer/User Job-to-be-Done or Problem
As a Product Manager responsible for Alumni Pathways, I want to make a variety of small enhancements to the software in PI 2 that don’t fit neatly in any of my epics.
Value to Customers & Users
A number of these enhancements were requested by customers on the previous platform (Alumni Outcomes) as ways to improve the software experience for them and add value. Specific benefits to customers and users are noted on each issue.
Value to Lightcast
We believe these enhancements will support new sales (e.g. through improving demos of the software) and increasing retention (e.g. by removing friction or adding value in the software). Specific benefits to Lightcast are noted on each issue.
Target User Role/Client/Client Category
Target external users: Institutional Research, Academic Leadership, Enrollment Marketing, and Advancement/Foundations teams across all current Edu segments.
Target internal users: Lightcast Sales, Marketing, and Success teams
Delivery Mechanism
The Alumni Pathways vertical on the Analyst Platform.
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?
Definition of done: Jira issues completed.
Success Criteria & Metrics are noted on each issue.
Aspects that are out of scope (of this phase)
Anything that isn’t an issue in this epic.
PART 2
Solution Description
Early UX (wireframes or mockups)
Designs are attached to each issue as relevant.
Non-Functional Attributes & Usage Projections
All issues need to meet standard Alumni Pathways criteria, including AO 2.0: Meet Contractual Requirements for National Student Clearinghouse Data.
Dependencies
The following PI #1 epics need to be completed before we can start on this epic:
Legal and Ethical Considerations
Just answer yes or no.
High-Level Rollout Strategies
These small enhancements will be released via our standard analyst platform agile process and communicated to Sales / Marketing / Success as applicable by our standard education product process (monthly update + release notes by sprint).
Risks
N/A
Open Questions
N/A
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 | Notes |
---|---|---|---|
Analyst Red | Flexible (intended to fill in the gaps between other epcis) | Lendl will continue to bring improvements to 3-in-a-box and grooming a similar rate to what we’ve been doing (most of which are captured in the linked Epic: https://economicmodeling.atlassian.net/browse/ARK-9123) | |
Micro | Flexible (intended to fill in the gaps between other epcis) |
| Some planned improvements will need new endpoints from Micro team. We’ll need a way to get this work on Micro’s radar. |