Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
Justifying and running a large Agile project
with Neo4j at its core
26th March 2019
© 2018 Achilles Information Limited | ...
2
• Achilles overview
• Justifying to the project to our investors
• Solution
• Architecture
• Data Model Overview
• Why G...
3
Working with
industry and
on behalf of
industry, to
provide
valuable
insight.
The Achilles Story
Working with
industry a...
4
Justifying the project to our investors
© 2018 Achilles Information Limited | Confidential
Process followed
1.Problem
analysis
2. Short term
stabilisation
3. Target
architecture
review
4. Prove the
product design
...
6
Develop product
offerings not bespoke
solutions
¡ Data driven architecture that allows content based product with no dev...
7
Solution Overview
© 2018 Achilles Information Limited | Confidential
Product
Definition
High Level
Product Backlog
Prioritise
IA
TA
Prod Manager & SME
BA
IA
Redbot
Feature Level
Product Backl...
9
High Level Solution Architecture
Peopl
e
Finan
ce
Achilles.com
(Public Website)
(Web chat)
Core
Titan
Question
3rd Party...
10
Extract from Data Model
11
Why graph is better for us
Collections-Focused
Multi-Model, Documents, Columns
& Simple Tables, Joins
Neo4j is designed...
12
• Search is faster than our SQL or NOSQL solutions
• Target sub 3 second response
• Achilles’ business is all about mak...
13
Current situation
© 2018 Achilles Information Limited | Confidential
14
§ First customer Community is live on new platform
§ In process of arranging engagement with Neo Innovation Centre re G...
15
Questions
© 2018 Achilles Information Limited | Confidential
Prochain SlideShare
Chargement dans…5
×

Justifying and running a large Agile project with Neo4j at its core, David Swayne, Achilles

390 vues

Publié le

Neo4j GraphTour Europe 2019 - Customer Presentation:
Justifying and running a large Agile project with Neo4j at its core, David Swayne, IT Consultant, Achilles

