Transcript Document

Serena Orchestrated-ALM Workshop
Demand, Develop, Deploy
27
Kevin A. Lee – Solutions Architect
Sep 2011
SERENA SOFTWARE INC.
Agenda
• Introductions and Expectations
• Serena Orchestrated-ALM
• Strategy and Vision
• Reference Architecture
• Demand Management
• Overview and Demonstration
• Development Management
• Overview and Demonstration
• Release Management
• Overview and Demonstration
• Questions and Feedback
2
SERENA SOFTWARE INC.
Agenda
• Introductions and Expectations
• Serena Orchestrated-ALM
• Strategy and Vision
• Reference Architecture
• Demand Management
• Overview and Demonstration
• Development Management
• Overview and Demonstration
• Release Management
• Overview and Demonstration
• Questions and Feedback
3
SERENA SOFTWARE INC.
ALM Market Evolution
Prior Generation
• Development Driven
• Point Products
• Silo Product Reporting
• Point-to-Point Integrations
• Rip and Replace
• Manual Audit
4
Next Generation
• Demand to Deploy
• Integrated ALM Solutions
• E2E Dashboards & KPIs
• Process Orchestration
• Leverage existing
investment
• Audit Ready
Definition of ALM
“ALM encompasses the practices, processes and tools that aid in
the management of the application development life cycle,
specifically the workflow and artifacts associated with producing or
maintaining a custom software application.
Key capabilities include change management, workflow and
work item management, and an integration backplane that
allows an organization to establish traceability and accountability
across multiple processes, multiple locations, multiple tool types,
and multiple tools of each type across the stages of development
and delivery.”
Jim Duggan, Thomas E. Murphy, Gartner
Marketscope for Application Lifecycle Management
5
SERENA SOFTWARE INC.
Introducing Orchestrated Application Delivery
Develop
Demand
Staff
Exec
Developer
QA
Deploy
Build
Engineer
Customer
Developer
Scrum
Master
Build
Engineer
Business
Analyst PMO CIO
Operations
Release
Manager
CTO
CCB
Sys
Admin
6
Serena Role Based Suites
Develop
Demand
Deploy
Serena Request Center
Serena Lifecycle Dashboard
Serena Service Manager
Serena
Requirements
Manager
Requirements
Elicitation
Requirements
Change
Management
7
Requirements
Management
Serena
Development
Manager
Serena
Release
Manager
SBM
Issue/Defect
Test Case
Orchestration
Management
Management
Agile
Planning
Development
& Build
SERENA SOFTWARE INC.
Release
Planning
Release
Vault
Release
Automation
Orchestrated IT – Closed Loop ALM and ITSM
Serena
Service
Manager
Infrastructure
Changes
Incidents
Biz user
Ops Change
Requests
Serena
Request
Center
Serena
Release
Manager
Production
Defect Fix
Request
Project & Enhancement
Requests
App Releases
Serena
Requirements
Manager
8
Serena
Development
Manager
SERENA SOFTWARE INC.
SBM-Based Solution Frameworks
Cross-Solution Reporting
Dashboard
Solution
Solution Contains
• Processes
• Data Model
• Forms
• Reports
• Notifications
• Role Configurations
Solution Framework Contains
• Custom Shell (UI Templates)
• Web Services (integrations)
Serena Business Manager
10
Solution Framework
SBM Platform
SERENA SOFTWARE INC.
Example: Release Manager Packaging
ALM Dashboard
Rel Mgmt KPIs
Release Trains
Application Releases
Release Packages
Deployment Tasks
Change Requests
Deployment Units
Web Services
Custom RLM UI
Serena Release Control
Forms & Reports
Plan
Promote
Deploy
Serena Release Manager Framework
Release
Vault
11
Approve
Release
Automation
SERENA SOFTWARE INC.
SBM
ITSM
Third Party Orchestrations
Requirements
Manager
PPM
12
Deploy
Develop
Demand
PLM
Development
Manager
Modeling
SCCM
Release
Manager
Quality
ITSM
O-ALM Reference Architecture
• What is it?
• Serena’s recommended best practices for realizing E2E ALM
• Blueprint for integrating Serena products & solutions
• Described by
• Reference Architecture – key artifacts, processes & integration points
• Implementation Guide – implementation best practices
• Target Audiences
• R&D – blueprint for integrating products & solutions
• Field & PS – implementation guidance for custom solutions
• Marketing – technical background for customer-facing collateral &
whitepapers
• Customers – recommended best practices for Serena O-ALM
13
SERENA SOFTWARE INC.
Logical Architecture
14
SERENA SOFTWARE INC.
Domain Model
15
SERENA SOFTWARE INC.
Process Model – Example Dev. Change Request
16
SERENA SOFTWARE INC.
Scenarios: Execute New Development
Business User
Business Analysts
Product Management
Development Team
Test Team
Release Team
Submit Request
Initial Assessment
Consider Request(s)
Allocate Requests to
Iterations
Update and Define
Test Cases
Create Release
Package
Defer/Add to Backlog
Decompose Requests
to Tasks
Assign Requests
and/or Baseline
Assign Requests to
Release
Develop and Test
Create Deployment
Tasks
Create Development
Request(s)
Build and Baseline
Deploy Release to QA
Deploy to
Integration?
Define and Prototype
Requirements
Review Prototype
Approve
Requirements
Deploy Release to
Production
Execute Test Cases
Validate Request
SBM
17
SBM/Dim RM/Composer
SBM
SBM/Dim CM/Eclipse/Hudson
SERENA SOFTWARE INC.
SBM/QC
SBM/Dim CM/Nolio
Agenda
• Introductions and Expectations
• Serena Orchestrated-ALM
• Strategy and Vision
• Reference Architecture
• Demand Management
• Overview and Demonstration
• Development Management
• Overview and Demonstration
• Release Management
• Overview and Demonstration
• Questions and Feedback
18
SERENA SOFTWARE INC.
Few Organizations Do Requirements Well
60%
of projects don’t meet
most business
requirements
of software features
are rewritten for each
new project
200X
33%
more expensive to
resolve issues later in
development process
19
90%
of development costs
wasted from poor
requirements
SERENA SOFTWARE INC.
Serena Requirements Management Lifecycle
Capture
20
Prioritize
Prototype
Detail
SERENA SOFTWARE INC.
Review
Deliver
Validate
Serena Requirements Manager
Requirements Definition
Requirements Development
Requirements Validation
Prototype
Composer
Dimensions
RM
SBM
Word
21
Agile
SERENA SOFTWARE INC.
CM
QC
Serena Requirements Manager Concepts
Primary Items
(with Workflow)
RM Class
Business Change
Request
External Items
1..n
1..n
n..1
Feature
1..1
Use Case
1..n
1..n
Test Requirement
Dev Change
Request
22
SERENA SOFTWARE INC.
System
Requirement
QC Requirement
Scenario: Execute New Development
Business User
Business Analysts
Product Management
Submit Request
Initial Assessment
Consider Request(s)
Development Team
Test Team
Release Team
SBM/Dim CM/Eclipse/Hudson
SBM/QC
SBM/Dim CM/Nolio
Defer/Add to Backlog
Assign Requests to
Release
Define and Prototype
Requirements
Review Prototype
SBM
23
Approve
Requirements
SBM/Dim RM/Composer
SBM
SERENA SOFTWARE INC.
Agenda
• Introductions and Expectations
• Serena Orchestrated-ALM
• Strategy and Vision
• Reference Architecture
• Demand Management
• Overview and Demonstration
• Development Management
• Overview and Demonstration
• Release Management
• Overview and Demonstration
• Questions and Feedback
24
SERENA SOFTWARE INC.
Application Development Realities
DEMAND
DEVELOP
48%
69%
25
Don’t have
standard tools
Development is offshored & outsourced
SERENA SOFTWARE INC.
DEPLOY
70%
Cost of development
is in rework
62%
IT projects fail to
meet schedule
Serena Development Manager
Dimensions
CM
ALM
Dashboard
SBM
IDE
26
RM
SERENA SOFTWARE INC.
QC
Serena Development Manager Concepts
Primary Items
(with Workflow)
Aux Table Items
ALM Project
External Items
1..n
1..n
Dev Change
Requests
n..1
1..1
Dim CM Task
1..1
Dev Tasks
Dev Packages
QC Defect
1..1
Dim CM Baseline
27
SERENA SOFTWARE INC.
Multi-site, Multi-platform, Multi-Environment
Java
C/C++
Microsoft.NET
Define
Develop
Web/PHP
Build
Test
SQL/COBOL
Deploy
Remote
Transport
Windows
Mainframe
Systems
Open
Systems
z/OS
Linux
UNIX
Library Caching
Define
Develop
Build
Test
Deploy
Serena’s Orchestrate-ALM Dashboard
29
Scenarios: Execute New Development
Business User
Business Analysts
Product Management
Development Team
Test Team
Allocate Requests to
Iterations
Update and Define
Test Cases
Release Team
Decompose Requests
to Tasks
Develop and Test
Create Development
Request(s)
Build and Baseline
Deploy to
Integration?
Execute Test Cases
SBM
30
SBM/Dim RM/Composer
SBM
SBM/Dim CM/Eclipse/Hudson
SERENA SOFTWARE INC.
SBM/QC
SBM/Dim CM/Nolio
Agenda
• Introductions and Expectations
• Serena Orchestrated-ALM
• Strategy and Vision
• Reference Architecture
• Demand Management
• Overview and Demonstration
• Development Management
• Overview and Demonstration
• Release Management
• Overview and Demonstration
• Questions and Feedback
31
SERENA SOFTWARE INC.
Release Management – What does it
Mean to You?
Biweekly
According to Webster’s:
1. Occurring twice per week
2. Occurring every two weeks
32
SERENA SOFTWARE INC.
Release Management Process
How Would You Describe Your
Release Management Process?
33
Release Management Satisfaction Is Low
34
Release Management … impact on business…
60%
INFRASTRUCTURE
Release Failures
60% of application failure &
downtime is release related.
(IDC Survey 2009)
Long Release Times
Release bottlenecks (can’t
make release window) delays
& limited operational agility.
High Costs
75% of IT operation teams’ is
spent on application release.
(Forrestor, 2009)
Serena Release Management
Development
Release Control
Plan, Manage & Approve Releases
Application
Software
Changes
Release Vault
Secure, Auditable Path to
Production
Deployed
Application
Releases
Release Automation
Automate Application
Configuration Tasks
• Release Manager
• DevOps
36
IT Ops
Datacenter
Serena Release Manager
Release
Vault
(Dim
CM/ZMF)
Release
Automation
Release
Control
CM
37
SVN
SERENA SOFTWARE INC.
RALLY
Serena Release Manager Concepts
Primary Items
(with Workflow)
1..n
Release Calendar
Aux Table Items
Release Train
External Items
1..n
Application Release
1..n
Dev Chg Request
1..n
Release Package
Application
1..n
Deployment
Process Template
Component
Deployment
Process
1..n
1..n
Deployment Unit
Deployment Task
Manual
38
SERENA SOFTWARE INC.
Automated
Customer Success
Serena Release Management
Release Management Satisfaction
Reduced Time from Dev to Deploy
“We now have a standardized,
managed and efficient software
release tool which has made our
customers very happy.”
“Serena has improved management
of code releases from development
through to production, reducing
delivery time by 25%.”
System Administrator
IT Specialist
Fortune 500 Computer Services Company
Fortune 500 Telecommunication Services Company
Automating Releases to Avoid Errors
“We have standardized and
automated our end-to-end coding
and release management process to
reduce human errors.”
Serena Release Management
“Everything is 100% under control.”
IT Director
System Administrator
Global 500 Pharmaceuticals Company
Global 500 Banking Company
39
SERENA SOFTWARE INC.
Customer Success
Serena Release Management
“Releasing applications into production environments is a critical part
of application development. Working with Serena makes coordinating
release processes very straightforward and helps us ensure all
stakeholders are notified on upcoming changes.
Instead of relying on manual processes, we have implemented a
repeatable, reliable procedure that is not only saving everyone
headaches, it also reduces cost.”
David Bell, Change and Release Manager
Mitsubishi UFJ
40
SERENA SOFTWARE INC.
Scenarios: Execute New Development
Business User
Business Analysts
Product Management
Development Team
Test Team
Release Team
Update and Define
Test Cases
Create Release
Package
Assign Requests
and/or Baseline
Create Deployment
Tasks
Deploy Release to QA
Deploy Release to
Production
Execute Test Cases
Validate Request
SBM
41
SBM/Dim RM/Composer
SBM
SBM/Dim CM/Eclipse/Hudson
SERENA SOFTWARE INC.
SBM/QC
SBM/Dim CM/Nolio
Questions
and
Feedback
42
SERENA SOFTWARE INC.