CollabNet Houston Workshop Live Enterpise agility_11.12.14

1 Copyright ©2014 CollabNet, Inc. All Rights Reserved.
- Enabling Agility and Governance
- Agile Delivery AND DevOps
Streamlining the Delivery Pipeline—from Agile Planning through
Continuous Delivery and Deployment
Dennis Nevins Steve Grossman Brian Dawson
Sales Manager Technical Account Mgr. Guest Speaker
dnevins@collab.net sgrossman@collab.net bdawson@collab.net
720-438-7218 214.690.0236
Logo CollabNet Confidential
CollabNet Solutions for ….

CollabNet Live Workshop Series - 2014
Achieving Enterprise Agility,
Continuous Integration, Continuous Delivery, and DevOps
Dennis Nevins Steve Grossman Brian Dawson
Sales Manager Technical Account Mgr. Guest Speaker
dnevins@collab.net sgrossman@collab.net bdawson@collab.net
720-438-7218 214.690.0236

About our Sponsors
CollabNet is a leading provider of Enterprise Cloud Development and Agile ALM products and
services for software-driven organizations. With more than 10,000 global customers, the company
provides a suite of platforms and services to address three major trends disrupting the software
industry: Agile, DevOps and hybrid cloud development. The CollabNet TeamForge® ALM platform
can be deployed on-premise or in the cloud. CollabNet complements its technical offerings with
industry leading consulting and training services for Agile and cloud development
transformations. Many CollabNet customers improve productivity by as much as 70 percent, while
reducing costs by 80 percent.
For more information, please visit www.collab.net.
Carahsoft Technology Corp. is the trusted Government IT solutions provider. As a top-ranked
GSA Schedule Contract holder, Carahsoft serves as the master government aggregator for
many of its best-of-breed vendors, supporting an extensive ecosystem of software
manufacturers, resellers, and consulting partners committed to helping government
agencies select and implement the best solution at the best possible value. Carahsoft is
consistently recognized by its partners as a top revenue producer, and is listed annually
among the industry's fastest growing firms by VAR500, CRN, Inc., Washington Technology,
Washington Business Journal, and SmartCEO.
For more information, please visit www.carahsoft.com.

• 9:00 – 9:30 PM : Breakfast, Networking
• 9:30 – 10:00 PM : Kick-off, Post-it Goals
• 10:00 – 10:30 PM : Enterprise Agility; Upstream & Downstream Agile
• 10:30 – 11:00 PM : Continuous Integration and Continuous Delivery (CI/CD)
• 11:00 – 11:20 PM : Case Study Exercise - Deutche Post
• 11:20 – 11:30 PM : Solution Example
• 11:30 – 11:45 PM : DevOps
• 11:45 – 12:00 PM : Feedback Loops & Enterprise Metrics
• 12:00 PM : Conclusion/Survey Form
DC DevOps Workshop Agenda

1st Cloud-Based ALM
Agile Transformations
Open Agile
ALM
1999 2005 2014
Apache / Subversion
2010
Market Leader
• Gartner MQ Leader –
– Federated ALM Solutions
• ALM, SCM, Cloud, Agile
• Enterprise Agility Experts
Legacy and Leadership
• Creator of Subversion (SVN)
• Open Source Federation
• First Cloud-based ALM solution
Scalable and Secure
• 10,000 Customers
• Impressive Client list
• Six Million Users Worldwide
• DOD Secure

Presenter Introduction – Brian Dawson
• 19 years working in and across software and IT disciplines
• Experience with 100’s of developers and development teams
• Focused on distributing knowledge and solving unique problems within software development
organizations
• Key Client Accounts include;
At CollabNet, I am an Enterprise Transformation Manager. I work with large and small software development
organizations to improve the Application Lifecycle Management (ALM) process through the use of TeamForge,
OSS, and best practices.
Prior to CollabNet, I spent 12 years in software development. Much of that was spent at Sony Computer
Entertainment including work as the Director of Tools and Technology, overseeing the development and
deployment of a worldwide collaboration portal, and managing tools and process adoption and
standardization.

• Goals
– Understand Enterprise Agility
– Understanding of common solutions for Enterprise Agile Transformation
– Lessons learned in applying CI, CD and DevOps in the enterprise
– Leave better informed
• Format
– Interactive workshop
– Meetup-style
– Split into 4 topics:
• Problem/Solution review
• Moderated group discussion
Workshop Goals & Format

9 Copyright ©2014 CollabNet, Inc. All Rights Reserved.9 Copyright ©2014 CollabNet, Inc. All Rights Reserved.
Topic #1
Enterprise Agility, Upstream and Downstream Agile