Publié dans : Logiciels
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Justifying and running a large Agile project with Neo4j at its core, David Swayne, Achilles

  1. 1. Justifying and running a large Agile project with Neo4j at its core 26th March 2019 © 2018 Achilles Information Limited | Confidential
  2. 2. 2 • Achilles overview • Justifying to the project to our investors • Solution • Architecture • Data Model Overview • Why Graph is better for us… • Current situation © 2018 Achilles Information Limited | Confidential Agenda
  3. 3. 3 Working with industry and on behalf of industry, to provide valuable insight. The Achilles Story Working with industry and on behalf of industry, to provide valuable insight. Businesses are not just responsible for what we do – we’re also accountable for what’s done on our behalf. And there’s a need for control… In 1990 operating in the gas and oil industry, we saw buyers needed more control. We designed our community model, supporting services and the technology to address this. We wanted to bring suppliers into the fold – to help them meet buyers’ needs while reducing their own qualification burdens. With stakeholders holding businesses to ever-higher standards, it’s important businesses have a complete picture of their supply chains Now we’re serving a network of over 800 buyers and 175,000 suppliers in all kinds of industries. We’re proud to be part of a truly worldwide community dedicated to raising standards and doing business in ways that benefit everyone.
  4. 4. 4 Justifying the project to our investors © 2018 Achilles Information Limited | Confidential
  5. 5. Process followed 1.Problem analysis 2. Short term stabilisation 3. Target architecture review 4. Prove the product design (POC) 5. Business case iteration ActivityOutput • Interviews with customers & staff • Analysis of existing platforms • Review of service issues • Improve governance • Review organisation • Contract review • Corrective actions • Modern methods • Review requirement • Propose technical solutions & architecture • High Level Design (HLD) • Estimate costs / benefits • Wireframe design in conjunction with product • Import data from 4 platforms • Build Search & other key functions 27 page report delivered to Board in April • HLD based estimate • Stabilisation measures • Detailed planning • Estimate costs / benefits • Product testing New Organisation D4 Product Life Cycle Management Outline Business Case July Tested success criteria POC Success Criteria Demo system for customers Full Business Case Silxo Confidential: Version 1. 1. Achilles Technology Review 22nd April 2017 Prepared by: Tim James– Silxo Ltd 1 Introduction: This report summarises the problems of the current Achilles product and IT landscape. It describes the situation at the time of the appointment of the new CTO, Tim James. It outlines the problems in product management, the gaps in IT processes, the deficiencies in the IT architecture and platforms as well as the overall operating model. It identifies the actions needed to address these and prioritises them based on criticality. The Appendix outlines the architectural characteristics and issues in each of the platforms. 2 Executive Summary 2.1 Findings • CTO area is responsible for product management and technology. Capability in these areas is low and heavily duplicated across regions, with 5 development centres doing similar things to competing platforms. There is no global control of delivery or join up between different parts of the organisation’s capabilities. • The cost of the CTO function is high, relative to the turnover, but IT has been seen as a reactive service that should respond to any sales opportunity. There is no understanding of the cost of running the BAU service vs. the investment made in innovation to differentiate Achilles from its cometitors– a principle that has been standard practice in all FS organisations for 20+ years. • The business is not designed around products, they have substituted so called platforms for products. There is no clear understanding of the P&L of the products, what drives profitability and where to invest to maintain revenue, grow business or expand into new markets. The product teams don’t understand what products or product features are important to customers. • Understanding business requirements was alien to the function and aggressively rejected in the Madrid office. Nothing was agreed with customers before work began, leading to debates about whether Achilles has delivered what was agreed once work was complete. • The focus on the AP2 project has failed and there is no global solution. This has led to major disappointment among customers and for regional teams to try to create a local solution to meet the global need. Mercure lacks clarity about what constitutes completed scope, any project controls, a business or systems design or a plan for how the service will be run. • There has been no attempt to architect or design solutions since Accelerate was built 8 years ago. All systems built since copy some of the failings of cD1 Design D2 Develop D3 Deploy D4 Deliver 1. Business Case 2. Product Canvas 3. Product Roadmap 4. Product Features/Benefits 5. Wireframes/User Stories 6. Architecture (4+1 model) 7. 4th Line Support 1. Service Development 2. Service Enhancement 3. Security 4. Service Scalability 5. Unit, Link Test 6. Technical Documentation 7. 3rd Line Support 1. Service Testing 2. Service Launch 3. Service Beta’s & Pilots 4. User Documentation 5. Service Transition 6. Security Testing 7. 2nd Line Support 1. Incident Management 2. Service Recovery 3. Service Performance 4. Service Change 5. Monitoring & NOC 6. Maintenance 7. 1st Line Support Product & Technical Design Service Delivery • Market / Personas • Investment • Features & Benefits • Functionality • Security • Release Schedule • Quality • Release to production • Transition • Performance • Value • Availability Customer (Expectations) • Strategic Advantage • Productisation • Partnership • Time-to-Market • Risk • Coverage • Architecture • Ease of Use • Security • Roadmap • Pilots • Integration • Business Value • Quality • Responsiveness • Consistency • Availability • Change • Performance • Volume Product and Technology Product Life Cycle Management (PLM) – ISO 27001 Compliant Artefacts • Vision & Roadmap • Priority Investments • Competition & Risk • Time to Release • Project Management • Agile Delivery • Pilot Size & Success • Days to Live • Penetration Testing • Uploads & Usage • Issues and Escalations • Failures & Code Changes Demand & Expectations Quality & Trust Develop & Deploy CTO Tim James Head of Development& Deployment– David Swayne Head of Architecture & Design – Navdeep Panaich Head of Service Delivery & Infrastructure – Mark Makepeace Head of Governance & Operations– Gareth Jones Director of Strategy & Product Management- Alex Myers -Product Management Team -Product Design Team - Architects -All Development Teams including Configuration - QA - Infrastructure - Service Delivery (1st /2nd Line support)- - Security -IT PMO/Project Management -Governance -Technical Bid Support/Demand Pune UK Mumbai Other Regions 1 Outline Business Case Nextgen Version 1.6 Date 20 July 2017 Authors Tim James David Swayne Navdeep Panaich Alex Myers Jonah Batambuze DRAFT 5.1 Proof of Concept Objective Measure Who by When Data richness: To illustrate that Neo4j can accommodate the richness of the Achilles model (which is currently distributed among multiple systems and technologies) in a single graph • Understandable for both business and technical staff • Able to support legacy “views” to minimise client migration effort • Able to support international language requirements • Adaptable to meet new business requirements Neo4j and Achilles 21st July 2017 Data source: To show that data can be loaded from existing systems • Data brought across different platforms (including V1, Ap2, FPAL, RQM) • All data accessible and searchable. Neo4j and Achilles 21st July 2017 Queries: To show that data can be queried easily • Data can be queried from a dotnet environment • data can only be searched, accessed and updated according the rights of the logged-in user • simple and complex queries. Ability to drill down on search to refine selection and obtain more detail about supplier and product • Search results available in Graph and List forms Neo4j and Achilles 30th August 2017 Performance : To show that the Neo4j-based solution will meet Achilles’s performance and availability objectives • Support database size of 8-10Tb • To prove that the service can be run in the cloud Neo4j and Achilles to access reference customer 21st July 2017 Supportability: To learn enough about Neo4j so Achilles and SILXO are confident the POC proves we can deliver a supportable next generation service • Knowledge can be transferred on support capability required • Neo support is adequate for Achilles and SILXO needs Achilles and Silxo 30th August 2017 Customer: To obtain feedback from Achilles customers on the potential solution and provide customer confidence. • Feedback from Customers that demonstrates the clear benefits from the Neo4j-based service • Minimal UI supports the demonstrations Achilles 10th September 2017 The Proof of Concept (POC) has been designed to prove the technical and data strategy is effective as part of the full business case and we will report the results with the FBC.. Executing the next generation strategy Business Case SUMMARY Tim James David Swayne Navdeep Panaich Alex Myers Michael Davis Jonah Batambuze 2017 | VERSION 0.4 Objective Measure Progress Data richness: To illustrate that Neo4j can accommodate the richness of the Achilles model (which is currently distributed among multiple systems and technologies) in a single graph • Understandable for both business and technical staff. • Able to support legacy “views” to minimise client migration effort. • Able to support international language requirements • Adaptable to meet new business requirements. Complete Data source: To show that data can be loaded from existing systems • Data brought across different platforms (including V1, Ap2, FPAL, RQM) • All data accessible and searchable. Complete Queries: To show that data can be queried easily • Data can be queried from a dotnet environment. • Data can only be searched, accessed and updated according their rights- user type of person logged in • Simple and complex queries. Ability to drill down on search to refine selection and obtain more detail about supplier and product. • Search results available in Graph and List forms. Complete Performance : To show that the Neo4j-based solution will meet Achilles’s performance and availability objectives • To prove that the service can be run in the cloud. • Support database size of 8-10Tb Target completion 27 th Sept. Supportability: To learn enough about Neo4j so Achilles are confident the POC proves we can deliver a supportable next generation service • Knowledge can be transferred on support capability required. • Neo support is adequate for Achilles needs. Complete Customer: To obtain feedback from Achilles customers on the potential solution and provide customer confidence. • Feedback from Customers that demonstrates the clear benefits from the Neo4j-based service. • Minimal UI supports the demonstrations. Complete
  6. 6. 6 Develop product offerings not bespoke solutions ¡ Data driven architecture that allows content based product with no development ¡ Access to tools and content based upon products subscribed to (auth & auth) ¡ All current questionnaires mapped to the new product set Migration of business from existing platforms to new environment ¡ Repeatable EVTL process to upgrade customers from 26 old to 1 new platform ¡ 90%+ data migration from each legacy product ¡ Transform free text to code based responses wherever possible ¡ No invalid data to be loaded into new platform Robust governance, project discipline and control ¡ Governance in place for stabilisation and continues for Titan ¡ Business ownership for managing change within business functions ¡ Governance and steering set up for 3rd parties ¡ Scrum.org Nexus processes implemented to scale Scrum to the required level Create a robust technical architecture and design ¡ Proven through Proof of Concept exercises ¡ Enterprise Design developed using TOGAF process ¡ Requirements and Design signed off before development commences 1 2 3 4 Key Drivers to Success
  7. 7. 7 Solution Overview © 2018 Achilles Information Limited | Confidential
  8. 8. Product Definition High Level Product Backlog Prioritise IA TA Prod Manager & SME BA IA Redbot Feature Level Product Backlog Requirement Verify Component / Service Design High Level Design PM BA Customer Develop & Fully Test through daily build cycle Development Release of code into Production Release Developer Tester Ops Release Engineer Tester PM Value Stream for Titan The Achilles BA, TA and IA build a Sprint Backlog by selecting items from the Product Backlog and refining them. This happens 2 Sprints ahead of Dev / Test. Members of the allocated Sprint + Core team pick up the refined Sprint Backlog and undertake any required detailed design. This happens 1 Sprint ahead of Dev / Test. Detailed Component / Service Design Detailed Design BA TA DBA Dev Lead Nexus + Sprint Team Planning Sprint Planning Scrum Master Scrum Team The Dev / Test members of the Sprint Team pick up the previously prepared artefacts and Plan to deliver the agreed Sprint Goal to the definition of ‘Done’. 1 2 3 Backlog Refinement Dev / Test Programme Milestone + Features HLD 1. Overarching SAD (HL design, guidelines and approach) + 2. Project SAD (use cases, activity diagrams, sequence diagrams, interface/API catalogue) Referenced/Updated: - EA (Data & Application ADDs) - Logical Data Model System Processes + CRUD Matrices + Features (inc. Acc Crit) + Sketches (HL) + UX/UI Prototypes + Balsamiq Wireframes + High Level Estimate Elapsed time = 10 daysElapsed time = 10 days Elapsed time = 10 days 1 2 3 User Stories + UI Mockups + DTD (detailed activity diagrams, API specifications, class diagrams, physical data model) Accepted User Stories + Sprint Goal + Sprint Backlog Micro Services + API’s + Automated Test Scripts + Ready in Pre-Prod for release Final Test Results (Pre-Prod) + Production Data + Production Code Deliverables Roles
  9. 9. 9 High Level Solution Architecture Peopl e Finan ce Achilles.com (Public Website) (Web chat) Core Titan Question 3rd Party Data Service Product Manager HR Buyer/Supplier Account Manager Finan ce T y k Buyer/ Supplier (Access through to Core Titan UI, or Power BI for MI) T y k T y k T y k T y k T y k T y k Document Repository Amazon SES (Bulk email) T y k T y k Automated Data Validation Services (OCR) Integration: • API messages are sent via HTTP/JSON/XML • Tyk uses the Mongo database • Nservicebus is used for message queues Legend: Product Services Build Project Titan Product Services Project Core Financials and CPM Project HTML 5 MVC .Net/C# Angular JS/Knockout JS HTML 5 MVC .Net/C# Angular JS/Knockout JS Neo4j 3.3.3 Ent SQLServer 2016 sp1 Ent T y k T y k T y k T y k T y k Data Checker (Access through BO UI to Core Titan) Technology/Software Database Master Data Price Product Subscriptio n Oracle Employee Oracle Oracle Finance MI AR AP GL Oracle Answer Product Customer SQLServer Customer Subscriptio n Data Hosting CTL Public Cloud (UK) (Windows 2016 Data Centre) Website Content CTL Dedicated Cloud (UK) (Windows 2016 Data Centre) Billing Engine HR System Finance System CRM System Finance BI Microsoft Datacentre (NL/IE) Sage Datacentre (CA/IE) Adaptive Data Centre NetSuite Datacentre (NL/IE) Zuora Datacentre (DE) Amazon AWS (IE) Google Cloud Compute – “EU-West” Local (in office) Avaya (Telephony) Telephony - 11 different solutions all bespoke to the regional offices Product Manager (PCC UI) Information Architect (PCC UI) Customer Services Transaction Payment Gateway Customer Credit Card Authorisatio n Request Authorisatio n Response T y k Achilles MI SQLServer Data Warehouse CTL Dedicated Cloud (UK) (Windows 2016 Data Centre) D&A Products Power BI CTL Dedicated Cloud (UK) (Windows 2016 Data Centre)Achilles MI User T y k SSIS Customer IdP Azure (Hub) Achilles AD Customer Infrastructure MS Azure CTL Public Cloud (UK) Customer Id Identity Store Achilles User ADFS is used to authenticate all Achilles & customer users T y k CTL Public Cloud (UK) ABBYY Private Cloud Customer ERP Customer Data Centre/Cloud 3rs Party Data Centre/Cloud T y k Billing & Subscription Project
  10. 10. 10 Extract from Data Model
  11. 11. 11 Why graph is better for us Collections-Focused Multi-Model, Documents, Columns & Simple Tables, Joins Neo4j is designed for data relationships NoSQL Relational DBMS Neo4j Graph Platform Connections-Focused Focused on Data Relationships Development Benefits Easy model maintenance Easy query Deployment Benefits Ultra high performance Minimal resource usage Started here Moved here Now here
  12. 12. 12 • Search is faster than our SQL or NOSQL solutions • Target sub 3 second response • Achilles’ business is all about making connections between Buyers and Suppliers • Evolve solution with new requirements over time • Flexible • Multi design solution • Algorithms out of the box • Ability to put data on Nodes or Associations Some tangible benefits © 2017 Achilles Information Limited | Confidential Why graph is better for us • No referential integrity • Different Dev teams can implement the data differently • Ongoing visibility of the design is required • People are used to relational thinking and not graph Risks
  13. 13. 13 Current situation © 2018 Achilles Information Limited | Confidential
  14. 14. 14 § First customer Community is live on new platform § In process of arranging engagement with Neo Innovation Centre re Graph thinking § Hitting aggressive dates is unsurprisingly a challenge § To-date, all release dates have been achieved Release 1 © 2017 Achilles Information Limited | Confidential Current Position
  15. 15. 15 Questions © 2018 Achilles Information Limited | Confidential

×