SailPoint ‐ Weekly minutes - razmipatel/Random GitHub Wiki

Summary of the Call – Key Points and Actions

🔐 SailPoint Integration & Access Requirements Authentication: Agreement reached to use OAuth for all access to SailPoint; pending confirmation from the I-Request team.

Design Documentation: Two design docs related to attestation and tagging were shared by Sean on Friday, 5th July. Follow-up review required.

Limitations Identified:

SailPoint cannot currently add users as eligible members to Entra ID groups.

SailPoint cannot read eligible group members for attestation purposes.

These limitations require custom scripts to manage eligible membership assignments and attestations.

Custom Scripts:

One script will handle adding/removing eligible members based on I-Request.

Another script will be used for attestation, to identify and remove stale eligible assignments.

Approach mirrors compliance scripting currently used in other connectors.

📆 Timelines & Resource Planning KTSL Statement of Work (SoW):

Work planned to begin 10th July, ending 10th August.

SoW includes the B2B and groups forms.

A separate SoW covers Entra ID roles (PUR form).

SailPoint SME: Expected to onboard next week and begin development on a dev environment.

Attestation Development: Can be worked on in parallel while I-Request integration is still pending.

Delivery Phases Clarified:

Connector First (tested with Postman/API)

I-Request Integration second

Attestation last, likely aligned with quarterly access review cycles

✅ AIB Framework & Delivery Alignment AIB Delivery Framework:

Emphasis on aligning activities with standard controls:

High-Level Design (HLD)

QA/Test Plan

Pre-Prod validation

Production readiness

Sean advised incorporating standard terminology and controls for clarity and governance alignment.

Action: Razmi to align project tasks to AIB delivery terminology and lifecycle (e.g., HLD sign-off, QA approach).

📊 Effort Estimation & Excel Sheet Discussion Resource Breakdown Request:

PMO requested task breakdown by resource (Sean, G, Michelle).

Total effort estimated: 25 days collectively across 3 Infosys resources + 5 days SailPoint PS.

Feedback:

Sean raised concerns that such granular breakdown (e.g., hours per task per resource) is unnecessary and not aligned with how partners typically work with AIB.

Action: Kamal to revise and simplify Excel sheet per project agreement with Razmi.

🚧 Project Governance & Delivery Leadership Delivery Lead Gaps:

Multiple changes in delivery lead (Aaron → Carolina → Kamal) have caused misalignment and lack of delivery framework knowledge.

Need for clear delivery lead assignment and alignment with AIB’s standard project delivery methods.

Suggestion made to engage AIB’s internal delivery team for consistent oversight.

📌 Agreed Next Steps Razmi to review and align task list with AIB delivery framework terminology.

Kamal to revise the Excel resource breakdown sheet and reissue it.

Razmi to merge minutes and Kamal’s notes and send summary on Monday.

Kamal to speak to Nick and clarify open issues, copying stakeholders.

Attestation campaign design and planning to proceed independently of I-Request timelines.

Infosys/SailPoint to begin development in dev once access is provided.