Colin Bowern TAKING THE BEST-IN-CLASS ROAD FOR ALM TOOLING

Size: px

Start display at page:

Download "Colin Bowern TAKING THE BEST-IN-CLASS ROAD FOR ALM TOOLING"

Megan Hart
5 years ago
Views:

1 Colin Bowern TAKING THE BEST-IN-CLASS ROAD FOR ALM TOOLING

2 TOOLS ARE A MEANS TO AN END.

3 FRICTION REPLACE

4 AGILE ALM = PEOPLE FIRST, TOOLS SECOND

5 ALM Practices Define Portfolio View Product Vision Product Backlog Sprint Progress Knowledge Sharing Develop Collaborative Coding Continuous Integration Code Analysis and Review Testing Release Artifact Management Packaging Deployment Environment Management Operate Availability Events Performance User Feedback

6 Maturing ALM Patterns & Practices Collaborate If you cannot communicate without tools, tools will not help Integrate Ensure successful hand-offs, feedback actioned through out delivery Automate Remove need to intervene where ever possible, especially on repetitive tasks Improve Regularly inspect for opportunities to do it better, faster, cheaper

7 It s About Reducing Cycle Time Monitor Define Release Develop

9 Building Your ALM Stack Source Code Repository Build Continuous Integration Code Analysis Testing Packaging Artifact Repository Deployment Configuration Management Monitoring Release Planning

10 Integrated vs. Best-in-Class Tool Chains Balance of magic and control depends on comfort No one-size-fits-all stack that will work for every team Can use a bit of both too! Magic Unicorns Control

11 My View of Integrated Solutions

12 Strategies: Strengths + Weaknesses Integrated Up sides Down sides Best-in-Class Up sides Down sides

13 Integrated Offerings

14 LICESNING BEST-IN-CLASS MAY BE MORE EXPENSIVE

15 Best-in-Class Offerings Source Code Repositories Git GitHub Enterprise, GitBlit, GitStack, Bonobo Mercurial Kiln, BitBucket Subversion VisualSVN, CollaNet SVN Perforce Plastic SCM Continuous Integration TeamCity Jenkins Hudson Bamboo BuildMaster ParaBuild Go

16 Best-in-Class Offerings Build MSBuild PSake Rake FinalBuilder Incredibuild NAnt Code Analysis Resharper Inspetions Tools Sonar Qube Coverty Code Advisor CodeIt.Right McCabe

17 Best-in-Class Offerings Testing NUnit XUnit SpecFlow Selenium WaitN Telerik Test Studio TestComplete Ranorex Packaging Web Deploy NuGet Windows Installer XML Advanced Installer InstallAware InnoSetup Nullsoft Scriptable Install System DeployMaster

18 Best-in-Class Offerings Artifact Repository ProGet MyGet Apache Archiva jfrog Artifactory Sonar Nexus Deployment Octopus Deploy Red Gate Deployment Manager Nolio Urban Code udeploy

19 Best-in-Class Offerings Configuration Management Puppet Chef Salt CFEgnine Vagrant Monitoring New Relic Mindscape RayGun Telerik Eqatec Splunk AppDynamics

20 Best-in-Class Offerings Release Planning Physical Post-it Notes TargetProcess FogBuz PMRobot Trello LeanKit Kanbanery Silver Catalyst AgileZen Agielfant IceScrum Easybacklog

21 Establish Design Principles for Your Tool Chain Clear roles and boundaries for tools Expectations for team covering development to release Identify where integration between tools can add value Example 1. Source control contains everything required to check out, build and run Where it doesn t make sense the README at the root lists the pre-requisites 2. Use tools to solve one problem TeamCity is our orchestration engine, it knows how to coordinate but doesn t care about the details PSAKE knows about the details, but doesn t dictate how orchestration occurs 3. Build once and only once, everything else should be based on those binaries We only build Release configuration builds and we ship debug symbols with our packages for better stack traces in error reports 4. Only packages from the artifact repository are deployed to production 5. Infrastructure should be treated like garbage

22 Sample Stack BitBucket (Git) PSAKE FXCop Resharper TeamCity XUnit Web Deploy TeamCity Octopus Deploy Azure Web Sites New Relic TargetProcess

23 Source Code Repository Build Continuous Integration Code Analysis Testing Packaging Artifact Repository Deployment Configuration Management Monitoring Release Planning SAMPLE STACK IN ACTION

24 Summary Choose the right tools for right now, not just because they are the corporate standard Replace low value implementations of functionality in your integrated stack As the team improves, explore how new tools can improve workflow Don t confine your research to traditional vendors or even the same eco-system

JetBrains TeamCity Comparison

JetBrains TeamCity Comparison TeamCity is a continuous integration and continuous delivery server developed by JetBrains. It provides out-of-the-box continuous unit testing, code quality analysis, and