10.15.2014 dallas ws_brian_d_dn_live workshop enterpise agility_cust

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 DawsonSales Manager Technical Account Mgr. Guest [email protected] [email protected] [email protected] 720-438-7218 214.690.0236

Logo CollabNet Confidential

CollabNet Solutions for ….

mailto:[email protected]




• Goals– Understand the Blueprint to Enterprise Agility

– Understanding of common solutions for Enterprise 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 and Format


• 4:00 – 4:45 PM – Eat, Drink and Meet

• 4:45 – 5:00 PM – Kick-off, Intros, Agenda

• 5:00 – 5:30 PM – Enterprise Agility, Upstream and Downstream Agile– Overview of the Blueprint to Enterprise Agility

– Connecting Agile Planning (Upstream) to Agile Development and Delivery (Downstream)

– Group Discussion

• 5:30 – 6:00 PM – Continuous Integration and Continous Delivery– Review of Continuous Integration and Continuous Delivery


• 6:00 – 6:25 PM – Enterprise DevOps– What is Enterprise DevOps

– Real-world Practices


• 6:25 – 6:50 PM – Feedback and Enterprise Metrics– Importance of Feedback and Enterprise Metrics

– Example Metrics


• 6:50 – 7:00 PM – Conclusion

Workshop Agenda


CollabNet Introduction

Industry Leadership• ALM, SCM, cloud, agile• Transformed 100s of largest,

most respected IT orgs• Manny industry leader awards• Enterprise agile experts

– 17,000+ ScrumMasters trained

Technology Pioneer• Creator of Subversion (SVN)• 1st cloud-based ALM solution• 1st compliant GIT solution

Proven Scale• 10,000+ customers• 6M+ users • 80,000 users at one site

Industry Recognition


Presenter Introduction

•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

Ok this is a bit gratuitous….

At CollabNet I work with large and small software development organizations to improve the Application Lifecycle Management 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.

6 Copyright ©2014 CollabNet, Inc. All Rights Reserved.6 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

Topic #1Enterprise 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.”


Blueprint for Enterprise Agility

Embrace Cloud

ImplementCommunity Architecture

Codify Dev Processes

OrchestrateDevOps

Leverage External Clouds

Collaboration & Insight

Va

lue

• Centralize access & visibility• Plug-in & collaborate – code, issues, people

• Map business / enterprise architecture(project hierarchies, workspaces, artifacts, roles)

• Be social (e.g. code reuse)

• Support Agile and mixed processes• Codify data definitions, tool integrations, workflows• Gain end-to-end visibility, traceability, repeatability

• Automate Continuous Delivery & DevOps• Collaborate enterprise-wide

• Extend DevOps to ext. clouds• Integrate & govern 3rd party

services


Enterprise Agility

Agile Delivery & DevOps

Agile Development

Enterprise SCM


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 upstream


*Only 13% preform upstream plus downstream CI/CD and test-driven

development

Enterprise Agility Requires Process & Platform IntegrationRequirements for Enterprise

AgilityAgile

ProcessAgile

PlatformComments

Agile Training

• Certification• Culture & Team• Iteration/Feedback

Codify a “consistent set” of agile processes into a tool platform, enabling scale across the company

Global • Distributed• Collaborative

Extend local agile teams & Sticky Note processes to be globally collaborative

Traceable • Project Traceability• Reusability

Create an auditable system of record for multiple sprints & releases

Scope • Integration to Downstream Agile

Tie upstream agile to downstream CI/CD/DevOps

Reuse & Scale

• Best Practices

- Codify libraries of common, repeatable workflows

Scale • Leverage Companywide

- Create business and technology hierarchies for global discovery, collaboration, re-use and reporting

*Only 32% perform standup, burndown/burnup, and short iterations; product owner; and constant feedback. * Forrester 2014

STREAM

DOWN

STREAM

UP


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?

Group Discussion


Topic #2Continuous Integration and Continous Delivery


Has this happened to you?

You tell management that

development of all user stories is

complete and you are ready to

deploy the application by Friday.

After QA, rework, and two failed

deployments you deploy the

application… 4 weeks later.

You receive a build from Development for your team to perform UAT, then spend the next 2 days trying to identify what has changed, instead of testing and delivering value.


CI and CD – Has this happened to

Your development team pushes an

update to the shared SSL library used

by all of the customer facing highly

secure web applications. Due to a

