SSO for Talent Transform
Created Date | Aug 2, 2023 |
---|---|
Target PI | PI6 |
Target Release | |
Jira Epic | |
Document Status | Hold Draft Review Committed At RISK |
Epic Owner | @Marla Santos |
Stakeholder | |
Engineering Team(s) Involved | Talent Transform |
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].
As a user, I want to be able to login to Talent Transform using my Identity Provider (IdP) so that I can minimize the number of separate credentials needed to login to various systems
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?
This would allow users whose companies utilize SSO (e.g. Microsoft Azure AD, Okta, Google) to not need to remember and store a separate set of credentials specifically for Talent Transform (and possibly for each different environment available). They would be able to login using their existing IdP.
Many clients have specific security policies in terms of password length, password expiration, password attempts that differ from Talent Transform’s built in policies. This would allow them to be compliant with those as they are maintained within their existing IdP and for Talent Transform not need to customize to fit those policies.
This also provides additional security as admins would not have to remember to remove terminated users from Talent Transform manually. Generally, those users will already have been de-provisioned from their IdP as part of the termination process to eliminate access, which then would automatically remove the required authentication method.
Value to Lightcast
Sometimes we do things for our own benefit. List those reasons here.
Lightcast employees would be able to login via Google
Target User Role/Client/Client Category
Who are we building this for?
Users with SSO
Delivery Mechanism
How will users receive the value?
They will see options for SSO on the login page
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?
Users will not need to create a separate password credentials to login to Talent Transform
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.
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 |
---|---|---|
|
|
|