• Like
  • Save
Ranger4 DevOps at High Speed Event - Mark Roberts
Upcoming SlideShare
Loading in...5
×
 

Ranger4 DevOps at High Speed Event - Mark Roberts

on

  • 903 views

November 14th 2013 was Ranger4's DevOps at High Speed event at Claridge's in London with our partners IBM and AppDynamics. This is Mark Roberts from IBM's DevOps Introduction presentation.

November 14th 2013 was Ranger4's DevOps at High Speed event at Claridge's in London with our partners IBM and AppDynamics. This is Mark Roberts from IBM's DevOps Introduction presentation.

Statistics

Views

Total Views
903
Views on SlideShare
854
Embed Views
49

Actions

Likes
0
Downloads
23
Comments
0

2 Embeds 49

http://www.ranger4.com 48
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Ranger4 DevOps at High Speed Event - Mark Roberts Ranger4 DevOps at High Speed Event - Mark Roberts Presentation Transcript

    • IBM Rational DevOps Introduction Mark Roberts IT Specialist, IBM Rational UK © 2013 IBM Corporation
    • Why Do Software Project Fail? Understanding the software engineering lifecycle 1.  Unstable, changing requirements (95%) 2.  Inadequate quality control and poor quality measures (90%) 3.  Inadequate progress tracking (85%) 4.  Inadequate cost and schedule estimating (80%) 5.  False promises by marketing and sales personnel (80%) 6.  Rejecting good schedule estimates for arbitrary dates (75%) 7.  Informal, unstructured development (70%) 8.  Inexperienced clients who can't articulate requirements (60%) 9.  Inexperienced project managers (50%) 10.  Inadequate tools for quality/analysis, lack of inspections (55%) 11.  Reusing assets filled with bugs (30%) 12.  Inexperienced, unqualified software engineering teams (20%) From Caper Jones Visualization of change and complexity
    • The emergence of Agile development Compressing the software delivery lifecycle
    • Compressing the Software Delivery Lifecycle Operations Development Development Cross over – DevOps Operations Blended roles and repeated operations Procedural Rigor Creative Behavior Agile Delivery Process Platform Procedural Rigor Creative Behavior Waterfall Process Platform
    • Software development: obsolescence by software delivery Software Development Distinct development phase Software Delivery Continuously evolving systems Distinct handoff to maintenance No distinct boundary between development and maintenance Requirements-design-code-test sequence Sequence of released capabilities with ever increasing value Phase and role specific tools Collocated teams Standard engineering governance Engineering practitioner led Common platform of integrated process / tooling Distributed, web based collaboration Economic governance tailored to risk / reward profiles Business value and outcome led
    • Environmental reality adds significant complexity §  Many tools from many vendors  Heterogeneous environments that are flexible for partners and suppliers Tool A §  Many teams in many places DB  Distributed development, cross site product development  Many levels of teams Tool B UI LOGIC DB Tool E UI LOGIC PMO, Bus, dev teams, ops teams, etc DB §  Coherent process  Flexible and robust process UI Tool C LOGIC DB supporting Lifecycle / Agile Methods  Measure and improve effectiveness DB Tool D UI LOGIC UI LOGIC 6
    • Delivery Challenges People Today’s business and technical needs are pushing traditional delivery approaches to the breaking point Customers! Line of Business! Requirements! Information Dev & Test Teams! 1st Gap! Desire for fast and continuous innovation! Process Operations Team! 2nd Gap! Code & Tests! Business Services! “At some point, you take a step back, and you realize you have an awful lot of siloe’d systems that are limiting transparency across strategic projects”. - Development Director Temenos, Inc.
    • A lack of continuous delivery impacts the entire business CHALLENGES Costly, error prone manual processes and efforts to deliver software across an enterprise Customers % 41 experience development delays Slow deployment to development and test environments leave teams waiting and unproductive Business Owners % 34 experience deployment delays Upgrade risk due to managing multiple application configurations and versions across servers Development/ Test % 45 experience production delays Operations/ Production 4-6 weeks to deliver code changes
    • Addressing BusDev gaps Customers! Line of Business! 1st Gap! Dev & Test Teams! Operations Team! 2nd Gap! Addressed by...! Desire for fast and continuous innovation! Requirements! Business Code & Tests! 1.  Iterative and Incremental Process Services! 2.  Traceability Agile Dev"
    • In Context Collaboration
    • Global Delivery of Software: An Issue ? Design Construction 30% Analysis Component Test 40% 40% Function & Performance Test 20% Deployment Project Management Near-Shore (East Europe) 70% 20% 80% 60% On-Site (Europe) 100% 100% 60% Off-Shore (India/China) Contractors/external staffing 60% 20%
    • Addressing Application Lifecycle Management gaps Customers! Line of Business! Dev & Test Teams! Operations Team! 2nd Gap! Desire for fast and continuous innovation! Requirements! Business Services! Code & Tests! Dev! Ops!
    • With only Agile Development improvements… Agile Dev" Functional Testing Acceptance Testing Operator Production Setup (weeks) Install CI builds are piling up Test and Ops teams have increased pressures to keep up with increased loads but continue to use waterfall approaches and traditional tools.
    • Why DevOps? Failures  due  to   differences  in  dev  and   ops  environments   Time  to  market  pressure   for  more  frequent  releases   Who did this last time? Dev Daily Build Prod Release 14 Manual  (tribal)  processes   Major  releases  take  days,   for  release  lack   100  people  and  are  managed     repeatability/speed   by  a  spreadsheet   Dave… Dave’s not here man… I’ll order breakfast
    • What is DevOps? DevOps is an enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback 15
    • What is DevOps? DevOps is an enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback •  Everybody does it 16
    • What is DevOps? DevOps is an enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback •  Everybody does it •  Software working in production 17
    • What is DevOps? DevOps is an enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback •  Everybody does it •  Software working in production •  Build Agility across the enterprise 18
    • What is DevOps? DevOps is an enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback •  •  •  •  19 Everybody does it Software working in production Build Agility across the enterprise Knowledge flows from right to left
    • Agile Development and Delivery Continuous Integration extends to Continuous Delivery Build Design Agile Dev Publish Test Test Dev Ops Monitor Prioritize Continuous Feedback Deploy
    • DevOps Principles & Values §  Automate deployments to test environments (Int, QA, UAT etc.) –  Generate confidence in the applications and your ability to deploy –  Remove human variability –  Fine granularity of deployment Develop, integrate, build, deploy and test in small work packages §  Test in production-like environments –  Use virtualized environments for testing but also use real databases, queues, host systems etc. §  Document the strategy – automatically –  Provide a full audit trail of all deployments including the content and operations used §  Treat deployment as a part of the development lifecycle –  Not ‘something done by someone else’ People –  Architectural awareness Process Information
    • A Continuous Delivery Pipeline Business Owners Development Testing Staging Production Customers Ensure applications are production-ready throughout the lifecycle and can be released at any time while minimizing rollback due to quality issues §  Validate on more production-like conditions earlier §  Standardization on processes and assets between Dev and Ops §  Automate hand-offs/promotions to increase velocity through the different stages §  Automated monitoring and dashboarding of quality and performance against service level agreements at multiple stages 22
    • DevOps Adoption §  What is the value to you of integrated delivery management ? –  Build a Business Case §  Extend the cross team collaboration / break down the ‘team’ barriers –  People – Processes – Tools §  Identify Capabilities and practices to Adopt / Enhance –  Include deployment considerations at all times 23
    • DevOps Adoption – 1 / 2 §  Requirements Management –  Requirements Management and communication across Development and Operations §  Versioning of all DevOps assets –  Versioning of Deployment Scripts and Source Code §  Access to Production-like Environments –  Documentation of Production-like environments as Patterns –  Developers have ability to launch and destroy production-like environments from these patterns §  Deployment Automation –  Pattern based reusable deployment scripts –  Ability to deploy applications in One-step –  Daily deployment and verification of applications to a production-like environment 24
    • DevOps Adoption – 2 / 2 §  Change Management –  Linking bugs, issues and work items to application changes –  Linking production issues to associated deployment bugs §  Automated Testing –  Automated testing is used to validate application and platform function and characteristics §  Monitoring –  Monitoring Deployed applications to validate performance and reliability §  Delivery Pipeline –  Having a dashboard to track application stages thru the delivery pipeline and track deployment velocity 25
    • Continuous Delivery Adoption Maturity Common Source Control Automated Builds (Build Definitions) Continuous Integration (CI) Automated Delivery Continuous Delivery to Test Continuous Delivery to Production-like Systems Continuous Delivery through to Production 26
    • IBM UrbanCode Deploy Deployment Automation Deployment of Applications through Environments §  Rapidly deliver to multiple environments for testing §  Visibility into deployment status via dashboards §  Easily roll back applications due to errors or changes §  Compliance via audit trails and security §  Integrated with existing investments (Open Source, Tivoli, Cloud, Microsoft, Commerce, Portal) Application Blueprint Versioned Artifacts Artifacts Deploy or Rollback Artifacts Deploy or Rollback Artifacts Deploy or Rollback Execute Against Execute Against Development Environment 27 Execute Against QA Environment Production Environment
    • IBM UrbanCode Release Release planning and orchestration Collaborative release management solution : §  Replaces error-prone manual spreadsheets and streamlines release activities §  Orchestrate release of multiple applications across multiple environments §  Centralized release processes control desk with real-time status §  Environments-to-releases allocation 28
    • IBM UrbanCode Release – Release planning and orchestration Collaborative release management solution that replaces error-prone manual spreadsheets and streamlines release activities §  Orchestrate release of multiple applications across multiple environments §  Centralized release processes control desk with real-time status §  Environments-to-releases allocation 29