A Short Intro

2

Nordea was created through a string of mergers

Pre-70

1970’s

1980’s

1990’s

2000’s

300 banks

80 banks

30 banks

4 banks

1 Nordea

3

Strong customer-orientated values and culture

Foundation: Profit orientation and prudent cost, risk and capital management

Great customer experiences It’s all about people One Nordea team

A Great European bank,

acknowledged for its people, creating superior

value for customers and shareholders

Nordea is the largest financial services group in the Nordic and Baltic sea region

4

11 million customers- 8 home markets- Approx. 10 million personal customers- 520 000 corporate customers, incl. Nordic Top 500

Distribution power- Approx. 800 locations in total- Approx. 7 million Netbank customers- Approx. 1.4 million mobile users

Financial strength- EUR 10.0bn in full year income (2013)

- EUR 637bn of assets (Q2 2014)

- EUR 28.8bn in equity capital (Q2 2014)

- AA credit rating- Core Equity Tier 1 capital ratio of 15.2% (Q2 2014)

EUR ~41.7bn in market cap- One of the largest Nordic corporations- A top-10 European retail bank

Nordea = Nordic ideas

Our organisation

QA,Methods & Development Tools

Ulriqa Söderström

Methods team Development toolsUlriqa Söderström

Requirements

TSCoESuvendu Mishra

5 •

Bussiness perspective of the tools team

• Focus on Continuous Delivery related process maturity

• Centralised support on tools and process - Administration and Training

• Effective use of best practices across different functional units

• Reduction in hardware, license, maintenance and support cost

• Simplification and standardization of process across Nordea

• People mobility across different units and reduce the process related training overheads

6 •

Nordea Tool Target Picture (TTP)

Nordea IT Journey

Previous Development Environment

Business Modelling

System Architect

Requirements

RequisitePro

Rational Software Architect

Analysis and Design

Rational SoftwareArchitect

Oracle BPM

Test

HP Quality Center

HP QuickTest Professional

Deployment

Deployment Management

Tool

Maven

Project management

Change- & Configuration Management

Environment

Implementation

XML Thunder

Eclipse IDE

ClearCase – ClearQuest – Rochade

PSDM – HyperSnap – Beyond Compare – XMLSpy – Oracle Enterprise Repository

MS Project

Not up to date

toolsUsers find

the tools old

Users installother tools

they like better

Too muchadministration

Lack of integration

Not web based

Doesn’tsupport

agile

Hightraining

cost

Difficult to customise

Expensive

Highlearning curve

Platform compatibility

8 •

Phase 1 (2013 release)

… in comparison of the tools we supported before TTP phase 1:

• Create your own repository

• Support for code review

• Traceability

• Better integration

• Improved performance

• Better productivity

• Collaboration

9 •

Jira for Support

< Q3 2013 (Outlook/Phone) • 2 mailboxes• 10 team members• 10+ tools

> Q3 2013 (Jira)• 1 mailbox (Jira mail handler)• 20 team members (10 in India)• 10+ tools

- No development, only maintenance- Difficult to keep good support using

emails- Emails tend to get lost or forgotten

+ Support process enforced by Jira+ More time for development+ Faster response time on support+ Eaiser to follow up on issues+ Transparency

10 •

Where we would like to go (Our Vision)

Business Modelling

Mega Suite

Requirements

New tool is being evaluated

Analysis and Design

New tool will be evaluated

Oracle BPM

Deployment

DeployIT

Bamboo

Nexus/Artifactory

Project management

Change- & Configuration Management

Environment

Implementation

XML Thunder

Eclipse IDE

Maven

Jira – Git – Stash

HyperSnap – Beyond Compare – XMLSpy - FishEye

MS Project – Clarity – Jira - Confluence

Test

Quality Center

SoapUI Pro

Semmle

New tools will be evaluated

Decided and used This phase (phase 2) New Tools to be decided

11 •

What did we look into in TTP Phase 2

• Service Testing

• SoapUI

• SoapUI Pro

• Apache JMeter

• HP Service Testing

• Unit Testing

• Junit

• TestNG

• Mockito

• Easymock

• DBFit

• DBunit

• Source Code Analysis

• Coverity

• Sonar

• Semmle

• Continuous Integration

• Atlassian Bamboo

• Jenkins

• TeamCity

Interviews Testing Pilots

Survey to approx. 1650 users – 40 % response rate • Gave a list of tools to look into

12 •

Tools Target Picture

13 •

Atlassian tools list

• Jira 6.1.3

Clone+, Email This issue, JAM, Jira Agile, Timesheet Reports and Gadgets, Links Explorer, Charting, Custom Content, Suite Utilities, Jira Toolkit, Unique Regex Custom field

• Confluence 5.3.1

bitvoodoo Registration, Confluence Questions, Gliffy, Knowledge Base Survey, PocketQuery, RefinedWiki Original Theme, RefinedWiki UI Toolkit, Viewtracker and Visibility

• Stash 2.12.3

External hooks, Jira hooks for Stash, Repository mirror, Auto Unapprove, Protect unmerged Branch hook, Workzone

• Bamboo 5.6.0DeployIT connection

• FishEye 3.3.1

14 •

Confluence

15 •

Jira

A common way of working

Nordea Simple Workflow Scheme(New, In Progress, Closed, Postponed)Pick this workflow if you are unsertain what you need. its the simpliest of the workflows and doesnt contain any control states.

Nordea Basic Workflow Scheme(New, In Progress, Resolved, Closed, Postponed, Rejected, Under Research)Pick this workflow if you need more control of the state of different issues. Use Resolved state as your testing stage.

Nordea Advanced Workflow Scheme(New, Approved, In Progress, Resolved, Closed, Postponed, Rejected, Under Research)Pick this workflow if you need a control state to approve or reject issues. This suites teams that have CCB meetings to approve/reject new issues.

Agile Simplified Workflow Scheme(ToDo, In Progress, Done)Pick this workflow if you are a agile team and want the flexibillity to make your own agile workflow. In the settings of your agile board you will be able to add, remove and change the different steps as your team develops. Very agile indeed

16 •

Bumps on the road

• SSL – different from tool to tool

• LDAP – different setup in each tool

• Not easy to get pilot projects

17 •

What is left

Remedy

• TTP Phase 3• Requirement and modeling tools• Continue to develop CI and automated test

• Continuously improving the processes and competences• Integration with other SDLC tools

18 •

Thank you!