Delivery Management

Assessment for Elizaveta Anatskaya

2025

hi, I am lisa. nice to meet you!

Certifications

Azure Fundamentals (AZ-900)

Professional Scrum Master (PSM I)

Project Management Professional (PMP)

Delivery Management School Program

Solution Architecture School Program

Managers' Mentoring Program

Successful Negotiations with Customer

Sandbox Activity

My path

Yamaha crm-reboost project

+ project status

RAG red, abmer, green

be ready to answer which epam tools I use, metrics
-----

screen from DC
PERF - client satisfaction survey, NPS net promoter score
metrics https://telescope-ai.atlassian.net/wiki/spaces/EPMDMO/pages/403115419/Metrics+Catalog

Key impacts

Main achievements – Sprint planning table

Main achievements – Clear timeline

Risks/dependencies tracking

features alignment

Onsite qrp collaboration with customer

Yamaha crm-reboost project

Clean architecture

Project's architecture

The CRM Reboost MVP architecture is a React-based web application that communicates directly with Salesforce as its primary backend, without intermediate AWS or Informatica middleware.

Authentication is handled through Salesforce Partner Community using OAuth 2.0, triggered directly from the React frontend via a connected app.
The React portal is hosted and served from AWS S3 buckets, along with third-party tools like INDG’s 3D configurator and Storybook-based UI components.
The application integrates with Salesforce APIs out of the box, consuming standard endpoints to fetch, upsert, and delete CRM data. Any required data transformation is handled within the React layer.
Custom REST APIs in Salesforce are avoided unless strictly necessary to support complex operations like sequential API execution or mixed DML, to minimize long-term technical debt.
Monitoring and alerting includes tracking Salesforce API usage and latency. The React app is expected to handle and log failures via the Salesforce Error Log API.

This architecture provides a lean, performant, and modular front-end experience, with minimal backend complexity and strong alignment with MVP principles.

post-MVP phase Architecture

where is business logic? why not in SF
why SF? if not business logic
maybe for usemanagement

BFF?

post-MVP phase Architecture

Client-facing architecture using Next.js SSR hosted in AWS EKS, served via CloudFront CDN and secured with AWS WAF and Application Load Balancer.
API Gateway acts as the central entry point for backend services, receiving both:
- Direct API requests routed via ALB
- Internal SSR app requests during page rendering
Authentication and authorization handled by Lambda Authorizer with token validation before forwarding to business logic
Business logic layer implemented with AWS Lambda functions:
- Core Logic Lambda handles processing, caching (Redis), and full-text queries (OpenSearch)
- Logging Lambda captures operational data, routed to CloudWatch
Data tier includes:
- PostgreSQL cluster with asynchronous read replica
- Redis for caching and OpenSearch for search and analytics
3rd-party INDG Configurator is embedded in the frontend; config data is passed from the frontend to INDG and visualized client-side
Salesforce integration used for CRM data synchronization and token validation via Lambda
CI/CD pipeline uses Jenkins → CloudFormation → Big Bang Deployment to manage infrastructure provisioning and EKS application delivery

Architecture Decision Table

justification for promotion and goals for future

Future Goals

Transition into a self-sufficient Delivery Manager role, independently owning delivery scope, execution, and stakeholder engagement
Obtain certifications in key areas to strengthen delivery leadership:
▸ Cloud platforms (AWS/GCP/Azure)
▸ SAFe for scaled agile delivery
▸ Six Sigma for process improvement and operational excellence
Mentor and scale delivery culture by supporting coordinators, standardizing tools, and contributing to internal best practices
Build expertise in financial control (e.g. margins, T&M/Fixed scope models)
Presales participation

I am already performing at the level expected of a Delivery Manager—handling multi-team delivery, leading stakeholder engagement, owning reporting and sprint predictability, and aligning teams across business and tech. I have also contributed by interviewing and developing internal tools like Epam URL and the Planning Poker Tool, both actively used internally. Additionally, I’m committed to continuous growth, pursuing certifications such as PMP, Scrum Master, and Azure, and actively participating in EPAM courses like DMS.

Mentors' Feedback

Projects Feedback

Projects Feedback

Projects' Feedback

Thanks

Elizaveta Anatskaya