Scribd
Upload
179 views

Devops Implementation For XXX Project

The meeting agenda covers adopting DevOps principles and practices to address problems with a project. It will discuss the current problem statement, DevOps values that can help, practical application to the project, shifting from big to small batches, and involving teams in value stream mapping. Action items include educating teams on DevOps, understanding the current process, setting targets to reduce times, and continuously improving using a Plan-Do-Check-Act approach while measuring outcomes.

Uploaded by

sekhar A
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
179 views

Devops Implementation For XXX Project

The meeting agenda covers adopting DevOps principles and practices to address problems with a project. It will discuss the current problem statement, DevOps values that can help, practical application to the project, shifting from big to small batches, and involving teams in value stream mapping. Action items include educating teams on DevOps, understanding the current process, setting targets to reduce times, and continuously improving using a Plan-Do-Check-Act approach while measuring outcomes.

Uploaded by

sekhar A
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Meeting Agenda :

1. Problem Statement for XXX Project-5 minutes

2. Dev-ops principles and Values which can address the


Problem Statement-7 minutes

3.Practical Application of the same to our Project and results-


8 minutes

4.Shifting from Big Batch to small Batch-5 minutes

5.Value Stream mapping and involvement of Project teams-5


minutes
Opening Pitch:
Problem Statement for xxx Project:

1.Slow Approval Process which kept testing teams waiting for the build
2.Recurring defects due to branching issues
3.Each team not working in collaboration with the other throwing the
problems in to each other courts
4.Reduced morale, reduced Performance and Productivity of the teams and
Potentially loss of Customer Faith
DEV-OPS Principles and Values

 Teams do not work in silos they follow a collaborative Approach


 Manual execution of Tasks are replaced by Automation where ever
Possible
 Development teams and Operations Team are working together in order
to get early feed back of deployment Issues
 Automated emails are generated and sent to concerned Teams in order to
look in to the issue faster
 Failing fast, Early Feedback and Succeed soon in the life cycle
 Decreased turn Around time for issues,faster deployment and smaller
deployment and smaller batches
Real time Implementation of Dev-ops
for xxx Project
 Adopt Improvement KATA/A3 Framework to Plan,DO,Check and Act for xxx
Project
 Estimate the Timelines and start with Pilot Teams ex:1 Team out of 4 Teams
 Identify the tools and things which can be Automated
 Shift from Big Batch to small batch deployments
 Adopt frequent deployment cycles by using tools and automated scripts
 Involve Dev,Testing,Ops Teams to work in collaborative mode
 Measure the value delivered,ROI and Market share
Anticipated Value:
 Spend more time on Planning and Analyzing things. Involve more People and take
effective feedback and find out the loopholes in the system
 Say for 1 month we do this exercise(Mar1-Mar31st)
 Identification of Tools and Code that can be automated needs to be identified.
Involve an automation team for the same and Provide them the start and End
dates(APr1st to APr3oth)
 Define the Process, Decide the Deployment Frequency, Shift form Big Batch to
Small Batches(May1st to may31st)
 Arrange Workshops and Educate the Team, Make sure all the different teams which
were working in Silos are now working in Collaborative mode(Jun1st to Jun30th)
 Kickoff the pilot Project with DEVops Process-July 1st
 Verify various metrics to Improve the Process Continuously
Ex:1.Deployment frequency,2.Change volume,3.Deployment time,4.Lead
time,5.Customer tickets,6.Automated test pass %,7.Defect escape
rate,8.Availability,9.Service level agreements,10.Failed deployments,11.Error
rates,12.Application usage and traffic,13.Application performance,14.Mean time to
detection (MTTD),15.Mean time to recovery (MTTR)
Moving from Big Batch to Small Batches:
 Minimum Viable Product can be Produces which can deliver a Value to
the Customers
 Many Product Increments leads to the Ultimate goal of the project
 Experimental Approach leads to Continuous Delivery to the customer
seeking early feedback
 Moving from Linear to lean(Feasible,Valuable,Usable,Delightful)
 Lower Risks of Deployment
 Improves Efficiency
 Increases Motivation and Urgency
 Reduces Costs
 Minimize Schedule Impacts
Value Stream Mapping:

 Fact Based Technique to show how value flows through the Organization
 Can Assess the current Condition of Cycle Time/Lead Time
 Document Step by Step Process of Current state of the Project
 Estimate the time taken for each of the Processes involved including the
wait time
 Document Future State by removing the Wait times
 Measure the Cycle Time and Customer Satisfaction
 Helped to set Target,experiment,measure impacts
 Include entire Team,Team members and Leaders
Example:
 Software is transforming the priorities of business in every industry. Consider how
Tesla has disrupted the automotive industry, how Airbnb has changed the world of
hotel bookings and vacation rentals, and how Uber has turned the taxi business
upside down. Each of these companies led with software that created an entirely
new experience for the customer.
 This radical shift has caused traditional companies in all sectors, and even
government organizations, to innovate and compete. They know that better
customer experiences fuel business, and software lets them deliver those
experiences to win, delight, and keep customers.
 As organizations work to deliver better digital experiences through faster, higher-
quality software, process innovation in the software development industry with
agile and DevOps has become a higher priority for tech executives. DevOps tools
and practices make it easier for companies to offer continuous delivery, continuous
integration, continuous testing, continuous monitoring, and continuous feedback.
To get that continuous feedback, you need metrics. Value stream mapping can help
with that.
Action Plan for XXX Project

1. Conduct Workshops to make the Team Understand


the Importance of Dev ops and its Principles and
Values

2. Make them understand the various Frameworks of


Devops and figure out which methodology is
applicable for the team

3.Understand the Agile and Lean Principles


Action plan continued:

 Understand the Problem Statement by assessing the Current state of the


Project
 Estimate each Process area of concern and capture the timings including
the lead and lag times
 Set a Target for the future and note down the improvements to be brought
in the system
 Adopt Plan,DO,Check and Act technique to see whether we are following
the Road map and ensure we achieve the success.
 Assess my measuring cycle time,Increased,Productivity,Customer and Team
satisfaction levels and Success rates.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy