Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Improving the developer workflow


Published on

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.

Published in: Technology
  • Login to see the comments

  • Be the first to like this

Improving the developer workflow

  1. 1. Improving the Developer Workflow<br />Dennis Doomen | Principal Consultant | Aviva Solutions<br />
  2. 2. A typicalday at the office…<br />
  3. 3. The product owner is upset…<br />
  4. 4. Improving the Developer Workflow<br />Dennis Doomen | Principal Consultant | Aviva Solutions<br />
  5. 5. DEMO<br />User Stories & Product backlog<br />
  6. 6. What you saw<br />Product Backlog for tracking requirements<br />“As role I want what because why”<br />Both technical and functional<br />Storyotypes for scoping<br />
  7. 7. The architect is accountable…<br />
  8. 8. Architecture<br />Views (XAML + C#)<br />Shell<br />View Models<br />Coroutines<br />Application Controller<br />Application Services<br />Service Agent<br />Bootstrapper<br />DTOs<br />Commands<br />Enterprise Library 5<br />Query Service<br />Command Service<br />Domain Entities<br />Command Handlers<br />Service Agents<br />Unit of Work<br />Repositories<br />Database<br />
  9. 9. DEMO<br />Code Metrics & Static Analysis<br />
  10. 10. What you saw<br />Use Code Metrics with Excel<br />Choose Code Analysis Rule Sets<br />Consider the Definition of Done<br />Check out NDepend<br />
  11. 11. The developer has to fix it…<br />
  12. 12. DEMO<br />Refactoring & Test drivendevelopment<br />
  13. 13. What you saw<br />Refactoring is essential<br />OneNote to keep track of ToDos<br />Gated Check-in<br />Unit Tests to verify regression<br />
  14. 14. His collegae has to review it…<br />
  15. 15. DEMO<br />Peer Reviews<br />
  16. 16. What you saw<br />Reviews are essential<br />OneNote is a great tool<br />Visual Studio needs a built-in review feature<br />
  17. 17. Takeaways<br />Silver bullets don’t exist<br />Adapt tools to your culture<br />Consider the butterfly effect<br />
  18. 18. Advicefrom the trenches<br />AvoidNotes C.P.<br />Avoid Unit Test C.P.<br />Check-in veryoften<br />Teams of 3-8 developers<br />Treatwarnings as errors<br />
  19. 19. Contact Me<br /><br />@ddoomen<br /><br />
  20. 20. Home<br />User Stories Applied – Mike Cohn<br />XP/Scrum from the Trenches – Henrik Kniberg<br />Growing Object-Oriented Software Guided by Tests – Freeman & Pryce<br />Clean Code – Robert C. Martin<br />C# 3.0/4.0 Coding Guidelines<br />Silverlight Cookbook<br />Fluent Assertions<br />