View
147
Download
0
Embed Size (px)
DESCRIPTION
In 2010 the Danish PBS and the Norwegian BBS companies merged into NETS converging into the leading provider of solution for payments, cards and information within Northern Europe. Each company had its test process defined, established, proved and operational. Denmark worked on a process, called OPUS, based on the waterfall model, classic, thoroughly defined and solid; whilst Norway defined and used their U04 process built on scrum principles, effective, result oriented and consolidated within the company. For a while both processes co-habited in happiness and harmony, developers, system architects, testers and users worked each comfortably with the existing approach from each side of the sea. One day management communicates that Nets will have one single IT-landscape, ergo one test process. At this time the saga of negotiating scrum through the laborious processes required in a waterfall-based organisation starts, whilst negotiating waterfall for scrum is kind of out of question - Not even a single hit in Google. Working on a common goal for defining test in a scrum approach and a waterfall model without getting stuck between departmental snags was an arduous task and demanded agile undertaking, my apologies for the epigram. The test team first priority is striving for quality, whichever path was taken. So this story does not finish with the test teams experiencing conflicts, management subjective or biased decisions and making fit together somehow the two processes. The main focus was directed towards quality full integrated in the project lifecycle, no matter the approach. At this point testers, business, process people, IT architect and developers had worked in partnership to achieve the “One IT-landscape” process and ensure quality in every phase: Squeezing two antagonist approaches into one single process, collaboration to achieve a common project lifecycle will set the basis for this presentation and further discussion.
Citation preview
Striving for Quality in One IT Landscape
1
Contribution to EuroSTAR 2011 Wednesday 23rd November , session W18
By Fabian Scarano
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?
x
- And Subsidiaries that became NetsThe Merging Companies
Cards Payment & Information Services
Financial Acquiring eSecurity
Business units’ key solution areas (BU)
Terminal solutions Transaction handling Acquiring of inter-national card schemes Electronic ID schemes
eCommerce Clearing and settlement Acquiring of local schemes (DK) e-identity solutions
Payment service providing Mobile solutions Acquiring of private
label schemesDigital signature
services
Loyalty cards (merchants) Invoice services Value-added
acquirer services Authentication
solutions
Pre-paid cards (merchants)
Merchant portals
Archive and documentservices
Portals and VAS
Merchant Solutions
Transaction acquisition
Acquirer processing & services
Issuer processing& services
ATM solutions & services
Card scheme management
Emerging payments
5
Corporate Strategy
Corporate Strategy
Corporate IT Strategy
Corporate IT Strategy
Ensure stability & security
Ensure stability & security
Reduce costs &realise cost synergies
Reduce costs &realise cost synergies
Enable business growth &
revenue synergies
Enable business growth &
revenue synergies
IT ContributionCorporate focus areas
A strategy at corporate level- Our IT strategy is anchored in corporate strategy
The northen Europe leader in paymenet, cards and information
services
1
2
4
3
Secure the trusted position- Safe and stable operations
Improve operational fitness through synergy realisation
Deliver on the potential of the three customer domains
Go for Nordic break-through positions
6
Corporate IT Strategy Corporate IT Strategy
• Business Context and Success
• IT Contribution
• IT Principles
• IT Governance
• Enterprise Architecture
• People
• Sourcing
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.
7
Demand: Expected impact
1. Secure the trusted position - safe and stable operations
3. Deliver on the potential of the three customer domains
2. Improve operational fitness through synergy realisation
2011 2012 2013 2014
Expected impact
4. Go for Nordic break-through positions
- Timeline Projection of the Transformation Programme
8
Anchored in corporate strategy- Selected by IT Management & Enterprise Architecture Team
Giving Birth to the New Test Process- Project Mandate
Establish the basis of the Mandate
Establish the basis of the Mandate
30. IT – Nets development methodologiesBenefit: n/aInvestment: inc. budgetQ3 2010 – Q4 2011
24. IT – Nets project modelBenefit: n/aInvestment: inc. budgetQ3 2010 – Q2 2011
24. IT – Nets project modelBenefit: n/aInvestment: inc. budgetQ3 2010 – Q2 2011
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
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
UnderstandIn Nets any test initiative must
identify its critical drivers to
understand why the testing needs
to happen
UnderstandIn Nets any test initiative must
identify its critical drivers to
understand why the testing needs
to happen
PrioritiseAD/AM will
prioritise testing to maximise benefit and
reduce risk to the business
PrioritiseAD/AM will
prioritise testing to maximise benefit and
reduce risk to the business
Nets’ Test Principles – Defined to support the IT Principles & be applied by all test initiatives
FlexibilityAim to progress at
all times, plan flexibility and
eliminate dependencies.
FlexibilityAim to progress at
all times, plan flexibility and
eliminate dependencies.
Be ahead All test initiatives
will strive to expose early
discovery of flaws
Be ahead All test initiatives
will strive to expose early
discovery of flaws
Competencie
sNets will retain and acquire the
necessary resources to get
the right infrastructure in
place
Competencie
sNets will retain and acquire the
necessary resources to get
the right infrastructure in
place
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
• Firmly anchored in the IT culture
PBS
• Name: OPUS
• Based: Waterfall development approach
• Existing documentation: Templates 100% process coverage process description
• Test tools deployed and used for all projects
• Firmly anchored in the IT culture
12
OPUS
U04
Identify Test Scenarios
Write test cases for the
Sprint
Identify TC to be run for the Sprint backlog
Is there a change?
Execute the Chosen Test Cases (req)
Test Analysis Test Preparation
Test Execution
Acceptance Test Test Closure
Test Model related to U04 -Development Model with test activities
Understand requirements
Start-up Execution of Sprint Production
Choose
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
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
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
• 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
17
One IT Test process Backlog Definition
Player
Process Process Output PurposeApproved
by
Project Deliverables
CommentHow to demo
Sprint starts
Sprint stops
Estimate
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.
Process descriptionTemplate for test strategyGood practices?Checklist for test strategy
1 8Review requirements Accepted and baselined
requirementsTo ensure that the requirements support the business process and include enough information to develop and test according to the business needs
Process description Checklist
2 3Test 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
Process descriptionTemplate for test plan.
1 5Functional 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.
Process description Example of test techniques
Remember to cover all test levels (including acceptance)How test tools can support (ALM & QTP)Reusability of testsCandidate for split
3 13Non functional test preparation Test cases/test specification To specify how the non-functional requirements will be
testedProcess description Example of test techniques
How test tools can support (ALM & QTP etc)Reusability of tests
3 13Prepare 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
Process descriptionExamples
3 2Preparing environment and data Test environments
Test dataTo ensure suitable environments configuration, generated data and transferred data for the planned tests.
Process descriptionGuidelines for data management
In smaller projects, the description of the test environment and the test data can be written in the test plan
4 8Review preparation Preparation phase accepted Ensure functionality coverage, data integrity,
understandable texts, apropriate test design and alignment with the objectives of the project
Process descriptionChecklist
4 3
18
One IT Test process Backlog Definition
Player
Process Process Output PurposeApproved by
Project Deliverables
CommentHow to demo
Sprint starts
Sprint stops
Estimated
Thinking behind Backlog Definition – Abstraction process that showed “tricky”, whilst defining the backlog
Automate tests Automated test suite To create and run a test automatically where that will make the testing more efficientEnhance the testware
Good practicesGuidelines for automation 5
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
Good practicesGuidelines for regression tests
Regression takes out of preparation phase and develops here 4 5
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
Test (Summary) Report template Good practices
3Run integration test Integration test report Assess the status of the solution in integration with it's
environment using the plans, specifications and schedules.Template for test reportGood practices
Approval Approval documents To assess to which extent the acceptance criteria are met
Process descriptionTemplate for acceptance docGood practicesBasis for acceptance
Describe the variety of acceptance test and proceduresCheck contract 5
Compliance Compliance report Ensure that the solution is compliant with regulatory requirements
Template for compliance reportGood practices
This item depends on the different areas Overlates til ADAM?UTGÅR
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
• 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
Where are we today?
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
• 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