Enterprise Agile Transformation
“Most firms are experiencing rapid
and fundamental change in both
business and technology. How do you
cope? You must transform your
software delivery approach.”

13%†32%*
Source: February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report
*Do standup, burndown/burnup, and
short iterations; product owner; and
constant feedback.
†Do upstream plus continuous
integration, continuous delivery, and
test-driven development.
Agile
Downstream
Agile development and delivery
CI, CD, DevOps
Agile
Upstream
Agile planning and project execution
SCRUM, XP, Kanban, etc

• Agile development and delivery are creating faster cycle times
• Proliferation of un-connected teams, processes and tools are:
– Limiting agility & scale
– Blocking visibility & governance
– Tying up resources better spent on delivering value & innovation
The Challenges & Issues

Achieving Enterprise Agility
Agile Planning
Continuous Integration
Continuous Delivery
DevOps
Value
Integration &
Collaboration

Leverage common platform as “hub”
• Connect multiple heterogeneous tools and process
Centralize source (and binary) IP
• Enables governance while reducing team overhead
Establish traceability early and consistently
• Integrate requirements/stories and work-item tracking to SCM
• Require associations between source code (or infrastructure) changes and
originating work
Establish “baseline” practices across teams
• Enable flexibility of Upstream process with repeatability of Downstream
process
Connect Agile Upstream to Agile Downstream

• What obstacles have you faced in adopting Agile planning practices?
• Do you support mixed methodologies (Scrum, Waterfall, Hybrid) within a
common tool chain (shared tracking and SCM)? How?
• How do you ensure Upstream (business) decisions are reflected in Downstream
(code and infrastructure) changes?
• Have you standardized on:
– Planning and work-item management?
– Version control?
• How? Why not?
• Have you scaled this process across your organization in a repeatable manner?
Group Discussion

Topic #2
Continuous Integration and Continuous Delivery

Has this happened to you?

CI and CD – Has this happened to

What is CI?
“Continuous Integration is a software development practice where members of a team
integrate their work frequently, usually each person integrates at least daily - leading to
multiple integrations per day. Each integration is verified by an automated build (including
test) to detect integration errors as quickly as possible…this approach leads to
significantly reduced integration problems and allows a team to develop cohesive
software more rapidly.”
As defined in 2006…
“Today, meaningful integration happens less in source control and more
frequently in a runtime environment… if you want to quickly verify that the work
of two developers is not conflicting, you need to run API tests, as well as some
functional tests scenarios. That means bringing the various services into an
integration test environment, and validating runtime functionality at a pace
similar to the classic CI build loop ”
]
Continuous Integration and todays technologies…

What is CI?

Why CI?
• Automation of repetitive manual processes
• More time focusing on adding value
• No need to wait hours, days, months to know how check-in affects the
build
• Constant availability for the build for testing, demo or release
• Shared visibility
• Increased team productivity
• Higher quality software, faster!

• Continuous Delivery extends the CI process from build to include test and
deploy phases
– Release ready, deployable software
– Ensure fluid coordination and communication between stakeholders
– Handle need for governance
Continuous Integration vs. Continuous Delivery
Continuous
Delivery
Plan
Define
Assign
Deploy
Maintain
Code Test
Commit Integrate
Test
Promote
ReleaseContinuous
Integration
“Continuous delivery of software
needs processes that encompass the
entire delivery process..”
Monitor

Establish central build platform and/or eco-system
• Flexible support for different teams needs
• Support easy on-boarding
– Managed or self-service
Naturally connect the build process to the common platform
• Supports traceability, visibility and governance
Manage binaries tightly
• Reduce risk
• Promote reuse
Invest in quality
• Unit testing
• Static code analysis
• Automated testing (UAT, Load, Smoke etc)
Enterprise CI and CD Practices

Source CodeBuild scripts
SCM
Binary Artifact Management
Unknown Input
Results in Unknown Output
Build
Product
Build
Product
Published
Exec
Deployment QA
Internal
Libraries
Project and
Sub-projects
3rd Party
Libraries
Binaries
Downstream Dependents
?
Project A
Build Process
Project B
Build Process
? ?
?
?
? ? ?

SCM
Managed Inputs
Result in Trusted Outputs
Build
Product
Project B
Build Process
Build
Product
Published
Exec
Deployment QA
Project A
Build Process
Internal
Libraries
Project and
Sub-projects
3rd Party
Libraries
Binary Artifact Repo (Nexus)
Binary Artifact Repo
(Nexus)

Patterns and Anti-Patterns
Action Type Comments
Build
Threshold
Pattern Fail a build when a project rule is violated. e.g. Coding Violations, Test Failures
Anti
Pattern
Scheduled Builds , Manual Code Review
Continuous
Feedback
Pattern Send automated feedback – Dashboards, Info Radiator
Anti
Pattern
Notifications not sent, ignored , CI Systems Spams
Automated
Tests
Pattern Automate the verification and validation of software to include unit, component, capacity,
functional, and deployment tests
Anti
Pattern
Manual testing of units, components, deployment, and other types of tests

– Who is leveraging Continuous Integration today?
• Just started?
• Mature implementation?
• Across the organization?
– What benefits have you recognized?
– What obstacles have you faced?
– Can your developers deploy to a production like environment?
– Have you scaled this process across your organization in a repeatable
manner?
Group Discussion

Break and Open Discussion
10 Minutes

Case Study Exercise
Review and Discuss

Implementation Example

CI/CD Implementation Example
① Ops, DB, and App Developers implement user stories from TeamForge and commit changes to SVN/GIT, the
user stories and code changes are associated.
② A CI build job runs, executing unit tests, code analysis, etc, a TeamForge Build Artifact is created, change notes
are generated and associated.
③ Every 15 minutes or on-demand a snapshot build is published to the Nexus Repository. The snapshot build is
deployed to the Development servers by Automic.
④ The Project Manager reviews the Change Notes and Release Folder in TeamForge and using the data decides to
promote a build as a Release Candidate, she creates a Release Manager Artifact (RMA) and set it to “Ready to
Release.”
⑤ A Jenkins Release Candidate Promotion job runs executing the application builds, publishing the artifacts to
Nexus and populating Automic with the release meta-data.
⑥ An Automic package references the Nexus release holding the release candidate to be deployed.
⑦ Operations, QA and/or Change Management promote and deploy the release candidate using Automic
Workflows.
⑧ At each promotion and deployment step the TeamForge Release Artifact is updated from Automic and team
members receive email notifications.
⑨ The Release Dashboard in TeamForge provides up-to-date pipeline Activity Reports and Release Notes.
⑩ Dev, QA, Ops and Management can view the Release Dashboard inTeamForge to track acitivy and make
informed decisions.

Topic #3
Enterprise DevOps

DevOps is an set of emerging principles…
• Leveraging collaboration, tools integrations, automation and the cloud
• Advocating process standardizations across development teams and IT operations
• Bridging gaps between development and delivery
DevOps optimizes processes ….
…to increase business value.
• Continuous Development
• Continuous Integration
• Continuous Delivery/Deployment
• Continuous Monitoring/Management
• Continuous Improvement
• Continuous Alignment
What is DevOps?

DevOps is about culture change
• Synergy of all functions of “getting into production”
Continuous Delivery is an example
of a technical implementation of
DevOps …
The “How”
Definitions

Tactical DevOps practices
• Assign Operation Staff to Project Team
– Ops Team Member participates in story development, iteration planning and stand-ups
• Capture Operations Tasks/Dependencies as Stories /Tasks in tracker
– Clearly communicate schedule in Ops Stories
– Operations can/should orchestrate Operations Stories through “Infrastructure-as-code”
wherever possible
• Maintain Operations tracker in same system as Stories aggregate operations
queue.
– Associate team-level Operations task to general operations queue
– Acknowledge that Operations is a service organization managing multiple priorities
– The operations team member champions these priorities on behalf of the team,
distributing the knowledge to required operations team members
• Ensure Operations has visibility into development and delivery pipeline
– Passive – Receive notification of all changes that may make it into production
environment, report
– Active – Provide ability to query and report on demand

Enterprise DevOps Practices
Enable collaboration amongst all stakeholders
• In a DevOps organization, developers, testers, and operations teams share goal
• Support clear and constant communication
Development based on operational input, operational plan on development input
• Developers understand how their software is going to be deployed
• Operations understands what is being deployed
• All stakeholders know when it is being deployed
Take a trust but verify approach to governance
• Enable developer to act rapidly
• Capture all activities
• Implement strong checks where needed, eliminate where the are not
Automation is a must
• Repeatability is critical to risk reduction and traceability
• Leverage enterprise deployment

• Do you consider yourself a DevOps organization?
• What obstacles have you faced in implementing DevOps?
• How frequently to you deploy to production?
• Can developer “push” to production?
• How to you govern production deployments?
• Do you manage your infrastructure with code?
– Chef? Puppet? Other?
Group Discussion

Topic #4
Feedback and Enterprise Metrics

Agile Governance and Visibility
Legend
Add On
CTF
• Reference Architecture
– Lifecycle plugins
• Role-Based Dashboards
– Executive, QA Mgr, Release Mgr,
Project Team
• Company-wide Traceability
– Build Management
– Release Management
– ARA Integration
• Cycle Time Metrics
– Build Duration *
– Cycle Time to Prod vs. Kill Rate *
– Artifact Average Age
• Velocity Metrics
– Burn down charts
– Build Count per day/week/month *
– File Churn per day
– # of deployments per day/wk/mo
• Community Metrics
– # of projects
– Registered users
Transaction Data & Insight
• Correlates “artifacts” vs just tickets
• Contextual & drillable dashboards
• Integrates TeamForge & 3rd party tools
• Single pane of glass across all global dev and
delivery teams, data and tools
Application Management

Executive Dashboard Portal

QA Manager Portal

Release Manager Portal

• How do you determine the “quality” of your productions deployments?
• Can you identify the the cycle-time from business need to delivery?
• As you adopt Agile development practices how to you measure success?
• How are reports rolled-up to provide management visibility?
• Share some reports that are important to you?
Group Discussion

In Conclusion
CollabNet Solutions, what’s next?

Please now Complete……..
Agile Assessment Questionaire……
And we’ll Give you…….
Gene Kim ‘Phoenix Project”
DevOps Best Selling Book (~ $45 value)

Next Steps #1
THE ASK IN RETURN FOR TODAY……….
30 Minute “Discovery Phone Call” …Soon!

Next Steps #2 - Deep Dive Demo – Onsite / WebEx
FRSApp
Work is planned
• Work item planning
• Associations
1 Users and Workspaces Created
• Community Architecture
• Project Templates
3
42
Jenkins Builds and Tests
Workspace is customized
• Tools provisioned
• Roles and Permissions
Developer assigned work
items
7
5 Developer changes code
6 Pushes changes
8 Notes exceptions notifies team
Feedback Issues9
Deploy package to ENV10
Create File Release11

Next Steps #3 - Enterprise Agility Assessment and Downstream Agile
Agile Delivery & DevOps
Agile Development
Enterprise SCM
Training Training
Implementation
Implementation
Consulting Consulting Consulting
Solutions
Product
Services
TeamForge
A. Enterprise Agility AssessmentService
Solution Pack Solution Pack
Blueprint
for Enterprise Agility
B. DevOps Applied Workshop
C. Agile Dev Applied
Workshop
Custom Continuous
Integration Implementation
D. Private/Public
Agile, CSM and
ALM Training

• Solution Pack solutions:
• Enterprise SCM leverages TeamForge SCM
(Git and SVN) Integration
• Agile Development (CI/CD) includes
Enterprise SCM
• Agile Delivery & DevOps Solution includes
Agile Development
CollabNet Solutions: TeamForge Solution Packs
Agile Delivery and DevOps
• Build + Release Workflow (Jenkins and ARA)
• Auto-build of build and release trackers
• Nexus integration – binary repos
Agile Development
• Build Workflow (Jenkins)
• Auto-build of build trackers
• TeamForge File Release System integration
Enterprise SCM
• TeamForge template – enterprise agility
template
• Dashboard template component
• Alerts component
• Solution Packs provide Enterprise Visibility and Traceability promote
repeatable, solutions for Agile Development and Delivery (Process and Tools)
• Solution Packs provide integrated solutions (Jenkins, Team City, ARA +)

› Across your entire application delivery pipeline, from
planning through deployment
› Across delivery lifecycles, workgroups, and your
distributed organization
› Enterprise-grade security with RBAC, permissions
management, authentication, encryption, auditing
› For creation and sharing of common, repeatable
processes across your organization
› Throughout development lifecycles and across
projects, tools, and teams
With CollabNet Enterprise Agility, You Gain
› Organization-wide discovery, collaboration, re-use,
and reporting

Questions?
blogs.collab.net
twitter.com/collabnet
www.facebook.com/collabnet
www.linkedin.com/company/collabnet-inc

About CollabNet
CollabNet is a leading provider of Enterprise Cloud Development. With more than 10,000 global customers, the
company provides a development platform and services to address three major trends disrupting the software
industry: Agile, DevOps and hybrid cloud development. CollabNet TeamForge® ALM, ScrumWorks® Pro Agile project
management and Subversion Edge and Enterprise Git source code management can be deployed separately or
together, in the cloud or on-premise. CloudForge® enables cloud development through a flexible platform that is
team friendly, enterprise ready and integrated to support TeamForge and leading third party tools. CollabNet
complements its technical offerings with industry leading consulting and training services for Agile and cloud
development transformations. Many CollabNet customers improve productivity by as much as 70 percent, while
reducing costs by 80 percent.
For more information, please visit www.collab.net.

