Technical Analyst

Technical AnalystProject: Identity and Access Management for Customer PortalProject Scope: Technical and functional requirements for migration of a segment of CFC’s customer base onto a new identity management platform; moving from Dominos/Lotus Notes to Adobe AEM and Okta. This will entail coordinating efforts for retirement of legacy apps and moving onto new platforms.Skills and Experience:Business analysis in an Agile / Scrum environmentUser story creation and refinementUser story management in JIRABusiness process flow creation and user management permission modelingExperience with identity management applications, document repositories, customer facing websites/portalsStrong communication skills and ability to work with both business and technical stakeholdersThis is not a specific IAM role. We need a strong Technical Analyst whose sole job is to work with the technology team and partner with our business partners to gather requirements for the 36 WebLogic Applications and AEM Content Pages and document the impact and what needs to be done for those artifacts to conform to our new AuthN and AuthZ model. This includes:Document requirements in JiraDocument our new permission model and updated business process flow and review for sign off from the businessMaintain Confluence pages of targeted impacted applications and proposed solutionOwn the Jira board from sizing to slotting stories in appropriate sprint and ensuring stories are signed off on and comments kept up to dateCreate Application documentation to guide the business on Authorization best practicesCreate Operational documentation to be used on how to maintain/support/update the Authorization Model to be used by support teamsWe don’t need a technologist that also does the implementation nor production support etc..The candidate does not need to know WebLogic, just understand 3 tier architecture and be able to assess which layer of the architecture is best for certain business and nonfunctional requirements. This is an Analyst position and not an architect nor implementer position. They need to capture the requirements and apply them to correct layers in the design in a requirements document.