Pramerica Systems Ireland

Lean Principles for Systems Development

Pramerica’s Journey to eliminate waste Mary Howick 8 th October 09 1

Prudential Financial Inc (NYSE:PRU)

Financial Services leader – 130 years in existence $580 billion assets under management Rock Symbol – Reliability, experience and strength Operations in US, Asia, Europe and Latin America 41,000 employees worldwide Diverse book of business Committed to Diversity and to community involvement 4 th on Fortune Worlds’ most admired companies list

Pramerica Ireland - June 2000

   Located in Letterkenny - 680 resources Supporting Systems and Operations across multiple business units Prudential’s strategic investment in an off-shore location with a lower cost model   Competitive to third-party service providers : provided over $152m in productivity savings to date.

Longevity, proven track record of quality, strong customer satisfaction ratings  Awards Received  Top 50 companies to work for in Ireland  Excellence Through People - Platinum  LOMA Excellence in Education

3

Lean Team Efficiency Ideas

Lean – our implementation Eliminate Waste

Bus Process Reengineering Agile for software development People Optimization

Team Alignment and visibility Empowerment Availability Qualification Engagement

4/27/2020

5

•

-Shared undestanding

•

Speedier decision making

•

Better communications

Requirements - Waterfall Methodology Business: Vision Analyst: Requirements Designer: Specification ir Business requirements 8 weeks Systems requirements 3 mths

4/27/2020

6 Program Spec 6 mths + 3 mths

Requirements - Agile methodology ir One Line requirement Create a User Story Add Acceptance Criteria

4/27/2020

7

Prioritization and work management

Requirements Backlog Backlog User Stories Just in Time acceptance Criteria.

Define Requirements Backlog Stories fully defined Based on business value • The Sprint is a time box. Dev & QA decide how much they can do • Prototyping used at the start • Management support and empower 4/27/2020 Sprint (3 wks) Completion (early release) 8

Lean/Agile – What has worked well

 Defining User Stories – 45 mins  Resource Alignment  Iterative development  Just in time - Backlog definition  Sprint Planning  Prototyping  Standup Meetings

Lean/Agile – Lesson Learned

 Issues in estimating  Other work impinging on Sprint  Work outside of our control  Representative from QA or Dev missing some calls  Partial requirements in a Sprint  Regression testing starting while Sprint bugs remain  Time creep in Stand up meetings  Gaining customer support