duplicate GoTo statement all

applications using the library

communicate passwords in the clear!

Share your stories….


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?


• Continuous Delivery extends the CI process from build to include test and deploy phases– Ensure fluid coordination and communication between take holders– Handle need for governance

Continous Integration vs Continous 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


Key attributes of CI and CD

• Drive automation and production of deployable of software

– Efficiency through automation

– Quality built in through good software development practices and

continuous testing

– Transparency through feedback and reporting

Core principles


Individual Benefits

• More time focusing on adding value

• No need to wait hours, days, months to know how check-in

affects the build

• Automation of repetitive manual processes

• Less time spent making builds work

• Reduced time manage dependencies

• Shared accountability


Team Benefits

• Increased team productivity

• Higher collaboration

• Collectively deliver more value

• Constant availability for the build for testing, demo or release


Optimized Development with TeamForge and CI

Work is planned

• Work item planning

• Associations

Feedback from builds, deployment, tests, etc.

1 Users and Workspaces Created

• Community Architecture

• Project Templates

3

4

8

2

Jenkins Builds and Tests

Workspace is customized

• Tools provisioned

• Roles and Permissions

• Dashboards created

Developer assigned work items

7

5 Developer changes code

6 Pushes changes

App FRS


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.

BD

Refactor diagram to focus on CI portion, CI to Dev


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


– 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?– Do you leverage automated testing?– Can management and other stakeholders track progress of builds and

non-production deployments?

Group Discussion


Topic #3Enterprise 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

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


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


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 based on development input• Developers understand how their software is going to be deployed• Operations understands what is being deployed• All stakeholders now 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 #4Feedback and Enterprise Metrics


Agility Metrics and Insight• Persona Based Dashboards

– Executive– QA Manager– Release Manager– Project Team

• Business Value Metrics– Business Value Streams KPIs Agility

Metrics ROI

• 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/week/month

• Community Metrics– # of projects– Registered users

Legend

Add On

CTF


Executive Dashboard Portal


QA Manager Portal


Release Manager Portal


Agile Development – Sample Report


Cycle Time Metrics


Velocity Metrics


SCM Sample Report


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

Agile Development – Sample Report


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


• How do you determine the “quality” 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 ConclusionCollabNet 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)


Partial List of Customers Platform, People, Value……Proof Points

HealthcareHealthcareFinancialFinancial Global ServicesGlobal Services TechnologyTechnology Govt. &

AerospaceGovt. & Aerospace

nehta

$1.2 Million SavingsConsolidation, Support

Scalability 10,000+ users, Consolidation, Support

Privately HostedApprox. 10,000 users,

HHS.gov

http://www.reuters.com/home.jhtml;jsessionid=UTXGEU5GPVPZWCRBAEOCFEY

http://www.dhs.gov/


Trend #1 - SCM Adoption: Get Ready for Git


Manage Git, Subversion & CVS with One Enterprise Platform

CVS


Trend #2 - Agile - Adaptive Planning & Task Boards

“First ever adaptive planning boards completely integrated within a native ALM platform.”

Adaptive Planning

• Agile, traditional, in-between

• Any work item: story, defect, task

• Drag & drop complete hierarchies

Integrated with ALM

• Built on tracker: 100% integrated

• Actionable work items

• Adjust plans ‘on the fly’

Completely integrate your agile management and

software dev teams


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

ImplementationImplementation

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


› Across your entire application delivery pipeline, from planning through deploymentManageability

› Across delivery lifecycles, workgroups, and your distributed organizationAgility

› Enterprise-grade security with RBAC, permissions management, authentication, encryption, auditingGovernance

› For creation and sharing of common, repeatable processes across your organizationTemplated Workflows

› Throughout development lifecycles and across projects, tools, and teamsVisibility & Traceability

With CollabNet Enterprise Agility, You Gain

› Organization-wide discovery, collaboration, re-use, and reportingCollaboration Arch.


- 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 DawsonSales Manager Technical Account Mgr. Guest [email protected] [email protected] [email protected] 720-438-7218 214.690.0236

Logo CollabNet Confidential

CollabNet Solutions for ….





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.

http://www.collab.net/

10.15.2014 dallas ws_brian_d_dn_live workshop enterpise agility_cust

Software

pm enterprise agility

pm enterprise devops

collabnet solutions

governance agile delivery

agile overview

continuous delivery

pm conclusion3 copyright

site4 copyright