Client: Metronet The project implemented API connections to Pega from legacy Java based system (Itential). Itential connects between Telecom hardware devices to furnish telemetry data to a Customer Services user interface, enabling prompt resolution to customers problems within a call center environment.
*Initiated and conducted Discovery sessions with the product owners and SMEs
*Initiated and conducted DCO sessions with network engineers to extrapolate detailed requirements, current architecture and workflows
*Managed SCRUM ceremonies from Sprint planning to Sprint retrospective sessions
*Conducted Business process re-engineering sessions and Grooming sessions to finalize the requirements
*Created product backlogs, and functional design documents along with technical design document generation using Pega auto documentation wizard.
*Authored requirements capturing template to aid in the requirements gathering process.
*Streamlined new Pega developer onboarding process and QA de

Client: State of Massachusetts The project implemented a simple Proof of Concept to automate a customer service workflow, that enables customer service agents to correspond using Auto AI generated email messages and organize their day to day tasks.
*Initiated and implemented End to End requirements gathering sessions with the product owners and SMEs
*Worked with Pega development team to perform Demo of Pega out of the Box features to the client
*Engage with various stakeholders to extrapolate detailed correspondence and workforce management workflows
*Create and manage product backlogs in Jira
*Created product backlogs, and functional design documents along with technical design document generation using Pega auto documentation wizard.
*Authored requirements capturing template to aid in the requirements gathering process.
*Collaborate in the creation of rollout of delivery plans and UAT user base training.

Client: T-mobile T-mobile is also trying to implement Pega's CDH (central Decisioning Hub) to gain a better competitive edge amongst other telecommunication carriers. The tasks performed here are identical in nature with Verizon project, however the scope of delivered functionalities are very limited in this T-mobile engagement:
*Onboard and interview new resources to form a competent Pega decisioning team.
*Work on extrapolating requirements for current adaptive and predictive models by engaging with data scientists at T-mobile
*Engage with various stakeholders to extrapolate detailed retention and add a line requirements
*Create and manage product backlogs in Jira
*Strategize and plan long term roadmap on how Pega and Infosys team can work together on this joint venture project.
*Participate in Database upgrade and design implementations for Pega 8.3 (using NOSQL approach)
*Collaborate in the creation of rollout an delivery plans using docker and Kubernetes

Client: Verizon Verizon has implemented Pega's CDH (central decisioning hub) to better serve its customer and increase their sales revenue. Its main objectives are to predict customers that are about to churn and initiate retention strategy, Predict possible upsell opportunities with current customers and manage various other decisioning related outcomes with their customer base.
*Document and understand their entire Pega CHD architecture and solution to increase the performance of CDH
*Improve their current adaptive and predictive models by driving out additional predictors and documenting them
*Engage with various stakeholders to extrapolate requirements for Upgrade from Pega 8.2 to 8.3
*Engage with design and architecture team to properly align business objectives with Pega's proposed performance improvement designs.
*Perform statistical analysis with the help of data scientists to test historical performances of various predictors on customer's churn rate and add a line use ca

Client: Frontier Communications Frontier Communications is upgrading its existing enterprise application system for its call centers, product management suite and service outage alerts system using Pega. I was in charge of managing, eliciting and designing solutions for their API requirements
•Managedand conducted SCRUM Ceremonies for new API development such as Sprint Planning, Daily SCRUM, Sprint Review, Sprint Retrospective, Backlog Refinement meetings and Requirements gathering or Joint Application Development (JAD) sessions.
•Ensureall the participating stakeholders and implementation teams are on the same page as to what requirements and capabilities are needed to be developed for the proposal.
•ConductDCO sessions (Direct Capture of Objectives) to drive out project requirement in details and also enable the team to come up with better estimates and delivery timelines.
•ComposeWorkflows, DFD Diagrams and Level 2 User Stories to be incorporated in the Pega 7.x tool and attach

Client: GDIT GDIT implemented a claims processing system for their insurance client using Pega Smart Claims Framework.
•Implemented2 factor authentication using google authenticator in Pega
•Creationof activities, steps and methods like property set, page new, calling other activities for implementing core business logic.
•Implementationof Decision tables, Decision Maps and Declarative expressions.
•Involvedin Bug Fixing Activities, Harness, Declare Expressions and When Rules.
•ConvertedTables from blob in Database for better performance
•Designedworkaround to address performance issues in production

Pega Architect Client: U.S Department of Commerce The U.S Census Bureau is using Pega to digitize their manual paper processing for their address canvassing and enumeration survey operations:
•Created High Level Class structure in Pega Rules Process Commander.
•Creationof activities, steps and methods like property set, page new, calling other activities for implementing core business logic.
•Implementationof Decision tables, Decision Maps and Declarative expressions.
•Involvedin Bug Fixing Activities, Harness, Declare Expressions and When Rules.
•CreatedTechnical Design documents and Pega Flows, comprising of Screen Flows, Process flow and straight through process flows.
•Workedwith Systems Analysts, Product owners, Census Stakeholders and Developers to capture requirements and DCO sessions for project sizing, application Design and development using Case Management framework.
•Activelyparticipated in the requirements design and build phases, delivering high quality deliverable

Client: TSYS Tsys handles credit card processing for major onshore and offshore Banks and has implemented Pega to be the interface between their mainframes and Customer Service Reps. Pega portals for CSRs helps serve their customers using a front End Pega application that uses special rules to communicate with the Backend mainframes.
•Actas an Agile coach and Pega SME to provide guidance and improve existing requirements gathering process using DCO and improve documentation.
•DerivedWorking Agreement, Definition of Ready and Definition of Done with various SCRUM teams. Enforced adherence to the guidelines established as a result.
•Created High Level Class structure in Pega Rules Process Commander.
•Creationof activities, steps and methods like property set, page new, calling other activities for implementing core business logic.
•Implementationof Decision tables, Decision Maps and Declarative expressions.
•Involvedin Bug Fixing Activities, Harness, Declare Expressions and When Ru

Agile Lead System Architect (LSA) Client: John Deere John Deere is developing Artificial intelligence capabilities that can automatically assist their dealership service technicians in troubleshooting and diagnosing tractors, engines and other industrial equipment. Pega is building this "Next Best Action (NBA) functionality, using Pega's case management and decision management features, which would enable John Deere to not only author their diagnostic procedures, but also to save time and money by delivering quality maintenance support services to their dealers worldwide.
•Managedand conducted SCRUM Ceremonies such as Sprint Planning, Daily SCRUM, Sprint Review, Sprint Retrospective, Backlog Refinement meetings and Requirements gathering or Joint Application Development (JAD) sessions.
•Ensureall the participating stakeholders and implementation teams are on the same page as to what requirements and capabilities are needed to be developed for the proposal.
•ConductDCO sessions (Dire

TMNA (Tokoyo Marine North America) is implementing a Pega 7 pilot project to automate their workflow management using Pega. In this role my primary function was to implement the solution with limited time at hand and manage a tight budget. The main objective of this project is to reduce workload, create efficiency and automate business process.
•Ensurethe project is operating within budget by cutting down operational costs, implement rapid development of requirements and rapid deployment of codes using prototyping techniques and accelerated code development methodology.
•Deliverengagements to the agreed customer scope, timescales, budget, and quality metrics, as well as assisting customers to achieve the expected ROI.
•ManageClient expectations and drive out project requirements.
•Actas a trusted advisor and coach to the client and staff on all aspects of Pega engagement, leading communication and providing thought leadership so that the best possible solution is implemented.
•Hel