Dimensions CM Spring 2016 VUG

Post on 19-Jan-2017

388 views 1 download

Transcript of Dimensions CM Spring 2016 VUG

1Copyright © Serena Software 2015

Dimensions CMSpring 2016 Virtual User Group

Ashley Owen Director of Product MarketingMarch 15th, 2016

2

Welcome to the quarterly Dimensions CM VUG

News and Announcements

Agile, DevOps and Dimensions CM

Q&A – Ask the Experts

3

News and Announcements

4

Serena Central

SIG to discuss LDAP Integration

SIG to discuss Agile functionality

Virtual User Group online

SIG to discuss using Git with CM

http://www.serenacentral.com/

5

Upcoming Events

Federal User GroupApril 5th - 6th 2016

Serena xChange16Sept 19th – 23rd 2016

6

New Serena Home Page

7

Have you ever wondered?

http://help.serena.com/doc_center/doc_center.html#dcmFeatureHistory

8

Agile, DevOps and Dimensions CM

9

Gartner’s Bimodal IT

Mode 1 Mode2

Goal Reliability Agility

Value Price for Performance Revenue, Brand, Customer Experience

Approach Waterfall, V-Model Agile, Kanban

Governance Plan-Driven, Approval based

Empirical, Continuous, Process based

Talent Good for conventional processes and projects

Good for new and uncertain projects

Culture IT-Centric, Removed from End users

Business-centric, Close to End Users

Cycle Time Long (Months) Short (Days, Weeks)

Marathon Runner Sprinter

10

“By 2017, 75% of IT organizations will have a bimodal capability”*

Systems of Innovation

Systems of Differentiation

Systems of Record

Mode 1Reliability

Waterfall, V-ModelIT-centric

Release inMonths/Years

Mode 2Agility

Agile, KanbanBusiness-centric

Release inDays/Weeks

Dependencies

Governance

Cha

nge

*Gartner predictions, 2014

11

Systems of Innovation

Systems of Differentiation

Systems of Record

App 1Traditional

Waterfall, V-ModelIT-centricRelease in

Months/Years

App 2Agile

Agile, KanbanBusiness-centric

Release inDays/Weeks G

overnanceC

hang

e App 3Transitional

Scrum fallProduct-centric

Release inWeeks/Months

Serena Provides Multi-Modal IT Support

Dependencies

Application Deployment speed determined by Application Architecture, Application Type and Compliance requirements

12

• Unit Testing• Distributed Teams• Refactoring• Continuous Integration• Automated Acceptance Testing• DevOps• Continuous Delivery• Test-Driven Development (TDD)• Pair Programming• Behavior-Driven Development (BDD)

Agile Enterprise Development & Delivery Practices

13

Serena Dimensions CMDevelop with velocity - collaboratively, securely and efficiently

Core Strengths• Graphical change graph• Collaborative peer review• Proven security & performance• Highly scalable SCCM• Strong process support

What’s New?• Shelving & Personal Streams• Integrated “Expert” Tool Chain• Cherry Pick Merge• KPI Metrics/Reporting• REST API

14

Agile Management for CM RequestsDevelop with velocity - collaboratively, securely and efficiently

Key Capabilities• Backlog management, Kanban,

burn-down and reporting• Development focused• Planning of CM requests• Management of teams• Integrated with SBM, RM and Jira

Value Benefits• Visualize and plan work within CM• Track progress, identify bottlenecks• Manage movement of work between

backlogs in other tools• Integrates with the full CM lifecycle

15

Serena Dimensions CM - Integrated Peer Code ReviewDevelop with velocity - collaboratively, securely and efficiently

Key Capabilities• Collaborative web based architecture• Integrates with Agile stories• Linked to Continuous Inspection• Strengthens audit trail & governance• Configurable for Projects & Teams

Value Benefits• Improved code quality

• Find 70-90% of all defects earlier• Cost reduction

• Save up to 30% of re-work hours• Developer productivity

• Up to 25% improvement in codingPeer Reviews in Software - A Practical Guide by Karl E. Wiegers

16

Feature Based Development - Isolating units of work

• Why separate out pieces of work?• Agile approach (only include in the release what work is complete)• Will not be affected by defects/changes introduced by other work• More stable/release-ready software

• Works best if the features are truly separate• Code does not overlap with that of other features• Separate software components• Something with a well defined interface

Mainline

Feature 1

Feature 2

17

Feature Based Development - Using separate streams

• Each development project has a mainline• Maybe one of these for each parallel release of software• Maybe your releases also feed up to a single mainline

• Separate stream for features or teams• Branch off the release stream when development starts

Mainline

Release2

Release1

FeatureX

18

Feature-based Development - How and when to rebase?

