improving the developer workflow
DESCRIPTION
In my part I'll show you the typical flow of tasks that I or my team members follow during our day-to-day work as consultants. I'll show you how to apply code reviews, code metrics, static code analysis, refactoring and maybe even some some TDD. All of that combined with the power of Team Foundation Server 2010 to stream-line those activities.TRANSCRIPT
Improving the Developer Workflow
Dennis Doomen | Principal Consultant | Aviva Solutions
A typical day at the office…
The product owner is upset…
Improving the Developer Workflow
Dennis Doomen | Principal Consultant | Aviva Solutions
USER STORIES & PRODUCT BACKLOG
DEMO
What you saw• Product Backlog for
tracking requirements• “As role I want what
because why”• Both technical and
functional• Storyotypes for scoping
The architect is accountable…
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
CODE METRICS & STATIC ANALYSIS
DEMO
What you saw• Use Code Metrics with
Excel• Choose Code Analysis
Rule Sets• Consider the Definition of
Done• Check out NDepend
The developer has to fix it…
REFACTORING & TEST DRIVEN DEVELOPMENT
DEMO
What you saw• Refactoring is essential• OneNote to keep track of
ToDos• Gated Check-in• Unit Tests to verify regression
His collegae has to review it…
PEER REVIEWSDEMO
What you saw• Reviews are essential• OneNote is a great tool• Visual Studio needs a built-
in review feature
Takeaways• Silver bullets don’t exist• Adapt tools to your
culture• Consider the butterfly
effect
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
Contact Me• dennis.doomen@avivasolutions.
nl• @ddoomen• www.dennisdoomen.net
Home• User Stories Applied – Mike Cohn• XP/Scrum from the Trenches – Henrik Knib
erg• Growing Object-Oriented Software Guided
by Tests – Freeman & Pryce• Clean Code – Robert C. Martin• C# 3.0/4.0 Coding Guidelines • Silverlight Cookbook• Fluent Assertions