curing the agile hangover

28
with Software Craftsmanship

Upload: valtech-uk

Post on 23-Jan-2015

1.382 views

Category:

Technology


4 download

DESCRIPTION

In this talk we Sandro Mancuso and Mashooq Badar (Directors at UBS) discuss their experiences in how they are trying to find the right balance between technical practices and processes. Empowered professional software engineers, well defined testing strategy, process automation, high investment in people development, requirements management and strong emphasis on quality have been the key areas of their focus.

TRANSCRIPT

Page 1: Curing the Agile Hangover

with Software Craftsmanship

Page 2: Curing the Agile Hangover

Requirements Dev Test Release

Page 3: Curing the Agile Hangover

Project Managers / Analysts

Developers Testers

Page 4: Curing the Agile Hangover

Dev Team 1 Dev Team 2 Dev Team 3

Component 1 Component 2 Component 3

Page 5: Curing the Agile Hangover
Page 6: Curing the Agile Hangover

Scrum Master

Developers

QA BA

Product Owner

Page 7: Curing the Agile Hangover

Team 1 Team 2 Team 3

Component 1

Component 2

Component 3

Page 8: Curing the Agile Hangover
Page 9: Curing the Agile Hangover
Page 10: Curing the Agile Hangover

Unreliable Release Process

Requirements not well

understood

Unreliable and costly tests

Inefficient Develop/Debu

g/Deploy cycles

Unstable system Late

discovery of bugs

Long running builds

Mountain of

Technical Debt

Low Moral and

Motivation

Stagnant Skillset

Lack of technical expertise

Page 11: Curing the Agile Hangover
Page 12: Curing the Agile Hangover
Page 13: Curing the Agile Hangover

Bad Quality Software

Poor ROI

Isolated Developers

Us and Them Attitudes

The Hangover

Page 14: Curing the Agile Hangover

Well Crafted Software

Poor ROI

Isolated Developers

Us and Them Attitudes

The Hangover

Page 15: Curing the Agile Hangover

Well Crafted Software

Steadily Add Value

Isolated Developers

Us and Them Attitudes

The Hangover

Page 16: Curing the Agile Hangover

Well Crafted Software

Steadily Add Value

Community of Professionals

Us and Them Attitudes

The Hangover

Page 17: Curing the Agile Hangover

Well Crafted Software Steadily Add Value

Community of Professionals

Productive Partnership

Software

Craftsmanship

Page 18: Curing the Agile Hangover
Page 19: Curing the Agile Hangover

Empowered Professionals

Career paths for

every Role

Role Equality

Low Moral and

Motivation

Lack of technical expertise

Page 20: Curing the Agile Hangover

Unreliable and costly tests

System

Integration

Component Unit

Long running builds

Late discovery of bugs

Page 21: Curing the Agile Hangover

System

Integration

Component

Unit

Page 22: Curing the Agile Hangover

Emphasis on

Quality

Boy Scout Rule

Automated Testing

TDD

Pair Programming

Continuous Integration

Embrace Legacy

Inefficient Develop/Debug/D

eploy cycles

Unstable system

Mountain of

Technical Debt

Page 23: Curing the Agile Hangover

Unreliable Release Process

Unstable system

Late discovery of bugs

Requirements

Dev /Test Release

Page 24: Curing the Agile Hangover

Dev Prod Integration

Zero Downtime Deployment

Continuous Deployment

Process Automation

Continuous Delivery

Page 25: Curing the Agile Hangover

High Investment in People

Coaching and Mentoring

Communities of Practice

External Communities

Hiring Process

Vendor Relationship

Professional Swap

Stagnant Skillset

Low Moral and

Motivation

Page 26: Curing the Agile Hangover

Where we are

Specification By Example

BDD

Code Reviews

Pair Programing

Continuous Integration

Generalizing Specialists

Automated Testing

Continuous Improvement

Testing at the right level

Page 27: Curing the Agile Hangover

Where we want

to be

Regional Mentors

Local Communities

of Practice

Centre of Excellence

UBS wide improvements

Automated Release and Deployment

Zero downtime

Continuous Disaster Recovery Practice

Distributed Source Control

and Social Coding

Simple Applications

Page 28: Curing the Agile Hangover

Sandro Mancuso [email protected] @sandromancuso

Mashooq Badar [email protected]

@mashooq