Transcript
Page 1: Improving the developer workflow

Improving the Developer Workflow

Dennis Doomen | Principal Consultant | Aviva Solutions

Page 2: Improving the developer workflow

A typical day at the office…

Page 3: Improving the developer workflow

The product owner is upset…

Page 4: Improving the developer workflow

Improving the Developer Workflow

Dennis Doomen | Principal Consultant | Aviva Solutions

Page 5: Improving the developer workflow

USER STORIES & PRODUCT BACKLOG

DEMO

Page 6: Improving the developer workflow

What you saw• Product Backlog for

tracking requirements• “As role I want what

because why”• Both technical and

functional• Storyotypes for scoping

Page 7: Improving the developer workflow

The architect is accountable…

Page 8: Improving the developer workflow

Query Service

Service Agent

DTOs

View Models

Views (XAML + C#)

Domain Entities

Repositories

Command Handlers

Database

Unit of Work Service Agents

Shell

Bootstrapper

Coroutines

Enterprise Library 5

Application Controller

Command Service

Commands

Application Services

Architecture

Page 9: Improving the developer workflow

CODE METRICS & STATIC ANALYSIS

DEMO

Page 10: Improving the developer workflow

What you saw• Use Code Metrics with

Excel• Choose Code Analysis

Rule Sets• Consider the Definition of

Done• Check out NDepend

Page 11: Improving the developer workflow

The developer has to fix it…

Page 12: Improving the developer workflow

REFACTORING & TEST DRIVEN DEVELOPMENT

DEMO

Page 13: Improving the developer workflow

What you saw• Refactoring is essential• OneNote to keep track of

ToDos• Gated Check-in• Unit Tests to verify regression

Page 14: Improving the developer workflow

His collegae has to review it…

Page 15: Improving the developer workflow

PEER REVIEWSDEMO

Page 16: Improving the developer workflow

What you saw• Reviews are essential• OneNote is a great tool• Visual Studio needs a built-

in review feature

Page 17: Improving the developer workflow

Takeaways• Silver bullets don’t exist• Adapt tools to your

culture• Consider the butterfly

effect

Page 18: Improving the developer workflow

Advice from the trenches• Avoid Notes C.P.• Avoid Unit Test C.P.• Check-in very often• Teams of 3-8 developers• Treat warnings as errors

Page 19: Improving the developer workflow

Contact Me• dennis.doomen@avivasolutions.

nl• @ddoomen• www.dennisdoomen.net

Page 21: Improving the developer workflow

Top Related