Striving for Quality in One IT Landscape

Transcription

1 Striving for Quality in One IT Landscape Contribution to EuroSTAR 2011 Wednesday 23 rd November, session W18 By Fabian Scarano 1

2 Agenda Nets: Merge of 3 companies & subsidiaries Corporate strategy & IT principles One IT Landscape Project mandate One IT test process Approach to the Project Test principles Where are we today? 2

3 The Merging Companies - And Subsidiaries that became Nets x

4 Business units key solution areas (BU) Merchant Solutions Cards Payment & Information Services Financial Acquiring esecurity Terminal solutions Transaction acquisition Transaction handling Acquiring of international card schemes Electronic ID schemes ecommerce Acquirer processing & services Clearing and settlement Acquiring of local schemes (DK) e-identity solutions Payment service providing Issuer processing & services Mobile solutions Acquiring of private label schemes Digital signature services Loyalty cards (merchants) ATM solutions & services Invoice services Value-added acquirer services Authentication solutions Pre-paid cards (merchants) Card scheme management Archive and document services Merchant portals Emerging payments Portals and VAS

5 A strategy at corporate level - Our IT strategy is anchored in corporate strategy Corporate Strategy Corporate IT Strategy Corporate focus areas IT Contribution 1 Secure the trusted position - Safe and stable operations Ensure stability & security The northen Europe leader in paymenet, cards and information services 2 3 Improve operational fitness through synergy realisation Deliver on the potential of the three customer domains Reduce costs & realise cost synergies Enable business growth & 4 Go for Nordic break-through positions revenue synergies 5

6 Corporate IT strategy - Structured approach towards Nets business success Inspired by Gartner methodology, our approach is business driven to help Nets to achieve its business goals. Corporate IT Strategy Demand Control Supply Business Context and Success IT Contribution IT Principles IT Governance Enterprise Architecture People Sourcing 6

7 Expected impact Demand: Expected impact - Timeline Projection of the Transformation Programme 1. Secure the trusted position - safe and stable operations 2. Improve operational fitness through synergy realisation 3. Deliver on the potential of the three customer domains 4. Go for Nordic break-through positions

8 Anchored in corporate strategy - Selected by IT Management & Enterprise Architecture Team 8

9 Giving Birth to the New Test Process - Project Mandate 24. IT Nets project model Benefit: n/a Investment: inc. budget Q Q IT Nets development methodologies Benefit: n/a Investment: inc. budget Q Q Establish the basis of the Mandate Objectives Define, develop and implement Nets corporate common test process that: Ensures compliance with the IT transformation programme Supports quality and test of the corporate IT strategy Focuses on business benefits at all stages and Supports Nets core values Where the IT transformation programme defined the following requirements for the test process: Flexible process that fits different needs Must fulfil Nets common requirements to processes Implementation of tools to support the process areas

10 Nets Test Principles Defined to support the IT Principles & be applied by all test initiatives Understand In Nets any test initiative must identify its critical drivers to understand why the testing needs to happen Prioritise AD/AM will prioritise testing to maximise benefit and reduce risk to the business Flexibility Aim to progress at all times, plan flexibility and eliminate dependencies. Be ahead All test initiatives will strive to expose early discovery of flaws Competencies Nets will retain and acquire the necessary resources to get the right infrastructure in place

11 Legacy Test Processes - Two countries and two different methodologies PBS Name: OPUS Based: Waterfall development approach Existing documentation: Templates 100% process coverage process description Test tools deployed and used for all projects BBS Name: U04 Based on: Scrum and Waterfall development approach Existing documentation: Few templates not always used Guidelines to be used by experienced TM Test tools used for many projects; however not aligned for the company and different from the tools used in DK Firmly anchored in the IT culture Inspired in test process improvement

12 OPUS 12

13 U04 Test Model related to U04 -Development Model with test activities Is there a change? Identify TC to be run for the Sprint backlog Choose Execute the Chosen Test Cases (req) Write test cases for the Sprint Understand requirements Identify Test Scenarios Start-up Execution of Sprint Production Test Analysis Test Preparation Test Execution Acceptance Test Test Closure