• When to “rebase” or update your Streams from mainline?• When there is a change you are dependent upon• You may not need to do this at all

• But the longer you leave this the harder your merge will be

Mainline

HotFix

NextRelease

FeatureX

Hot Fix has completed so

the team decide to merge it in.

19

Feature-based Development - How and when to merge?

• How and when to merge • When testing is complete• When another team needs your feature• When Serena Pulse tells you the health and quality are good• When a release is complete

Mainline

HotFix

NextRelease

FeatureX

Release has shipped, so can be merged to

mainline.

20

Serena Dimensions CM – Continuous Inspection ToolchainDevelop with velocity - collaboratively, securely and efficiently

Key Capabilities• Extensible plug-in architecture• Schedule & inspect code changes• Report findings & vulnerabilities• Supports DevOps “Shift-Left” • Aggregated KPI Metrics

Value Benefits• Display results in code review• Real-time developer feedback• Reduce coding risks & issues• Monitor code health & quality• Speed release readiness

"Given enough eyeballs, all bugs are shallow."The Cathedral and the Bazar —Eric Raymond

21

Enhancing Deployment and DeliveryDeliver with velocity - collaboratively, securely and efficiently

Key Capabilities• Integrates SDA with Dimensions

deployment pipeline• Replace Dimensions deployment scripts

with SDA processes

Value Benefits• Brings the power of SDA to CM

Deployments• Use CM for managing stage gates, and

SDA to orchestrate deployment• Integrated audit trail. Know what was

deployed where and why

22

Dimensions CM Deployment

Development SIT UAT Staging Production

Dimensions GSL – Promotion Stages

Dimensions Deployment Areas

23

Dimensions CM and SDA deployment

Development SIT UAT Staging Production

Dimensions GSL – Promotion Stages

SDA Environments and Pipelines

Dev

Dev-Test

SIT

UAT Stage Prod

24

Deployment Automation – the reality

Dev Test UAT Prod

Application B (Legacy)High risk – low velocity

Application C (Mobile)Time-to-market critical

Low Risk

Application A (Java)Low risk – high velocity

Application D (.Net)High compliance

Medium risk

Application Deployment speed determined by Risk, Application Architecture, Application Type and Compliance requirements

Automated deployments (continuous deployment) Manual intervention

25

But wait, do you have a Repository Sprawl problem?

• DevOps driving option of Git

• Repository Sprawl• Multiple Source Code Repos• Individually Managed/Maintained

• Security???• Reliability???• Cross-team collaboration???• Audit trail???

“Commercial SCCM offerings offer improved scale, performance, security and integration.” Jim Duggan, Joachim Herschmann, Gartner 2015 SCCM Market Guide

26

Dimensions CM Secure Vault

Dimensions CM

Dimensions CMPromotion Pipeline

Serena DeploymentAutomation

Dimensions CM = Git Master Repository

Dimensions CM Pulse

svnS

ubversion B

ridge

CM

Git

Connector

27

Docker Trusted RepositoryDeliver with velocity - collaboratively, securely and efficiently

Key Capabilities• Enterprise strength Docker Registry• Versioning and approvals of Docker

images• Granular access control for images

Value Benefits• Single source for all your artifacts• Scalable and fault tolerant• Secure and control what images are

deployed• Full traceability

28

What the Analysts Say “ ”

“By 2016, DevOps Will Evolve From a Niche to a Mainstream Strategy Employed by 25 Percent of Global 2000 Organizations”

“…with the total for DevOps tools reaching $2.3B in 2015 (up 21% yoy)”

“DevOps-ready tools have seen and will continue to see the largest growth potential”

“Cultural resistance and low levels of process discipline will create significant failure rates for DevOps initiatives..” http://www.gartner.com/document/2987231.

30

DevOps and artifact management

Serena Confidential

Continuous IntegrationContinuous Deployment

Anywhere, anytime, any platform

End-to-end, Dev to Ops

Complex, heterogeneous toolsetRequires sophisticated orchestrationSingle point of control and visibility

31

• Incremental Delivery– Stream based development– Feature based development

• Shift Left Testing– Continuous Inspection

• Automated Testing• Define Done

Agile, DevOps and Dimensions CM

• Version Everything– Software, Images, Models, containers

etc.• Incremental Delivery

– Stream based development– Feature based development

• Shift Left Testing– Continuous Inspection

• Automate Everything– Continuous Inspection + SDA

• Dashboard Everything

Mode 1 Mode 2

32

Open Forum - Ask the Experts

33

Serena Software’s DevOps Drive-inTuesday March 29th, 09:00 PT 17:00 GMT 18:00 CETFirst 300 attendees will receive a copy of Gary’s book

www.serena.com/drive-in

Gary Gruver

34

Thank you

www.serena.com