Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
Welcome. Techtown Training Web Seminar series
Intro to DevOps for Project Managers
Today’s Presenter :
• Chris Knotts, PMP – New skills evangelist, product manager, enterprise training specialist – Techtown Training
DevOps & Project Managers – We will discuss:
• Level-set: “What is DevOps?”
• A typical enterprise environment and the life cycle of IT and software delivery projects
• Agility: the bridge to DevOps
• Continuous delivery and incremental workflows
• Major implications for IT project mangers
What is DevOps?
Source: www.devopsdays.com
Attribute Key Elements
High-trust, high-
performance culture
IT capabilities =
strategic assets, not
cost centers
Highly automated
processes; mature
deployment pipeline
Continuous delivery of
software and IT value
Commitment to
continuous learning
& improvement
Unified mission; aligned incentives across departments and
teams; little fear/failure/blame, high quality of work life
Projects, features and work flow through fast cycles times,
systems are “anti-fragile,” IT processes & capabilities are
aligned with overarching organizational needs
Technical phases of projects supported by common tools
and automation processes, collaboration replaces handoffs,
codebase/IT infrastructure is agile and functional by default
Features, projects and IT work follow a regular, iterative flow.
Cycle time is short, workflow favors small frequent changes
Disciplined feedback loops quickly travel back upstream for
inclusion. Tools for monitoring, measurement and alerting
implemented & effective. Shared knowledge repositories.
DevOps IS…
A simplified look at the enterprise
s s
S e c u r I t y, G o v e r n a n c e S e c u r I t y, G o v e r n a n c e S e c u r I t y, G o v e r n a n c e S e c u r I t y, G o v e r n a n c e
Business Customer
Application
Development teams IT Operations, Production
Environments, Support
Change Management
A simplified look at the enterprise
An Agile review
The Agile Manifesto (2001): We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
That is, while there is value in the items on the right, we value the items on the left more.
Individuals and Interactions
Processes and tools
Working software
Comprehensive documentation
Customer collaboration
Contract negotiation
Responding to change
Following a plan
OVER
OVER
OVER
OVER
1. Without a common goal, you will never achieve 2. Commit to values first…the practices will follow 3. Implementing DevOps (or any new way or work) is about
LEARNING…not getting it perfect 4. Agile practices allow adaptability and predictability 5. Articulate a vision and get buy in from your internal
customers 6. Find the MINIMUM requirements for a solution! 7. Optimize the whole! Limit work in progress (WIP)
anywhere possible 8. Build great teams
Lessons from Agile
A simplified look at the enterprise A simplified look at an enterprise Welcome to the 21st century!
Every member of a cross-functional team is responsible for the delivery process.
• One of the most important goals of a continuous delivery environment is to attach responsibility for the successful deployment of a piece of code (be it software features or infrastructure code) to the person who developed it
• Everyone is responsible for quality!
• When something is wrong (an outage, a broken build, a bug) the entire team’s priority becomes fixing it
• Let’s discuss how this works in the context of continuous integration and continuous delivery
The deployment
pipeline concept
Source: Continuous Delivery: Reliable
Software Releases through Build, Test,
and Deployment Automation
Continuous Delivery Maturity Matrix
Obvious (and important) implications for project managers…
Plan-driven corporate behavior
50% of defects introduced
here
A disruptor: Unique attributes of software as a product of work
Application Delivery & Cost of Defects
Equalizing Requirements
One of the most important tools of DevOps: Failure
Getting from: To: Failure is not a cause for blame, it is a vehicle for change, learning, and improvement.
Quality and testing
The “Iron Triangle” of Constraints
The “Agile Triangle”
Source: Jim Highsmith, Agile Project Management (2nd Edition)
Jason Bloomberg, Intellyx
http://insights.wired.com/profiles/blogs/the-devops-drumbeat-rethinking-the-iron-triangle#axzz42wCYG2EG
Jason Bloomberg’s Agile Architecture “Quality Star”
Jason Bloomberg’s Agile Architecture “Quality Star”
To sum up:
• Stakeholders are oriented around teams and projects
• Quality is tied to value – and is everyone’s responsibility, from requirements and code creation to deployment
• Technical non-functional requirements (and technical debt) receive equal priority to functional requirements
• Deliver often, deliver early, learn and adapt. Roll planning into your continuous processes
• Testing and QA is not a separate function: it is a key enabler of continuous delivery
• Expect failure and plan for the contingency
Thank you!
Tweet to us: @techtown_IT @chris_knotts
Today’s activity awards 1 PDU Today’s PDU: One Category A Management PDU (professional development unit) - WS031516 from provider 2161, ASPE.