14 Approach to One IT Test process (1) Basis to start the project Method Scrum Prince2 inspired Sourcing Test Services department owns the project Line manager takes the role of the business stakeholder Reference group reviews the partial development Project board, executive review and acceptance Company s Vice president is the sponsor Communication plan Test Website Test forum Coaching Training sessions Tools Standard office tools Sharepoint to bridge the two-locations gap

15 Approach to One IT Test process (2) Define Project Plan Resource allocation and workload (70,50,20,10,10,10) How to involve the rest of the AD & AM units actively Describe the backlog & play Poker Define Sprints Sprint planning Daily Scrums (twice a week) Sprint review and acceptance Retrospective Implement first cut of the model

16 The New Process 16

17 One IT Test process Backlog Definition Pla yer Process Process Output Purpose Decide test strategy Test strategy To establish an agreement between the Test Manager, Project Manager and Project Owner about how the test assignment will be conducted. Appr oved by Project Deliverables Process description Template for test strategy Good practices? Checklist for test strategy Comment How to demo Sprint starts Sprint stops Estimate Review requirements Accepted and baselined requirements To ensure that the requirements support the business process and include enough information to develop and test according to the business needs Process description Checklist 1 8 Test planning Test plan To describe and reach agreement with the PM and the central stakeholders concerning what is to be tested, when, where and by whom Functional test preparation Test cases/test specification To specify how the functional requirements will be tested, in the case of system and Integration test, whilst the objective in UAT is to specify how the application supports the business needs and processes. Non functional test preparation Test cases/test specification To specify how the non-functional requirements will be tested Prepare test schedule Test schedule To ensure preparation of a detailed list of tasks and the sequential order in which they should be performed. To enhance test plannig in general Preparing environment and data Test environments Test data To ensure suitable environments configuration, generated data and transferred data for the planned tests. Review preparation Preparation phase accepted Ensure functionality coverage, data integrity, understandable texts, apropriate test design and alignment with the objectives of the project Process description Template for test plan. Process description Example of test techniques Process description Example of test techniques Process description Examples Process description Guidelines for data management Process description Checklist Remember to cover all test levels (including acceptance) How test tools can support (ALM & QTP) Reusability of tests Candidate for split How test tools can support (ALM & QTP etc) Reusability of tests In smaller projects, the description of the test environment and the test data can be written in the test plan

18 Thinking behind Backlog Definition Abstraction process that showed tricky, whilst defining the backlog Pla yer Process Process Output Purpose One IT Test process Backlog Definition Automate tests Automated test suite To create and run a test automatically where that will make the testing more efficient Enhance the testware Regression test (prepare and run) Test results (various) including defects described Ensure that the existing functionality works and performs as it did before the change Test report Test status report To inform management and stakeholders of status and risks according to plan. Marks the end of a test level or all test efforts with a recommendation Run integration test Integration test report Assess the status of the solution in integration with it's environment using the plans, specifications and schedules. Approval Approval documents To assess to which extent the acceptance criteria are met Compliance Compliance report Ensure that the solution is compliant with regulatory requirements Appr ove d by Project Deliverables Comment How to demo Sprint starts Sprint stops Estimat ed Good practices Guidelines for automation 5 Good practices Guidelines for regression tests Test (Summary) Report template Good practices Template for test report Good practices Process description Template for acceptance doc Good practices Basis for acceptance Template for compliance report Good practices Regression takes out of preparation phase and develops here 4 5 Describe the variety of acceptance test and procedures Check contract 5 This item depends on the different areas Overlates til ADAM? UTGÅR 3 18

19 One IT Test Process: challenges Describing a sound backlog Working in two different countries and locations Involving all company s stakeholders Processing review from the reference group Anchoring the result throughout Nets Parallel corporate initiatives with direct impact on the test process (i.e. Release Management) Other process development not started (Project Model /Requirements) Common use of the test tool

20 Where are we today?

21 Summary Companies Merge Corporate IT Strategy One IT Landscape One IT Test Process Have a flexible process that can support Scrum and Waterfall methods Project approach and challenges IT Test Principles

22 Contact information 22