🔹 Key Summary Points

Three Core Workstreams Identified:

Requirements Gathering: Clearly define and document requirements, especially for amalgamating the current AD Connector with the new Wind RD Connector.

Testing: Ensure comprehensive testing of all functionalities post-integration.

Attestation Solution Design & Delivery: Build and deliver a robust identity attestation process post-testing.

Main Concerns Raised:

Lack of Clear Requirements: Development has started without documented requirements, raising concerns about delivery misalignment.

Project Ownership Confusion: Multiple changes in project management (Kamal new, Caroline left, unclear PM roles), causing delays and repeated communication.

Resource Prioritisation & Project Code: No project code confirmed, blocking work. Request made to Simon Toland for confirmation and prioritisation.

Repeat Requests: Same data (e.g., rate cards, SOW) repeatedly requested by different people without clear reasoning, wasting time.

Risk of Misalignment: Development teams risk delivering a solution that doesn’t meet regulatory or business needs.

Action Items and Follow-ups:

Request Finalised Project Code and get work formally approved by Simon Toland.

Meet with Kamal to clarify SOW scope and timeline expectations.

Identify Key Data Fields for onboarding B2B users and determine if SailPoint IdentityIQ or native SailPoint forms will be used.

Review Integration with SailPoint Utility: Explore prebuilt forms/utilities to meet compliance and DORA requirements.

Schedule Discussion with Jan/Scott on IdentityIQ integration options.

Technical Requirements:

Maintain current app functionality in the new connector.

Ensure B2B users are properly set up in the warehouse to allow early attestation.

Evaluate the SailPoint IdentityIQ solution as a faster route for compliant onboarding.

Operational and Governance Notes:

Emphasis on capturing all required identity governance fields (role, manager, reporting line, etc.).

Concerns raised over SailPoint form integration versus developing new custom forms.

Need to avoid duplicating tools or building custom solutions if a ready-made utility exists.

Team Dynamics and Frustrations:

Frustration around lack of project direction and repeated tasks.

Concerns about delivery accountability falling on technical staff rather than PMs.

Ongoing misalignment between delivery, technical teams, and external vendors (Accenture).

🔸 Next Steps Get Project Approval & Code: Confirm priority and secure Simon Toland’s sign-off.

Define Requirements: Create and share a clear, formal requirements document.

Engage with SailPoint Team: Understand existing capabilities and decide on integration path.

Plan Testing & Attestation: Begin planning the attestation solution once functionality is validated.

Clarify PM Structure: Determine who is driving delivery and who owns timelines to prevent further confusion.