an agile approach to ebs enhancements · internally operating oracle erp / hcm / epm / sales and...
TRANSCRIPT
** Distribution Restricted **
An Agile approach to EBS EnhancementsDelivering quality, faster
The Evolution of IT Delivery MethodologyAge of enlightenment
In the beginning…
Traditional Waterfall Methodology
Waterfall Methodology
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Developers agree design early in development cycle
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Waterfall Methodology - Positives
Waterfall Methodology - Positives
Developers agree design early in development cycle
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Progress is more easily measured, as the full scope
of the work is known in advance
Waterfall Methodology - Positives
Developers agree design early in development cycle
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Progress is more easily measured, as the full scope
of the work is known in advance
Resource engagement fluctuates depending on
phase allowing other/external activities to continue
Waterfall Methodology - Positives
Developers agree design early in development cycle
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Progress is more easily measured, as the full scope
of the work is known in advance
Resource engagement fluctuates depending on
phase allowing other/external activities to continue
Out-with progress meetings and approvals, customers
are not required after the requirement is defined
Waterfall Methodology - Positives
Developers agree design early in development cycle
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Progress is more easily measured, as the full scope
of the work is known in advance
Resource engagement fluctuates depending on
phase allowing other/external activities to continue
Out-with progress meetings and approvals, customers
are not required after the requirement is defined
Natural flow to development with less risk of “piecemeal”
Waterfall Methodology - Positives
Years of utilisation and success
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Waterfall Methodology
Years of utilisation and success, but . . .
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Waterfall Methodology - Negatives
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Effectiveness of Requirement
- Customer is not clear on what they really want
- Customer is hesitant to commit to detail
- Customer cannot visualise the solution
Waterfall Methodology - Negatives
1. Gather and document requirements
2. Design
3. Code and unit test
4. Perform system testing
5. Perform user acceptance
6. Fix any issues
7. Deliver the finished product
Effectiveness of Requirement
- Customer is not clear on what they really want
- Customer is hesitant to commit to detail
- Customer cannot visualise the solution
Customer may not like the end result
Historical Moment
What happened in Utah, Feb 2001 ?
Historical Moment
Birth of the Agile ‘Software Development’ Manifesto
Agile Manifesto Principles
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Agile Methodology Definition
Agile software development methodology is based on iterative development,
where requirements and solutions evolve through collaboration between
self-organizing, cross-functional teams and the customer.
Our Customer Case StudyThe guinea pig
About TechnipFMC
Global, Oil & Gas Company - Oracle 12.2.7
€11.1 Billion Revenue (2016)
48countries
40,000+ Employees
MultipleRoll-outs& Upgrades
ERP
SCM
HCMProjects
Custom
Up to
75Consultants
ContinuousEnhancement
Stream
Implemented Oracle
Module Footprint
FINANCE SCM PROJECTS HR
General Ledger
Fixed Assets
iExpenses
eTax
Accounts Payable
Accounts Receivable
Cash Management
Subledger Accounting
iProcurement
Purchasing
Inventory
Sourcing
iSupplier
Project Costing
Project Billing
Project Cost Control
Project Management
Human Resources
Absence Management
Self-Service HR
Time & Labor
Resource Management
Compensation Workbench
Structure
System blueprint for the
business; configuration,
governance and processes
Rollouts and Group Project
Delivery
Business and Solution led
improvements via config
and customisation
Regression Testing(URT)
Solution Testing(UAT)
Development(MD.070)
Solution(MD.050)
Requirements(BR.030)
REQUIREMENTS & SOLUTION DESIGN
▪ Time to define true requirement in detail required for planning and execution
▪ Time to determine solution and obtain full agreement
▪ BR.030 too complex
▪ Business provide solution, not true requirement
Waterfall Points of Failure for Enhancements
Regression Testing(URT)
Solution Testing(UAT)
Development(MD.070)
Solution(MD.050)
Requirements(BR.030)
SOLUTION DESIGN & DEVELOPMENT
▪ Time to document full solution (MD.050) for development to begin
▪ Solution adjustment due to technical restraints
Waterfall Points of Failure for Enhancements
Regression Testing(URT)
Solution Testing(UAT)
Development(MD.070)
Solution(MD.050)
Requirements(BR.030)
USER ACCEPTANCE & REGRESSION TESTING
▪ Solution does not meet business expectation
▪ Solution fails during UAT testing
▪ Solution fails during URT testing
▪ Wasted time for configuration / deployment to environments
Waterfall Points of Failure for Enhancements
ENHANCEMENT LIFECYCLE
▪ Loss of focus and engagement for enhancement
▪ Lack of resource availability
▪ Full lifecycle time can take 3-6 months for a single enhancement
Regression Testing(URT)
Solution Testing(UAT)
Development(MD.070)
Solution(MD.050)
Requirements(BR.030)
Waterfall Points of Failure for Enhancements
Addressing the challenge with AgileTime for change
Blue-sky thinking within Boundaries?
REQUIREMENT SPRINT
TESTING
RELEASE
Change Request raised; what, where,
why? Discussion between BA and
Business
SOLUTION
Design Authority to decide general
solution target. Discussion between
SSL, BA, Functional and Business
Complete full testing of solution based
on generated list of Test Scripts. UAT
and URT carried out in synchrony
Phased Development focusing on
regular review cycles to progress
solution and validate
BA validated release testing and then
Production release of solution for
business use
Applied Agile (Hybrid) Process
Agile Process - Requirement
NEW REQUEST
IDENTIFIED GAP
BUSINESS INITATIVE
• Same Methods of Identification
Agile Process - Requirement
WHAT
WHERE
WHY
?
?
?
• Same Methods of Identification
------------------
• Clear and Simple Definition (User Stories)
Agile Process - Requirement
Agile Process - Solution
DESIGN
AUTHORITY
• Collaborative Review of Requirement & Solution
Design
Agile Process - Solution
• Collaborative Review of Requirement & Solution
Design
------------------
• MD.050 Document During & Upon Completion
of Solution Build
MD.050
PRODUCED
IN TANDEM
Agile Process - Solution
Agile Process - Sprint
• Plan Sprint Phases
• Identify Deliverables
• Confirm Resource Requirements
SPRINT PLANNING SESSION
Agile Process - Sprint
• Plan Sprint Phases
• Identify Deliverables
• Confirm Resource Requirements
------------------
• Iterative Phases of Development (Sprints)
ReviewReview
Review
Review
Sprint 1 Sprint 2
Agile Process - Sprint
Sprint
Review
Agile Process - Sprint
• Plan Sprint Phases
• Identify Deliverables
• Confirm Resource Requirements
------------------
• Iterative Phases of Development (Sprints)
------------------
• Emphasis on and importance of Testing
COMMUNICATION
• Daily Stand-ups
• Sprint Completion Reviews
Review
Agile Process - Sprint
REQUIREMENT SPRINT
TESTING
RELEASE
SOLUTION
Agile Process
The ResultsAdoption and Delivery Impact
The Same, but Different
AGILE
REQUEST SOLUTION DESIGN SPRINT TEST
WATERFALL
REQUIREMENT SOLUTION DESIGN DEVELOP USER TESTINGREGRESSION
TESTING
Keep the change familiar to ease adoption.
Evolve to a clear target
AGILE
REQUEST SOLUTION DESIGN SPRINT TEST
Control the scope creep.
• User Stories • Fix 80% Scope
• Iterative Development
• Constant Solution
• Relative Changes
• Pass Confidence
Results
AGILE
REQUEST SOLUTION DESIGN SPRINT TEST
Results
AGILE
REQUEST SOLUTION DESIGN SPRINT TEST
About Inoapps
Oracle Platinum PartnerLargest Independent Oracle
Specialist Partner in EMEA
2016 Oracle Specialized
Partner of the Year SaaS Cloud
Transformation – Global
Expertise in Hosting,
Managed & Cloud Services
2018 Cloud First
Partner of the year – UKI
Internally Operating Oracle
ERP / HCM / EPM / Sales
And Marketing Cloud
25+ customers in the
Cloud and counting300+ Staff Globally
Innovative Products Division
Delivering extensions to
Oracle Cloud
Established On / Offshore
Global delivery model
Andy Birdstarts Inoapps
Teamsolve
D E R B Y
BGF Investment
M A L A Y S I A
CrocusConsulting
U S A
L I N L I T H G O W
S I N G A P O R E
2016 Oracle Specialized Partner of the Year: SaaS Cloud Transformation – Global
2006 2010 2014 2016
2008 2012
2018
2015 2017
Houston
London
Aberdeen
Edinburgh
Derby
Kuala Lumpur
Singapore
Oracle’s Managed Service Provider Program
Oracle Specialized Partner of the Year for Database as a Service – UKI
Indigo Tide
E D I N B U R G H
2018 Oracle Cloud First Partner of the Year UKI
20221000 employees worldwide
Inoapps & Scotland
Sits on the board of ONE
(Opportunity North East)
DIGITAL and ENTREPRENEURSHIP
Initiative
Oracle Cloud References in
Scottish Public Agencies
(Scottish Legal Aid
Board)
CODECLANGRADUATE
SCHEME
EDINBURGHLINLITHGOW
GLOBALOPERATIONS
OFFICES
EDINBURGH& ABERDEEN
FOUNDED
2006
ABERDEEN
PRODUCTS
R&D
30
ENTREPRENEUROF THE YEAR
E&Y
SCOTLAND
2017Finalist
TECH
IDENTIFIEDUNICORN
SCOTLAND
Inoapps Key Focus AreasORACLE SaaS APPLICATIONS
PaaS for SaaS INOAPPS PRODUCTS
• Right equipment, right place,
right time – every time.
• Save money & Increase
efficiency.
• Visibility & control from
acquisition to receipt.
• Ensures regulatory
compliance.
• Automatically create billing
events based on Oracle
Project expenditure items.
• Save time by eliminating
manual re-keying, freeing
people up for other tasks.
• Accurately capture, track, allocate and
recover costs for any Joint Venture
operations, in any country or currency.
• Improve decision-making by reporting
data reconciled in real-time.
• Streamline workflow and reduce errors.
• Partner portal encourages info sharing &
joint working.
• Get the right people to the right place at
the right time – every time.
• Integrate with time-writing and payroll.
• Make huge cost & efficiency savings
with improved resource planning, time-
writing and payroll management.
• Full visibility of equipment in the field,
in real-time – third party & internal.
• Reduce financial impact of
losses.
• Increase rental contract profitability.
• Save time & money.
• Enhance customer relationships.
01MANIFESTING
03PROJECT BILLING
05JOINT VENTURE ACCOUNTING
04SCHEDULING
02EQUIPMENT RENTAL
Extend Your Oracle Cloud Footprint With Inoapps’ Industry Solutions
Industry Focus
Current Industry Solutions:
• Construction & Engineering
• Professional Services
• Public Sector
• Higher Education
• Oil & Gas
• Healthcare
• Gaming
• Finance
• Travel and Transport