Selling DevOps style
•Transferir como PPTX, PDF•
12 gostaram•5,480 visualizações
Fun look at Promoting DevOps in the Enterprise
Recomendados
Mais conteúdo relacionado
Mais de Paul Peissner
Mais de Paul Peissner (14)
Último
Último (20)
Selling DevOps style
- 1. DevOps Style Paul Peissner v5a Please use this with the DevOps Style Survey at https://www.surveymonkey.com/s/DevOps-style
- 2. DevOps Style A New IT Model That's Gaining Traction This was designed to be taken with the DevOps Style Survey at https://www.surveymonkey.com/s/DevOps-style
- 3. Selling ‘Just-Enough’ DevOps Is there… • Vision & Awareness • Compelling Events • Support & Sustainability Don’t try to boil the ocean… Do you have… • Driving Pain or Need • Means & Motive • Champions & Sponsors
- 4. 3 Layers & 3 Roles in Enterprise DevOps • People & Culture • Process & Flows • Products & Tools • Practitioners (Engineer, etc..) • Managers/Team leaders • Executives/Line of Bus. Know what you want to do and who needs to be involved… IT Layers… IT Roles…
- 5. People Culture Process Flows Products Tool-chains Practitioner Mgr/Leader Exec/LOB Playing Enterprise DevOps - Tic Tac Toe Define “your” success… STANDARIZATION Exploration
- 6. People Culture Process Flows Products Tool-chains Practitioner Mgr/Leader Exec/LOB Me/Myself - Practice Personal Education Socialize Collaboration Cross-team trainings Explore beyond legacy Collaboration Coaching Innovative pilots & new hybrid flows Playing Enterprise DevOps - Tic Tac Toe Is it just another “special silo” or is it viral DevOps success?
- 7. People Culture Process Flows Products Tool-chains Practitioner Mgr/Leader Exec/LOB Playing Enterprise DevOps - Tic Tac Toe DevOps Legacy Us vs. Them - Project(s)Avoid fighting with the 30 year old, 800 pound, legacy gorilla, if you can! Personal Education Socialize Collaboration Cross-team trainings Explore beyond legacy Collaboration Coaching Innovative pilots & new hybrid flows
- 8. People Culture Process Flows Products Tool-chains Practitioner Mgr/Leader Exec/LOB Playing Enterprise DevOps - Tic Tac Toe Corp Initiative - New IT Models Systems Thinking Leadership Leaders & innovation can be destroyed when there is no support! Personal Education Socialize Collaboration Cross-team trainings Explore beyond legacy Collaboration Coaching Innovative pilots & new hybrid flows
- 9. Systems Thinking Leadership Personal Education Socialize Collaboration Collaboration Coaching Innovative pilots & new hybrid flows People Culture Process Flows Products Tool-chains Practitioner Mgr/Leader Exec/LOB Me/Myself - Practice Us vs. Them - Project(s) Corp Initiative - New IT Models Playing Enterprise DevOps - Tic Tac Toe STANDARIZATION Exploration Legacy DevOps What is DevOps success? You, team, dept., company? Cross-team trainings Explore beyond legacy
- 10. The BIG “CHANGE” Challenges • Software, Technologies, Architectures… • Methodologies, Processes, Deployment modes… • Organizational structures, IT responsibilities, IT reward systems… • Business models, customer needs, market dynamics, security… • Established practices, routines, legacy systems, incumbent projects… • Blind-spots, Schools of thought, legacy Best-Practice, dated knowledge… • Protecting vested interests, politics, loyalties and fear of the unknown… • Executives vs. Employees (Too much, too little, too fast, too slow, unneeded, critical, viral…) • R&D / Development vs. the Business teams (Needs more, needs less, new direction…) Be patient, Win support, in the right time and the right way! Change-inevitable evolutions Change-resistant (organizational) tendencies Change-balancing tensions – Change Cadences & Needed Stability
- 11. The BIG “Culture and Community” Challenges Managing 4 Types of Work Exploring flexible Agile models Business Projects & Internal Projects Scrum, Kanban, Planned Changes & Unplanned Changes Lean, XP, Scrumfall… - Unplanned Changes Lean, XP, Kanban? Business Projects - Planned Changes Scrum, Scrumfall, Lean? Internal Projects - Unplanned Changes Kanban? Community Motivation / Culture Shaping 1. WHAT – Provides logical process guidelines – Efficiency & skills mastery 2. HOW – Empowers ownership and innovation – Effectiveness & collaboration 3. WHY – Evokes emotion and vision loyalty – Motivation & significance Community vs. Culture • Community – group of people… • Culture – the shared values and beliefs … Simon Sinek’s Golden Circle
- 12. Cultural Transformation in the Enterprise The BIG “Culture and Community” Challenges Community vs. Culture • Community – group of people… • Culture – the shared values and beliefs … 1. Core VALUES 2. Business benefiting GOALS that align with your values 3. PRACTICES, PROCESSES & FLOWS that support your goals 4. PEOPLE, SKILLS and NEW REWARD SYSTEMS that can support the practices, processes and flows Managing “Power” Transitions (Collaborative vs. defensive/competitive) Monitor and evaluate the adapting and changing cultures Define Established vs. Emerging (Communities, Cultures and Beliefs)
- 13. Typical feature “use” of traditional BIG software Standish Group Study Reported at XP2002 By Jim Johnson Chairman The BIG Traditional Software Challenges… (Waterfall, Complex Mega-projects & Feature-rich Legacy Apps)
- 14. Limit Scope, Optimize Dev & Teach the business Agile’s iterative cycles and the “chunking” efforts… …helps development and the business to prioritize for the best ROI… …and know when to stop!
- 15. Agile – Process Alignment (Development & Customers) The Lean Startup Steve Blank and Eric Ries Customer Development Agile Product Development
- 16. Some Agile / DevOps Innovation Ideas to consider Big picture – systems fixing is the slowest but best way to change the organization Leverage “systems thinking” and… • Re-use existing assets or processes in new, improved or novel ways… • Re-use projects templates, resources and build inter-related, self-reinforcing eco-systems. Avoid building one-off, net-new or stand alone projects • Support and promote ideas that “create value” for existing offerings/markets • Avoid “new non-aligned” widgets that promote random and “zone” disrupting (less continuous train-of-thought). The lack of continuous (flowing) innovation can have a long-term impact • Involve business users in design and development conversations – teach them about software capabilities • Address individual issues and then figure out how to fit them together
- 17. What is your organization ready to address? 1) Agile IT culture enablement – Open Source & Tools, Collaboration, EDU. & Vision 2) IT process alignment – Integrations, Training, Process & Standardization 3) IT performance optimization – Pilots, Coaching, Simplify Platforms/System flows 4) Business Value and/or Business Growth - Dev Code re-use, project templates, process optimization … - Ops automation, monitoring, standardization & simplification… Corporate Effort Amount of organizational support needed Business ROI Visible Business value and benefits $
- 18. Going Viral – Getting Support and Buy-in Example: Agile / DevOps 2- Way Agreement (Leader to a Developer) Company-wide… - we’re investing in Software to drive a high value ROI - we’re embracing Agile (DevOps) to drive hyper-productivity As a team leader… - I will promote, preserve and enhance our team and… • Protect our team’s knowledge and learnings for years to come… • …for the sake of our future needs - the org., users and not-yet-hired co-workers - I will invest in your Agile (DevOps) development As a developer… - even if we fail…your NEW skills will be of high “career” value 1 2 3
- 19. DevOps Style Have fun… You may find the DevOps Style Survey helpful too… https://www.surveymonkey.com/s/DevOps-style
Notas do Editor
- The Nature “Viral adoption” is unpredictable and contagious…DevOps as a IT industry phenomenon makes universal sense…but depending where you sit in the Traditional Enterprise IT practice and the pain issues.
- DevOps Enterprise discussions need to make sure there is clarity in all 3 stages of a Successful and Sustainable adoption.Compelling Pain – What and where is the energy coming from that is encouraging a DevOps conversation… - What are the “Current State” drivers that can help drive “behavior and process change” discussions.Compelling Opportunity – Is there a “high profile or high value” project that can be the “pilot” for a different model?Is there a funded project with reasonable “Time, Resources, Reward, Value and Support” to experiment with?Is there a planned retrospective that can compare old v. new, traditional v. modern, flexibility v. inflexibility, etc…Compelling Roadmap – Is there a corporate initiative, champion, urgency that can access value and success?Is the enough structure and support to standardize and adopt integration/hybrid practices.Is there a “voice or a single figure” who embodies the transformation efforts (a benevolent dictator) to resolve roadblocks
- People discussing DevOps need to remember that there is 30+ years of IT tradition, practices and careers that can blindly and unknowingly resist the ideas and values that DevOps promotes.Processes change discussions can cause fear and frustration when talking about the process the “is” driving the business todayProducts and tool chains can have profound “affinity and loyalty” with individuals because they are comfortable, knowledgeable and proficient with the established tools…even if the lifecycle of value has long passed Practitioners – need to become more cross-discipline and total process knowledgeableManagers – need to maximize efficiency, collaboration, adaptability and team development to help the businessExecutives – need to invest in processes that provide the “business” with software driven advantages and growth
- Enterprise DevOps discussion can go many different ways but in my opinion…A successful Enterprise DevOps discussion needs to transition from exploration to standardization across all 3 layers and involve ALL personas!
- Practitioner sponsored DevOps tends to focuses on… Direct relationship collaboration and problem solving This can drivestrong IT loyalties and “favor-based” networks…that can produce “silos” down the roadStage by stage enablement within the “IT” organization It tends to involve business teams “after the fact” and supports the idea of simply a “Lower Cost-center” IT modelInnovations, knowledge and information tend to “live” and are celebrated “in the moment” by “clever” owner/innovatorsHistory, Processes and Long-term sustainability are often “devalued” as new found flexibility is over-exercised
- Team leaders tend to focus…Their group and “the” project creating unique environments for successTeam leaders need to invest in “changing” practices for all groups to benefit from their effortsTeams to be competitive and even combative when confronted by established projects, legacy systems and traditional practicesIn the earliest stages “new” processes are “most” vulnerable and can be sabotaged and disrupted…making success impossible. Avoid threatening the established status quo openly. Lead by example and “invite” others to join. Teams can be “inspired” to do things differently…But you are not fighting internal teams…Your are one (IT) team enabling “business technologies” to help your “business teams” to compete and achieve success
- Executives tend to focus on Culture leaders - Inspiring people to change and follow with great ideas and vision Often because the system and current practice seem to be change-resistant and innovation-killing by default Process leaders - Give voice to the evolution that appears to be driving the efforts from various process improvementsTend to look internal to incremental changes that can drive “segment” specific optimizations Technical leaders – Can drive system wide changes that have huge potential But with the support of the IT culture or pacing the cadence of changes they can end up frustrating the organization
- Know who and what you are (and are not) dealing with in a DevOps conversation….Drive for standardization over time and across the organization….
- Budgets, investment, buy-in and support has to grow as DevOps evolves to eventually become a “BUSINESS” value…
- From a Project, Leader and Developer perspective Waterfall is much more high-risk and costly…