Modernize Development with Agile Engineering Practices
Download as PPTX, PDF0 likes581 views
This document discusses modernizing development with agile engineering practices. It introduces Kevin Hancock, a senior director at CollabNet with over 15 years of experience helping large organizations transform into agile teams. The presentation covers establishing upstream practices like Scrum and downstream practices like continuous integration (CI) and continuous delivery (CD). It emphasizes establishing the right people, processes, and tools to connect teams and provide visibility and governance across the development lifecycle.
Modernize Development with Agile Engineering Practices
- 1. Modernize Development with Agile Engineering Practices Sept 2016
- 2. 2 Presenter Kevin Hancock, Senior Director Worldwide Field Operations In his fifteen plus year at CollabNet, Kevin has led successful implementations of CollabNet products and services at some of the world’s largest enterprises. Kevin works with organizations to transform their globally distributed application development teams into modern, agile organizations, helping to save millions of dollars while accelerating software delivery. Kevin holds a Bachelor of Science degree from Carnegie Mellon University, and a Masters degree from the University of Pittsburgh. • 20 years working in IT with the last 15 focusing on Development Organizations • Experience with 1000’s of developers and 100’s of development teams • Practical knowledge of building development communities across organizations
- 3. 3Source: 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
- 4. 4 Upstream “Must Haves” The daily standup Reports accessible to all stakeholders Put Product Owners in charge Break requirements into small chunks, iterate and collect feedback. Connect Agile projects to enterprise PMO planning and reporting. * “How Can You Scale Your Agile Adoption?” by Diego Lo Giudice, February 5, 2014 Forrester
- 5. 5 Downstream “Must Haves” Build and Integrate Build, automate, and commit daily Test Shift to the left; automate unit testing. Deliver and deploy Per change * “How Can You Scale Your Agile Adoption?” by Diego Lo Giudice, February 5, 2014 Forrester Code Review Rules determined by needs of team
- 6. 6 The reality Proliferation of unconnected teams, processes and tools • Limit agility and scale • Block visibility and governance • Tie up resources
- 7. 7 CollabNet at a Glance 10,000+ customers, proven in global deployments as large as 80,000 users and 1 billion commits Leader in open-source based application lifecycle management, version control, DevOps, and agile solutions 250 employees across the globe Founded in 1999; HQ in South San Francisco, CA March 2016
- 8. 8 Focus on People, Processes, Practices Agile and Certified Scrum Training and Coaching Workshops SVN and Git Applied Workshops DevOps Applied Workshop Agile Development Applied Workshop
- 9. 9 And Tools . . .
- 10. Agility and Foundation for DevOps Section 2
- 11. 11 DevOps Underpinnings* Dev Ops * The Phoenix Project by Gene Kim MonitorDeployBuild & TestCodePlan 1. Left to right flow of work from business development operations 2. Constant flow and feedback 3. Creating a culture that fosters continual experimentation and learning
- 12. 12 DevOps Needs Culture Automation Measurement Sharing Build trust through transparency Unite around the business’ goals and objectives Don’t point fingers, fix problems Leverage existing investments Provide easily used templates for common tasks Actions and events triggered as part of workflow Common KPI’s across organization Personae based dashboards for better understanding Trends to measure improvement Cross team and cross organization sharing Feedback loops at all stages that allow actions to be taken Put actions and events in context
- 14. 14 Distributed and Centralized SCM
- 15. 15 Code Practices * 2016 State of DevOps Report Chapter 4 Page 31 by Puppet + DORA
- 16. 16 Branch and merge feedback Staycloseto TrunkMergeDaily master release-3.0 GUI-integration feature-23 COMMIT-BASED REVIEWS PULL REQUEST Branches are protected and require reviews • Pushes trigger a review • Organizations set up rules around reviews
- 17. 17 CollabNet Approach SVN and Git federation and replication 24x7 support On-premise or in the cloud IP Security Governance • Security and RBAC • Central repo management • History protection • ALM tool integration • Audit compliance • Workflows and code reviews Master Flexibility, Visibility and Governance
- 19. 19 Testing Pyramid Unit Service UI CostandRuntime The higher we go . . . • The more unreliable • Greater cost • Slower feedback * Concept by Mike Cohn - https://www.mountaingoatsoftware.com/company/about-mike-cohn
- 20. 20 What is Continuous Integration?
- 21. 21 What we see . . . Source CodeBuild scripts 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 Downstream Dependents ? Project A Build Process Project B Build Process ? ? ? ? ? ? ?
- 22. 22 Desired State Source CodeBuild scripts 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) Downstream Dependents Binary Artifact Repo (Nexus/Artifactory)
- 23. 23 TestLink Integration Tester creates multiple Test Cases for a Test Suite Test Suite Test Cases Test Plan Defects Tracker Req. Tracker Test Suite automatically created per requirement Tester creates Test Plan for a build that holds multiple Test Cases Defects automatically created for failed Test Case Build/ Binary
- 25. 25 CollabNet Approach Continuous Business Planning Continuous Monitoring and Operations Continuous Testing Collaborative Development Continuous Release & Deployment MonitorDeployBuild & TestCodePlan Continuous Life Cycle Integration Traceability, Visibility & Automation
- 26. 26 TeamForge Platform Event Data Store Trackers Project / Portfolio Administration Collaboration Run time Event Mgmt. Operational Data StoreTool Chain setup Teams Users Roles/Perms Event Sources Associations Domain Objects Activities Universal Search Native Artifact UI Lifecycle Reports Federated Tool UI Activity Streams Pipeline Monitors External Listeners Notification Activities, Objects, Associations Events Events User Workspace Configure Configure Store Federated Tools Native Artifacts Custom Objects
- 27. 27 TeamForge Capabilities Reporting & Governance search traceability documents wikis discussions Release Test Build Track Code Plan My page Reports Projects Monitoring My settings Open ALM Collaboration Architecture Communities My workspace Deploy GitEye EventQ Process Templates Dashboards & Report Catalog Desktops • Integrated ALM development and collaboration tools • Flexible and repeatable process templates • Cross-project collaboration architecture • Reporting & Governance Track Actions throughout the lifecycle
- 28. 28 Demonstration
- 29. 29 CollabNet Solution Value Leverage the tools developers want to use Visibility and traceability across actions, activities, and events Standardize agile development practices to increase velocity Reports, dashboards, and actionable insight into your releases
- 31. Thank You