Cycle Time Metrics

DevOps – Sample Report
This report compares multiple versions (may be in separate projects) and displays
the “Kill Rate” (time to close an artifact) – with the Cycle time for that Version to be
deployed into Production.
This kind of metric is unique to CollabNet. Traditional Agile Burn Up / Burn Down
charts (also available in CTF) do not show any connection to an actual deployment
environment

Velocity Metrics

SCM Sample Report

• This report is a classic Agile Burn down comparing multiple
releases (may be cross project)
Agile Development – Sample Report

Agile Development – Sample Report

CollabNet Solutions for Enterprise Agility
Blueprint
for Enterprise Agility
Reference Architecture
Agile Delivery & DevOps
Agile Development
Enterprise SCM
Training Training Training
Implementation Implementation Implementation
Consulting Consulting Consulting
Solutions
Product
Services
TeamForge
Enterprise Agility AssessmentService
Solution Pack Solution Pack

Infrastructure As Code
Is the concept that infrastructure should be treated as source code
•Aligns software developments practices with infrastructure
‒ Tags, branches and releases
‒ Manage life-cycle
• Test, Dev, UAT, Production
‒ Continuous Testing

PULL
Making Automated Deployments Real

Improving Code Quality

Implementation Example
① Ops, DB, and App Developers implement user stories from TeamForge and commit changes to SVN/GIT, the
user stories and code changes are associated.
② A CI build job runs, executing unit tests, code analysis, etc, a TeamForge Build Artifact is created, change notes
are generated and associated.
③ Every 15 minutes or on-demand a snapshot build is published to the Nexus Repository. The snapshot build is
deployed to the Development servers by Automic.
④ The Project Manager reviews the Change Notes and Release Folder in TeamForge and using the data decides to
promote a build as a Release Candidate, she creates a Release Manager Artifact (RMA) and set it to “Ready to
Release.”
⑤ A Jenkins Release Candidate Promotion job runs executing the application builds, publishing the artifacts to
Nexus and populating Automic with the release meta-data.
⑥ An Automic package references the Nexus release holding the release candidate to be deployed.
⑦ Operations, QA and/or Change Management promote and deploy the release candidate using Automic
Workflows.
⑧ At each promotion and deployment step the TeamForge Release Artifact is updated from Automic and team
members receive email notifications.
⑨ The Release Dashboard in TeamForge provides up-to-date pipeline Activity Reports and Release Notes.
⑩ Dev, QA, Ops and Management can view the Release Dashboard inTeamForge to track acitivy and make
informed decisions.

SCM
Unknown Input
Results in Unknown Output
Build
Product
Build
Product
Published
Exec
Deployment QA
Internal
Libraries
Project and
Sub-projects
3rd Party
Libraries
Binaries
?
Project A
Build Process
Project B
Build Process
? ?
?
?
? ? ?

SCM
Managed Inputs
Result in Trusted Outputs
Build
Product
Project B
Build Process
Build
Product
Published
Exec
Deployment QA
Project A
Build Process
Internal
Libraries
Project and
Sub-projects
3rd Party
Libraries
Binary Artifact Repo (Nexus)
Binary Artifact Repo
(Nexus)

Continuous Integration Tools
Maven
Ant
MSBuild
Make
NAnt
Rake
Subversion
GIT
Perforce
PVCS
XUnit
Sonar
Cobertura
Checkstyle
Coverity
SCM
Java
.Net
Analytics
CI
CI Products
Jenkins / Hudson
TeamCity
Bamboo
Build tools
And compilers

Shared Process Example

Wrap Up: TeamForge TrialZone
Dashboards
Embedded Tools Integrated Tools
…
Deployment Manager
GitEye
Packaged Tools
Code Search
Code Review
Git + Gerrit
Jenkins (CI)
Private
Cloud
Public
Cloud
On-Premises Deployment
Data Center Deployment

Survey Questions & Feedback
Chris Nimmer
cnimmer@collab.net
www.collab.net
703.869.6402
blogs.collab.net
twitter.com/collabnet
www.facebook.com/collabnet
www.linkedin.com/company/collabnet-inc
https://www.surveymonkey.com/s/GCBMQRC

CollabNet Houston Workshop Live Enterpise agility_11.12.14

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a CollabNet Houston Workshop Live Enterpise agility_11.12.14

Semelhante a CollabNet Houston Workshop Live Enterpise agility_11.12.14 (20)

Último

Último (20)

CollabNet Houston Workshop Live Enterpise agility_11.12.14