Embed Size (px)
Citation preview
A Stack that Drives Digital Transformation
Vikas Agarwal
Prabhu Jha
Key Drivers
Key Challenges with Legacy
Closed to extension, less flexible for
adaption
High costs of storage, infrastructure, people
Lot of manual tasks –Error prone and
difficult to automate
Expensive UX/CX modernization
Customer satisfaction
Profitability
Competition
Increased speed-to-market
What and Why of Digital Transformation?
Implementation of technology strategically that delivers clear results, including:• Getting to market faster and more effectively• Innovative new business models, products, and services• Optimized business operations• Exceptional end-to-end customer experiences
Change management,KPIs
People, teams,culture
Emergency Managed Optimized
Digital capability developmentnot central to organizational strategy KPIs
• Isolated knowledge • Vertical skillsets• Poor training
Strong digital vision and strategy,organizational priorities KPIs change
• CoE
• Specialists and generalists
• Tech skills
• Fluid structures
• Collaborative environment
Digital vision lived through leadershipand operations, top-down bottom-up,agile and adaptive strategy
• T-shaped, • Deep knowledge, • Human layer over tech, • Knowledge sharing, • Entrepreneurial
Working practices,processes, tools
• Frigid structure, • Waterfall,• Infrequent release cycle• No DevOps• Manual testing
• Agile development• Automated tests,• rapid prototyping and
continuous build• DevOps Readiness
• Interdisciplinary agility, • cross-functional,small, nimble
teams.• DevOps Implemented
Process FlowFoundation Intermediate Advanced
Digital Maturity Model
Social
Mobile
Analytics
Cloud
Integration
friendly
Real-time
data
availability
Speed of
development
Agile/ DevOps
friendly
Supports
Great UXPerformance
Big Data
Support
Goals of Technology Selection for Digital Transformation
Pillars of Digital Transformation
Right Technology and toolset – MEAN
Right Technology and toolset – MEAN
JSON Everywhere – DB, Back-end, Front-end
Isomorphic JavaScript
Event-based non-blocking I/O
Fast response times for data availability
Microservices as opposed to traditional monolithic applications
TDD/BDD Karma, Mocha, Chai, Jasmin, Protractor etc.
Schemaless Database: MongoDB
Minimalistic ExpressJS framework
AngularJS for maintainable front-end code
Built-in plugins for various client-side libraries
Integration
friendly
Real-time
data
availability
Speed of
development
Agile/ DevOps
friendly
Supports
Great UX
Performance
Big Data
Support
Why MEAN Stack?
Replacing your current applications
Augment/reuse your existing applications
Less complexity
Quicker ROIShorter program duration
Higher cost Cost of legacyHigher data migration
costs
Risk of business
disruption/discontinuity
Higher cost of quality
Requires more domain
expertise and analysis
Longer program duration
Stakeholder Management
for Longer Duration
Intense AS-IS analysis required
ROI will take time
Maximize use of legacy IT
assets
Domain expertise built
into the system
Easier Change Management
Lowered Risk of Business
discontinuity
Lower cost of quality
Better goal tracking/ success
measurement
Ways of architecting your transformation
Mobile
IoT
Social
Node.JS + Express + MongoDB/Mysql
Progress BackendWeb
ProgressWeb services
Modulus Cloud
RESTWeb
Services
Omni-channel Consistent Customer Experience
Analytics
Partners, customers, third-parties
Proposed Technology Situation
Proposed Architecture – Detailed View
Identify the least risky business
areas and document them
Identify the desired UX Goals,
plan UX Transformation
Identify the solution building
blocks
Develop their replicas (with
enhanced UX) on MEAN stack
Run parallel beta and then, conduct A/B tests or MVT
Integrate into the remaining of the system and make
production deployments
Develop DevOps capability
Start with Continuous Integration
Unit Test Automation
Functional Test Automation
Continuous Delivery
Identify Cost Centres (servers, infrastructures)
Identify right Cloud Solution
Plan for deployment and
Business Continuity
Transformed Increment
Overall IT Spectrum
IT increment to be transformed Transformed IT Spectrum
Transformation Roadmap
An ISV having a product built on Progress 8.
State prior to transformation:
- Windows based GUI application
- No Web interface
- No mobile application
- Expensive non-standard based integration with third parties
AS-IS Analysis
Usability study
Cost centres and revenue leaks
Scalability, performance bottlenecks
Constraints related to multiple channels
TO-BE Analysis
Identified new UX goals
Identified new goals related to i18n, localization, scalability
Forecast data volumes
Identified analytics needs
Identified social reach-out needs – multi-channel capability
Adopted Agile, started CI, mandated unit tests (front-end and backend both), built test automation framework, automated testing.
Performed UX transformation for Web & Mobile (responsive design) – AngularJS and KendoUI
Upgraded Progress OpenEdge to v11.6 Chose appropriate cloud based on the data volume forecasts Designed and created Node.js API economy, set up automated
regression tests (Swagger, 3Scale and SOAPUI) Integrated Web Analytics (Google Analytics) Consumed API into a mobile app (Telerik Platform)
Approach to Transformation
Example Use Case
Relevance to Progress Ecosystem
PAS
Offers a no-obligation assessment of your legacy applications
Helps you with full lifecycle of MEAN applications: design, development, code-reviews, deployment and maintenance.
Helps you move away from monolithic systems to microservices or SOA based systems
Helps you plan your UX transformation
How JKT helps You Transform
Q & A
