Learning Objectives :
# Understand what is Devops, why devops and what is it’s history
# What are it’s core principles and practices
# Understand key steps you need to take if you are planning to implement Dev-ops in your organization
Instilling DevOps ways of working requires transforming a culture from one that is highly siloed and relies on overly complex processes to one that emphasizes collaboration, empowerment, continuous delivery and flow. This transformation is not easy for large enterprises and requires gradually establishing new attitudes while forming expected outcomes. A DevOps "dojo" approach can be used to immerse individuals and teams in the new ways of working through hands-on learning and coaching to help make the changes stick. While challenges will be experienced, the transformation aims to benefit the organization by enabling more frequent delivery of value to customers.
DOES15 - Ramona Jackson and Aji Rajappan - Continuous Delivery at Cisco ITGene Kim
Cisco IT implemented a large-scale continuous delivery transformation to improve software quality, optimize costs, and accelerate time to capability. Their approach included establishing a core team, adopting agile methodologies, automating testing, embedding subject matter experts, and grouping applications into adoption waves. Key results were increased agile adoption rates, productivity savings, and measurable business value. The transformation required addressing needs like environment refreshes and concurrent code versions, as well as focusing on areas like tools, training, processes, and culture change.
How (can) Scrum and DevOps Walk Together to Build a High-Quality Product Deli...Scrum Day Bandung
Discussion in fishbowl format to find out how Scrum and DevOps should more power-full if we use it together and properly, then validating with data and convergence of CEO Scrum.org and CEO DevOps Institute.
Being Agile, Doing Agile and Agile in Crisis: We have the Agile Industrial Complex, Dark Agile, Faux/Fake Agile, Zombie Scrum, Flaccid Scrum, CrAgile, FrAgile, WAgile, and more. What do they all mean, and how do we know if we are doing them instead of "Being Agile"
The document discusses achieving sustainable agility at scale. It begins by introducing Ahmed Sidky and his experience in agile transformation. It then presents a hypothetical scenario of a CIO trying to quickly transform a large IT organization of 3,000 people to agile. However, the summary notes that the CIO's plan focuses more on process change than culture transformation and may not lead to sustainable organizational agility. The document goes on to discuss the differences between industrial and knowledge work mindsets and fixed versus agile mindsets. It emphasizes that agile is first a mindset described by values and principles before specific practices. Achieving organizational agility requires transforming the entire organizational culture and ecosystem, not just processes.
Think that DevOps is just for product? Think again.
In this webinar, ITSM expert John Custy shows you how to apply DevOps principles to your IT org. This event is for anyone involved in the support and development of IT systems and services. The keys to higher-performing services are so simple, they might surprise you.
Watch the full webinar here: http://atlassian.com/help-desk/how-to-run-it-support-devops-way
Brought to you by JIRA Service Desk. Learn more: http://atlassian.com/service-desk
Explore what is an Agile culture
Explore the Agile Mindset
Explore what is an Agile culture
Explore the Agile Mindset
Review the 6 basic steps required to transition to an agile culture that will accept the Agile Mindset
Instilling DevOps ways of working requires transforming a culture from one that is highly siloed and relies on overly complex processes to one that emphasizes collaboration, empowerment, continuous delivery and flow. This transformation is not easy for large enterprises and requires gradually establishing new attitudes while forming expected outcomes. A DevOps "dojo" approach can be used to immerse individuals and teams in the new ways of working through hands-on learning and coaching to help make the changes stick. While challenges will be experienced, the transformation aims to benefit the organization by enabling more frequent delivery of value to customers.
DOES15 - Ramona Jackson and Aji Rajappan - Continuous Delivery at Cisco ITGene Kim
Cisco IT implemented a large-scale continuous delivery transformation to improve software quality, optimize costs, and accelerate time to capability. Their approach included establishing a core team, adopting agile methodologies, automating testing, embedding subject matter experts, and grouping applications into adoption waves. Key results were increased agile adoption rates, productivity savings, and measurable business value. The transformation required addressing needs like environment refreshes and concurrent code versions, as well as focusing on areas like tools, training, processes, and culture change.
How (can) Scrum and DevOps Walk Together to Build a High-Quality Product Deli...Scrum Day Bandung
Discussion in fishbowl format to find out how Scrum and DevOps should more power-full if we use it together and properly, then validating with data and convergence of CEO Scrum.org and CEO DevOps Institute.
Being Agile, Doing Agile and Agile in Crisis: We have the Agile Industrial Complex, Dark Agile, Faux/Fake Agile, Zombie Scrum, Flaccid Scrum, CrAgile, FrAgile, WAgile, and more. What do they all mean, and how do we know if we are doing them instead of "Being Agile"
The document discusses achieving sustainable agility at scale. It begins by introducing Ahmed Sidky and his experience in agile transformation. It then presents a hypothetical scenario of a CIO trying to quickly transform a large IT organization of 3,000 people to agile. However, the summary notes that the CIO's plan focuses more on process change than culture transformation and may not lead to sustainable organizational agility. The document goes on to discuss the differences between industrial and knowledge work mindsets and fixed versus agile mindsets. It emphasizes that agile is first a mindset described by values and principles before specific practices. Achieving organizational agility requires transforming the entire organizational culture and ecosystem, not just processes.
Think that DevOps is just for product? Think again.
In this webinar, ITSM expert John Custy shows you how to apply DevOps principles to your IT org. This event is for anyone involved in the support and development of IT systems and services. The keys to higher-performing services are so simple, they might surprise you.
Watch the full webinar here: http://atlassian.com/help-desk/how-to-run-it-support-devops-way
Brought to you by JIRA Service Desk. Learn more: http://atlassian.com/service-desk
Explore what is an Agile culture
Explore the Agile Mindset
Explore what is an Agile culture
Explore the Agile Mindset
Review the 6 basic steps required to transition to an agile culture that will accept the Agile Mindset
This document discusses agile metrics for measuring value, flow, quality, and culture. It presents common metrics used by Scrum teams like velocity, burnup/burndown, lead time, and defects. Flow-related metrics across the development lifecycle are explained, including the differences between cycle time and lead time. The document also discusses measuring value, happiness, culture, and frameworks for metrics like SAFe. Key takeaways are that outcomes rather than activity should be measured, and that culture, collaboration, and safety are important but difficult to measure metrics.
Agile focuses on mindset, culture, and stability while responding quickly to market changes. DevOps extends Agile by adding automation. DevOps is characterized as CALMS - Culture from Agile, Automation from DevOps, Lean from Agile, Measurement from DevOps, and Sharing from Agile. Key principles include continuous delivery, continuous integration, deploying in small batches frequently, and automating to enable continuous delivery.
DevOps culture: Computer scientists are only human ... ;)Jörg Hastreiter
Eye-catching top 10 signs, that you have to change something and DevOps is a possible answer. Typical points of resistance illustrate, that DevOps is a human challenge!
The document discusses agile development models as an alternative to traditional waterfall models. It describes how agile models use iterative development with short cycles to facilitate adapting quickly to changing requirements. Several specific agile methods are listed such as Scrum, Extreme Programming, and Lean Development. The key principles of agile development are close customer collaboration, preference for working software over documentation, frequent delivery of software increments, and ability to accommodate changing requirements.
This document discusses Ahmed Sidky's experience with evolving agile leadership at Riot Games. It describes how Riot decoupled traditional leadership responsibilities across new roles like Team Captain, Delivery Lead, and Product Lead. It also discusses how Riot invested in growing the skills and competencies needed for these agile leadership roles through learning, mentoring and practice. The document provides examples of responsibilities for each role and emphasizes that leadership is about accountability and enabling the team to share responsibility.
Tracking DevOps Changes In the Enterprise @paulpeissnerPaul Peissner
DevOps - Train and Rails theme
Questions to consider when exploring, adopting or scaling DevOps in the Enterprise.
Hybrid models are the "only" option for organizations with legacy business models they must support, while they search for the right balance and strategies to enable DevOps to co-exist with legacy practices.
A 40 minute introduction to DevOps for the Wellington DevOps Meetup, March 2021.
Rob forgot to talk about DevSecOps, which was a fundamental topic, and the general concept of "Shift left". Only so much you can fit in an hour, but they are good topics to research further.
Rob also mentioned some books
IT Revolution DevOps Forum is the best sources of free ebooks about Devops. It costs you an email signup, but it is worth it.
Team of Teams, Stanley McChrystal - good for business agility.
(See also Brave New Work, by Aaron Dignan, as Rob's favourite primer on new ways of working)
The Phoenix Project, by Gene Kim et al. - KoolAid intro to Devops, convinces most people.
Devops Handbook, gene Kim at al - good general refence
Continuous Delivery, Humble and Farley - still the definitive textbook
The Checklist Manifesto, Atul Gawande - in praise of checklists
Field Guide to Human Error, Sidney Dekker - safety culture influences Devops
(see also Dekker's two Youtube videos on Safety Differently and Just Culture)
Rob England consults and trains in IT locally in Welly tealunicorn.com/nwomit
Or see the work Rob and Cherry do together at enterprise level tealunicorn.com/clients
This document discusses an approach to DevOps. It outlines some of the challenges faced in a pre-DevOps environment like SLA violations and burnout. It then discusses how adopting a DevOps mindset can enable faster delivery while maintaining quality. Key aspects of DevOps include treating other teams as customers, establishing feedback loops, and including time for improvement. Metrics like lead time, deployments, and customer satisfaction are important. The document provides examples of DevOps practices from Spotify and references for further information.
Dealing with Shifting Priorities using Lean/Kanban Flow, WIP Limits and Capac...AgileSparks
Many teams suffer from due to conflicting priorities. When today's priority one usurps yesterday's priority one, expensive context switching becomes a problem.
Operations teams are especially hard hit by shifting priorities because of increased variability from supporting ongoing development of new projects while maintaining features & apps in production. Add in unplanned work and security issues and we have a battle between getting new features delivered or keeping production stable. Hence the dilemma DevOps is working to solve.
Dominica will talk about how Dev and Ops teams can use use a Lean flow Kanban approach to limit work-in-progress and allocate capacity for the nature of the demand as a way to address and improve prioritization issues and context switching.
Panel Discussion "Agile and Business Analysis" Dr. Mohamed Salama, Hind Zanto...Agile ME
Agile and Business Analysis (Girvan, L., Paul, D.) was published in 2017 by BCS, The Chartered Institute for IT. This book will be reviewed by two academics (Hind Zantout and Mohammad Hamdan) and the key strengths and weaknesses presented. It is anticipated that a reviewer from industry will join the presenters and contribute the view from industry.
Með tilkomu agile hugbúnaðargerðar er hætt á að forritarar fórni hlutum sem voru sjálfsagðir í aðferðum eins og Waterfall og RUP en eiga fullt erindi í agile þó svo með öðrum hætti. Má nefna skjölun, en margir misskildu agile á þann veg að ekkert þarf að skjala. Skjölun er nauðsynleg þótt hún sé með örðum hætti, en svo er einnig með architecture. Í agile er nauðsynlegt að huga vel að architecture en einnig að átta sig hvað það er sem við skilgreinum sem architecture og hvað ekki.
Í þessum fyrirlestri er fjallað um architecture og agile og hvernig þessir hlutir geta fallið vel saman. Með aglie teymum flyst mikið af ábyrgð á architecture til teymanna, en samt þarf að vera einhver sameinlegur strúktúr og sýn.
Powerpoint from my speak at Agile ME 2017, about how to optimize your agile process, by having an agile approach to your process as well as your product.
This session is an overview on what DevOps is (to me) and how it impacts traditional organizations the most. DevOps is way more than just continuous delivery! From an Agile (synergetic) mindset, DevOps takes a step beyond and focusses on automation, collaboration and learning. Apart from that I also look forward to what oppurtunities lie ahead when implementing DevOps.
On March 2nd I presented this DevOps Unraveled session for abt 40 IT-managers at business university Nyenrode. This was part of the Masterclass Agile management
(Dutch website http://www.executiveeducation.nl/open-programmas/programmadetails/masterclass-agile-management/sectie/introductie.html ).
This document provides an introduction to Agile software development. It discusses the origins and evolution of Agile methods from the 1970s onwards. Key characteristics of Agile include iterative development, emphasis on individuals and interactions over processes, customer collaboration, and responding to change. Specific Agile methodologies like Scrum and Extreme Programming are described. The document also outlines 10 key principles of Agile development such as active user involvement, empowered self-organizing teams, frequent delivery of working software, and collaboration between all stakeholders.
DevOps is popping up in tech circles all over the place. Do you know what it is? How to take advantage of it's benefits? Or where to start. In just a few minutes you can kick-start your shift to a DevOps mindset.
Journey toward Quality Assistance - Agustinus Verdy & FachrulScrum Day Bandung
Continues Integration and Continues Delivery are important in Agile. In this session Very & Fachrul will explain us why CI/CD is no negotiable to build high value product and also deliver a good quality product.
Four pillars of DevOps - John Shaw - Agile Cambridge 2014johnfcshaw
Slides presented at Agile Cambridge 2014 http://agilecambridge.net/ac2014/sessions/index.php?session=57
Session Description:
The emerging practice of DevOps is a natural extension to established Agile methods. The choice of tooling to support the practices is important and will influence heavily how rapid, repeatable and reliable live deployments might be.
Three of the four pillars are concerned with automation through tooling but, arguably, the fourth pillar is more important than the other three together. The fourth pillar is at the heart of the Agile Manifesto: people.
The "Gold Rush" for DevOps is dominated by vendors and the push to sell their wares. But it is people who use the tools, people who define, develop and assure the software, and people who manage the services after they have gone live. One of the cornerstones of DevOps is breaking down the walls between development teams and operations; too much tool specialisation will lead to further separation and even the introduction of yet another silo.
This talk will cover four pillars to DevOps: Environments, Deployment, Testing and People. The insights brought together in this talk were gained under commercial engagements with government clients, on development of financial systems responsible for management of funding in the adult education sector.
Most senior executives in large enterprises believe DevOps and CI/CD are interchangeable. If I have a CI/CD pipeline, I am “doing DevOps”, right? Not exactly. The dilemma that these executives have is that they don’t believe DevOps can be with the people they have. It can be done. I’ll show you how!
5 Keys to Building a Successful DevOps Culture featuring Mandi WallsSerena Software
The document provides 5 keys to building a successful DevOps culture:
1. Set clear and measurable goals that matter to stakeholders across teams.
2. Gain executive support by focusing on goals that benefit multiple teams and influence informal leaders.
3. Start with pilot projects on representative work to practice the cultural and technical aspects of DevOps.
4. Provide training to all teams on new tools and processes while prioritizing the learning work.
5. Continually share progress and successes through various internal and external channels to evangelize DevOps.
The complexity in the simplicity of Agile? by Arie van BennekumAgile ME
Looking at Agile, it is so simple. In fact Agile is just structured common sense. Still so many people struggle to get their success in Agile. What is going on? The point is Agile, with all its simplicity, is based on different paradigms and the old paradigms hinder. The question is, can you identify thew old paradigms and furthermore, how do you change them. Arie van Bennekum will take you in his talk on his 22 years Agile journey and share his experience, successes, his delta’s and IATM, the Integrated Agile Transformation Model he developed for Agile transformations. IATM is a successful Agile change process to (the next level of) Agile he and his teams use doing international Agile transformations.
Killing Agile Software Development : Presented by Rizky Syaiful oGuild .
Last month (June 2016), I helped a well-known higher education institute in Indonesia. I train the lecturers there, so that their students can practice agile software development.
[I show the audience some photos and videos as the proofs]
Can you imagine a condition when all our CS/IT students already get the real experiences of proper Scrum, Automated Testing, etc?
In that imaginary world, agile software development is already the norm! In the other side, there is no more room for Waterfall’s Big-Design-Up-Front style. Because we know that any software problem is inherently a design problem—or complex problem in Cynefin framework. You can’t solve that kind of problem by designing a big-fixed solution up in the front.
And if almost every software development is already agile—as it was visioned back then in 2001 manifesto, why would we still use ‘agile’ term?
We invent words to categorize things. Before ‘agile’ was proposed in the 2001 manifesto, they called it ‘lightweight’. Because it’s different with the previous heavy weight Waterfall.
Now, when I say the word ‘computer’, what would your brain emulate? A mainframe computer? Or a personal computer? Both of them are literally a computing machine. I put my money on personal computer. Because almost everyone see personal computer in daily basis. And they haven’t seen any mainframe computer once in their life.
Just as the dead of ‘personal’ term, in ‘personal computer’—I don’t count PC because that’s an abbreviation—‘agile’ in ‘agile software development’ will also be dead.
Not because it’s bad. On the contrary, that’s because agility the best option for software development.
In 2026 I, believe, we will call it simply as ‘software development’.
Please help the world to reach that kind of utopia, at least by telling your ex-lecturers, “you should teach agile software development properly”.
We should be so proud for standing here. Being a part of agile software development movement, of the 21st century.
Why?
Because a good movement always has a goal,
this agile software development movement also has a clear end.
Appreciative Enquiry : Presented by Sridharan VembuoGuild .
As we all know, Agile, at it’s core, emphasizes on team work. And, if you look at any successful Agile story, the key to it’s success would be a self-oragnized, cohesive team and other factors only add to this.
More often than not, Retrospectives are probably the only forum where the entire team comes together as a single unit and these meetings usually end up being crib (and ranting) sessions. And, because of that, teams are not very enthusiastic about retrospectives and these meetings become more of a ritual than being productive and useful.
As the name ‘Appreciative Enquiry’ suggests, the focus of this meeting was on things that created a positive impact on the team and the project. Sridhar shared few real life examples from his projects, the effective of doing regular Appreciative Enquiries and also guided the participants how they can successfully adopt this technique in their team.
This document discusses agile metrics for measuring value, flow, quality, and culture. It presents common metrics used by Scrum teams like velocity, burnup/burndown, lead time, and defects. Flow-related metrics across the development lifecycle are explained, including the differences between cycle time and lead time. The document also discusses measuring value, happiness, culture, and frameworks for metrics like SAFe. Key takeaways are that outcomes rather than activity should be measured, and that culture, collaboration, and safety are important but difficult to measure metrics.
Agile focuses on mindset, culture, and stability while responding quickly to market changes. DevOps extends Agile by adding automation. DevOps is characterized as CALMS - Culture from Agile, Automation from DevOps, Lean from Agile, Measurement from DevOps, and Sharing from Agile. Key principles include continuous delivery, continuous integration, deploying in small batches frequently, and automating to enable continuous delivery.
DevOps culture: Computer scientists are only human ... ;)Jörg Hastreiter
Eye-catching top 10 signs, that you have to change something and DevOps is a possible answer. Typical points of resistance illustrate, that DevOps is a human challenge!
The document discusses agile development models as an alternative to traditional waterfall models. It describes how agile models use iterative development with short cycles to facilitate adapting quickly to changing requirements. Several specific agile methods are listed such as Scrum, Extreme Programming, and Lean Development. The key principles of agile development are close customer collaboration, preference for working software over documentation, frequent delivery of software increments, and ability to accommodate changing requirements.
This document discusses Ahmed Sidky's experience with evolving agile leadership at Riot Games. It describes how Riot decoupled traditional leadership responsibilities across new roles like Team Captain, Delivery Lead, and Product Lead. It also discusses how Riot invested in growing the skills and competencies needed for these agile leadership roles through learning, mentoring and practice. The document provides examples of responsibilities for each role and emphasizes that leadership is about accountability and enabling the team to share responsibility.
Tracking DevOps Changes In the Enterprise @paulpeissnerPaul Peissner
DevOps - Train and Rails theme
Questions to consider when exploring, adopting or scaling DevOps in the Enterprise.
Hybrid models are the "only" option for organizations with legacy business models they must support, while they search for the right balance and strategies to enable DevOps to co-exist with legacy practices.
A 40 minute introduction to DevOps for the Wellington DevOps Meetup, March 2021.
Rob forgot to talk about DevSecOps, which was a fundamental topic, and the general concept of "Shift left". Only so much you can fit in an hour, but they are good topics to research further.
Rob also mentioned some books
IT Revolution DevOps Forum is the best sources of free ebooks about Devops. It costs you an email signup, but it is worth it.
Team of Teams, Stanley McChrystal - good for business agility.
(See also Brave New Work, by Aaron Dignan, as Rob's favourite primer on new ways of working)
The Phoenix Project, by Gene Kim et al. - KoolAid intro to Devops, convinces most people.
Devops Handbook, gene Kim at al - good general refence
Continuous Delivery, Humble and Farley - still the definitive textbook
The Checklist Manifesto, Atul Gawande - in praise of checklists
Field Guide to Human Error, Sidney Dekker - safety culture influences Devops
(see also Dekker's two Youtube videos on Safety Differently and Just Culture)
Rob England consults and trains in IT locally in Welly tealunicorn.com/nwomit
Or see the work Rob and Cherry do together at enterprise level tealunicorn.com/clients
This document discusses an approach to DevOps. It outlines some of the challenges faced in a pre-DevOps environment like SLA violations and burnout. It then discusses how adopting a DevOps mindset can enable faster delivery while maintaining quality. Key aspects of DevOps include treating other teams as customers, establishing feedback loops, and including time for improvement. Metrics like lead time, deployments, and customer satisfaction are important. The document provides examples of DevOps practices from Spotify and references for further information.
Dealing with Shifting Priorities using Lean/Kanban Flow, WIP Limits and Capac...AgileSparks
Many teams suffer from due to conflicting priorities. When today's priority one usurps yesterday's priority one, expensive context switching becomes a problem.
Operations teams are especially hard hit by shifting priorities because of increased variability from supporting ongoing development of new projects while maintaining features & apps in production. Add in unplanned work and security issues and we have a battle between getting new features delivered or keeping production stable. Hence the dilemma DevOps is working to solve.
Dominica will talk about how Dev and Ops teams can use use a Lean flow Kanban approach to limit work-in-progress and allocate capacity for the nature of the demand as a way to address and improve prioritization issues and context switching.
Panel Discussion "Agile and Business Analysis" Dr. Mohamed Salama, Hind Zanto...Agile ME
Agile and Business Analysis (Girvan, L., Paul, D.) was published in 2017 by BCS, The Chartered Institute for IT. This book will be reviewed by two academics (Hind Zantout and Mohammad Hamdan) and the key strengths and weaknesses presented. It is anticipated that a reviewer from industry will join the presenters and contribute the view from industry.
Með tilkomu agile hugbúnaðargerðar er hætt á að forritarar fórni hlutum sem voru sjálfsagðir í aðferðum eins og Waterfall og RUP en eiga fullt erindi í agile þó svo með öðrum hætti. Má nefna skjölun, en margir misskildu agile á þann veg að ekkert þarf að skjala. Skjölun er nauðsynleg þótt hún sé með örðum hætti, en svo er einnig með architecture. Í agile er nauðsynlegt að huga vel að architecture en einnig að átta sig hvað það er sem við skilgreinum sem architecture og hvað ekki.
Í þessum fyrirlestri er fjallað um architecture og agile og hvernig þessir hlutir geta fallið vel saman. Með aglie teymum flyst mikið af ábyrgð á architecture til teymanna, en samt þarf að vera einhver sameinlegur strúktúr og sýn.
Powerpoint from my speak at Agile ME 2017, about how to optimize your agile process, by having an agile approach to your process as well as your product.
This session is an overview on what DevOps is (to me) and how it impacts traditional organizations the most. DevOps is way more than just continuous delivery! From an Agile (synergetic) mindset, DevOps takes a step beyond and focusses on automation, collaboration and learning. Apart from that I also look forward to what oppurtunities lie ahead when implementing DevOps.
On March 2nd I presented this DevOps Unraveled session for abt 40 IT-managers at business university Nyenrode. This was part of the Masterclass Agile management
(Dutch website http://www.executiveeducation.nl/open-programmas/programmadetails/masterclass-agile-management/sectie/introductie.html ).
This document provides an introduction to Agile software development. It discusses the origins and evolution of Agile methods from the 1970s onwards. Key characteristics of Agile include iterative development, emphasis on individuals and interactions over processes, customer collaboration, and responding to change. Specific Agile methodologies like Scrum and Extreme Programming are described. The document also outlines 10 key principles of Agile development such as active user involvement, empowered self-organizing teams, frequent delivery of working software, and collaboration between all stakeholders.
DevOps is popping up in tech circles all over the place. Do you know what it is? How to take advantage of it's benefits? Or where to start. In just a few minutes you can kick-start your shift to a DevOps mindset.
Journey toward Quality Assistance - Agustinus Verdy & FachrulScrum Day Bandung
Continues Integration and Continues Delivery are important in Agile. In this session Very & Fachrul will explain us why CI/CD is no negotiable to build high value product and also deliver a good quality product.
Four pillars of DevOps - John Shaw - Agile Cambridge 2014johnfcshaw
Slides presented at Agile Cambridge 2014 http://agilecambridge.net/ac2014/sessions/index.php?session=57
Session Description:
The emerging practice of DevOps is a natural extension to established Agile methods. The choice of tooling to support the practices is important and will influence heavily how rapid, repeatable and reliable live deployments might be.
Three of the four pillars are concerned with automation through tooling but, arguably, the fourth pillar is more important than the other three together. The fourth pillar is at the heart of the Agile Manifesto: people.
The "Gold Rush" for DevOps is dominated by vendors and the push to sell their wares. But it is people who use the tools, people who define, develop and assure the software, and people who manage the services after they have gone live. One of the cornerstones of DevOps is breaking down the walls between development teams and operations; too much tool specialisation will lead to further separation and even the introduction of yet another silo.
This talk will cover four pillars to DevOps: Environments, Deployment, Testing and People. The insights brought together in this talk were gained under commercial engagements with government clients, on development of financial systems responsible for management of funding in the adult education sector.
Most senior executives in large enterprises believe DevOps and CI/CD are interchangeable. If I have a CI/CD pipeline, I am “doing DevOps”, right? Not exactly. The dilemma that these executives have is that they don’t believe DevOps can be with the people they have. It can be done. I’ll show you how!
5 Keys to Building a Successful DevOps Culture featuring Mandi WallsSerena Software
The document provides 5 keys to building a successful DevOps culture:
1. Set clear and measurable goals that matter to stakeholders across teams.
2. Gain executive support by focusing on goals that benefit multiple teams and influence informal leaders.
3. Start with pilot projects on representative work to practice the cultural and technical aspects of DevOps.
4. Provide training to all teams on new tools and processes while prioritizing the learning work.
5. Continually share progress and successes through various internal and external channels to evangelize DevOps.
The complexity in the simplicity of Agile? by Arie van BennekumAgile ME
Looking at Agile, it is so simple. In fact Agile is just structured common sense. Still so many people struggle to get their success in Agile. What is going on? The point is Agile, with all its simplicity, is based on different paradigms and the old paradigms hinder. The question is, can you identify thew old paradigms and furthermore, how do you change them. Arie van Bennekum will take you in his talk on his 22 years Agile journey and share his experience, successes, his delta’s and IATM, the Integrated Agile Transformation Model he developed for Agile transformations. IATM is a successful Agile change process to (the next level of) Agile he and his teams use doing international Agile transformations.
Killing Agile Software Development : Presented by Rizky Syaiful oGuild .
Last month (June 2016), I helped a well-known higher education institute in Indonesia. I train the lecturers there, so that their students can practice agile software development.
[I show the audience some photos and videos as the proofs]
Can you imagine a condition when all our CS/IT students already get the real experiences of proper Scrum, Automated Testing, etc?
In that imaginary world, agile software development is already the norm! In the other side, there is no more room for Waterfall’s Big-Design-Up-Front style. Because we know that any software problem is inherently a design problem—or complex problem in Cynefin framework. You can’t solve that kind of problem by designing a big-fixed solution up in the front.
And if almost every software development is already agile—as it was visioned back then in 2001 manifesto, why would we still use ‘agile’ term?
We invent words to categorize things. Before ‘agile’ was proposed in the 2001 manifesto, they called it ‘lightweight’. Because it’s different with the previous heavy weight Waterfall.
Now, when I say the word ‘computer’, what would your brain emulate? A mainframe computer? Or a personal computer? Both of them are literally a computing machine. I put my money on personal computer. Because almost everyone see personal computer in daily basis. And they haven’t seen any mainframe computer once in their life.
Just as the dead of ‘personal’ term, in ‘personal computer’—I don’t count PC because that’s an abbreviation—‘agile’ in ‘agile software development’ will also be dead.
Not because it’s bad. On the contrary, that’s because agility the best option for software development.
In 2026 I, believe, we will call it simply as ‘software development’.
Please help the world to reach that kind of utopia, at least by telling your ex-lecturers, “you should teach agile software development properly”.
We should be so proud for standing here. Being a part of agile software development movement, of the 21st century.
Why?
Because a good movement always has a goal,
this agile software development movement also has a clear end.
Appreciative Enquiry : Presented by Sridharan VembuoGuild .
As we all know, Agile, at it’s core, emphasizes on team work. And, if you look at any successful Agile story, the key to it’s success would be a self-oragnized, cohesive team and other factors only add to this.
More often than not, Retrospectives are probably the only forum where the entire team comes together as a single unit and these meetings usually end up being crib (and ranting) sessions. And, because of that, teams are not very enthusiastic about retrospectives and these meetings become more of a ritual than being productive and useful.
As the name ‘Appreciative Enquiry’ suggests, the focus of this meeting was on things that created a positive impact on the team and the project. Sridhar shared few real life examples from his projects, the effective of doing regular Appreciative Enquiries and also guided the participants how they can successfully adopt this technique in their team.
The Objective of this Manifesto is to define guiding principles around the Customer-Supplier working environment with regards to working on Scrum projects. The assumptions made are
•The environment is customer-supplier (i.e. an outsourced environment)
•The environment is distributed and may not be co-located
•The environment involves multiple vendors
The Customers and Suppliers are integrated elements of a working environment in a project. The Customers and Suppliers will work together with a common goal and that is “Producing Value for the End Customer”. This manifesto supports the Agile Manifesto Value “Customer Collaboration over Contract Negotiation”.
If You Need To Run A Project You've Already Failed : Presented by Evan LeybournoGuild .
I want to be controversial for a moment and propose an end to IT projects, project management & project managers. I propose that the entire project process is flawed from the start for one simple reason. If you need to run a project, you’ve already failed.
By definition, an IT project is a temporary structure to govern and deliver a complex change (such as a new product or platform) into an organisation. However, to be truly competitive, an organisation needs to be able to deliver a continuous stream of change. Managed properly, this negates the need for a project and the associated cost overheads.
This is fundamentally what #noprojects is. The approach, structure, tactics and techniques available to successfully deliver continuous change. At its core, #noprojects is predicated on the alignment of activities to outcomes, measured by value, constrained by guiding principles and supported by continuous delivery technologies.
This presentation introduces you to #noprojects. You learn how to define an outcome and create an Outcome Profile. You also learn how to manage change within the context of an outcome through the Activity Canvas.
Agile Transformation and The Metrics Drama : Presented by Deepak GururajaoGuild .
As more and more companies are embarking on the journey of Agile Transformation, leaders are on the constant lookout for various kinds of metrics to measure the progress. Newer and more improved Metrics are being created everyday. Some of them are naive, while the others are complicated to measure. Most metrics are focused on execution. Through his experience, Deepak have seen multiple perspectives for measuring transformation.
Deepak shared his perspective about measurement, and offered the participants, his understanding of Agile Transformation. He discussed about the metrics that make sense from a business perspective.
At the end of the day, its not only the Technology/Engineering leaders, but, also business leaders who fund the transformation and business gets equal share of their benefits form the transformation.
Practical Methods for Adopting DevOps - Michael StahnkePuppet
The document outlines 5 methods for adopting DevOps practices in large organizations with siloed IT teams: 1) Standardize variable infrastructure to reduce failures, 2) Break down silos through collaboration between teams, 3) Share knowledge of failures to prevent recurrences, 4) Experiment with new tools and processes in test environments, 5) Continuously improve processes by addressing root causes rather than symptoms. The methods advocate reducing variability, integrating operations into software development, conducting root cause analyses, and allowing engineers to experiment.
Design Thinking & Innovation Games : Presented by Cedric MainguyoGuild .
Accelerate Innovation: Learn why it matters and how it’s done.
Design Thinking can be used to design products, user experiences, corporate strategy or public services… Innovation Games, whose primary intent is not pure entertainment, can be applied to a broad spectrum of areas like training, hiring, generating new ideas, gathering feedback about a product or change management… The list goes on.
An increasing number of organizations have realized the enormous potential of human-centered and playful approach to innovation design and development. The growing success of Agile methods, which put a strong emphasis on people interactions, on fun and on building a creativity-friendly environment, have made Design Thinking and Innovation Games even more popular.
DevOps: A Culture Transformation, More than TechnologyCA Technologies
DevOps is not a new technology or a product. It's an approach or culture of SW development that seeks stability and performance at the same time that it speeds software deliveries to the business. We will discuss this cultural shift where development teams have to accept the feedback of operations teams and the operations team should be ready to accept frequent updates to the SW that it's running.
To learn more about DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
Accenture DevOps: Delivering applications at the pace of businessAccenture Technology
Are you ready to shift to continuous delivery? DevOps, a leading software engineering innovation, makes this shift possible by bringing business, development and operation teams together to streamline IT and applying more automated processes.
DevOps and Continuous Delivery Reference Architectures (including Nexus and o...Sonatype
There are numerous examples of DevOps and Continuous Delivery reference architectures available, and each of them vary in levels of detail, tools highlighted, and processes followed. Yet, there is a constant theme among the tool sets: Jenkins, Maven, Sonatype Nexus, Subversion, Git, Docker, Puppet/Chef, Rundeck, ServiceNow, and Sonar seem to show up time and again.
Katrina Novakovic "Default to Open: Creating a DevOps Culture"Fwdays
DevOps is not just having your Dev and Ops teams sit in the same room reporting to the same manager, introducing some agile tools, automating some manual steps of established processes and carrying on working the same way. You haven't actually changed the way the teams operate. Building a culture is at the core of DevOps adoption, and this involves a change in mindset.
This session will look at what key cultural characteristics made Red Hat the world's leading provider of enterprise Open Source solutions (spoiler alert: they are based on Open Source principals) and how you can apply these to your teams to break down silos and enhance openness, sharing and collaboration. There will be time for Q&A to answer your questions about relevant topics, such as remote teams, failing fast and any other barriers you are facing.
A talk delivered by Dr Tim Cockle at Public Sector Enterprise 2013.
The presentation looks at how various agile techniques can be applied in public sector organisations.
Topics covered:
• Understanding what agile means for you
• What are the core principles and implications
• How to find the balance when moving towards agile
This document provides an introduction to DevOps. It begins with background on the presenter and then outlines the topics to be covered: What is DevOps?, Why DevOps?, and How to DevOps?. Under What is DevOps?, it explains that DevOps emphasizes communication and collaboration between development and operations teams. It also discusses definitions of DevOps and what DevOps is not. The Why DevOps? section notes that DevOps can increase speed, reduce risks, and help companies adapt to changes. How to DevOps? involves cultural shifts, focusing on people, processes, tools, and adopting concepts like automation, lean, measurement and sharing.
Innovation is defined as the production, adoption, assimilation and exploitation of a novel value that renews products, services and markets or develops new methods of production. Innovation can be both a process and an outcome. Agile principles focus on individuals, collaboration, responding to change and frequent delivery of working software. Agile aligns well with innovation as it is iterative, dynamic and involves feedback. Examples where agile has enabled innovation include education through tools like SOLE that delegate learning to students, disaster management through goal-driven teamwork, and connecting IoT devices through collaborative development. The presentation concludes that agile provides values and an open framework to realize innovations faster through experimentation and opportunities.
This document outlines Forum's Principles of Learning presentation from 2011. It discusses trends impacting workplace learning effectiveness and strategies for success. The 6 principles of workplace learning are outlined as linking learning to individual and organizational value, connecting action and reflection in a continuous cycle, addressing learners' attitudes and behaviors, providing a balance of challenge and support, creating opportunities for participants to teach, and designing learning communities and media. The presentation also discusses developing leaders and a shifting role for learning and development in enabling knowledge sharing and building learning solutions to address strategic issues.
The document discusses various approaches to training including experiential learning, laboratory approaches, and systematic approaches. It describes Kolb's experiential learning theory and the experiential learning cycle. It also outlines the key steps in a systematic approach to training including needs assessment, objective setting, design, implementation, and evaluation. Training approaches should consider factors like gender, culture, ability and sexuality to ensure inclusiveness.
The document summarizes a presentation on reimagining assessment and feedback given by consultants from Jisc. It discusses Jisc's current research on trends in assessment, principles of good assessment, results from a poll on concerns in the higher education assessment landscape, examples of how technology can help implement assessment principles, and looking to the future of assessment including what is not yet supported digitally. The presentation engaged participants in activities to discuss tools, examples of good practice, and future support needs.
Lieve Leroy how can grasshoppers change ict practiceslievle
The document discusses using a "grassroots" approach to encourage teachers to adopt new information and communication technologies (ICT) in their classrooms. Key aspects of the grassroots approach include allowing teachers to propose small-scale ICT projects, providing support and guidance during implementation, and disseminating successful projects. The approach has been used successfully in Zambia to motivate teachers with little ICT experience and increase ICT use in education.
ePortfolios supporting training and the trainerJohn Pallister
The document discusses the use of ePortfolios to support training and professional development. It notes an increasing demand for retraining employees and the need for evidence of skills and competencies. An ePortfolio provides a way for learners to compile digital evidence of their skills, achievements, and reflections. This supports personalized learning and motivation. The ePortfolio process benefits both learners and trainers by facilitating reflection, planning, and feedback. The document recommends creating a learning environment that supports ePortfolios, integrating their use into policies, training teachers, and ensuring learners understand the process.
The document outlines the AIESEC Experience Pipeline which involves several steps and opportunities for learning and development. It discusses five key principles of the AIESEC Experience: 1) taking an active role in your own learning and that of others, 2) challenging your worldview, 3) developing meta-cognition and personal reflection skills, 4) increasing practical and theoretical knowledge, and 5) creating a network of contacts from around the world. The principles are meant to guide participants' experience and facilitate learning through various activities and roles within the AIESEC program.
This document discusses identifying and sharing good practices within organizations. It defines good practice as a process or methodology that has been shown to be effective. It recommends a six-step process for identifying and sharing good practices: 1) identify user requirements, 2) discover good practices, 3) document good practices, 4) validate good practices, 5) disseminate and apply good practices, and 6) develop an infrastructure to support good practice sharing. The benefits of sharing good practices include improving performance, reducing costs, and minimizing knowledge loss. Cautions include that good practice is an ongoing process and culture plays an important role.
The document discusses Appreciative Inquiry (AI), a strengths-based approach to organizational change and development. It provides an overview of AI, including its key principles and the 5-D cycle of Define, Discover, Dream, Design, and Destiny. Case studies are presented showing how various organizations have used AI to improve performance, build shared visions, and develop strategic plans through collaborative inquiry and storytelling.
The document discusses preparing staff for online learning and identifies several challenges organizations face based on survey data. It provides feedback on six questions: how to increase skills and confidence; improve access; encourage collaboration; help leaders understand online learning's benefits; prepare trainers; and overcome past negative experiences. Suggestions include guiding, empowering and involving staff; improving technology access; fostering reflection and information sharing; communicating regularly; and addressing issues proactively. The goal is to build an open culture where online learning is embraced.
Many organizations have long term employees retiring and find themselves needing to be competitive to fill key roles. Schools are teaching new ways of working that include working as part of a team, and using Agile methods.
In this one hour webinar we will explore how hiring practices and working environments need to change in order to attract and retain top talent in today's competitive market.
This document provides an overview of an entrepreneurship course at NYU ITP that uses the Lean LaunchPad methodology. The course will be taught by Jen van der Meer and Josh Knowles and will guide student teams through developing business models and minimum viable products over the semester. The class will include exercises on the business model canvas, guest speakers, and mentors who will coach individual student teams. Students will be expected to conduct customer interviews and iterate their ideas based on feedback.
How Scrum Master can help the team in quitting 'SMOKING' - Talk by Bhanu Golc...oGuild .
During Discuss Agile Day Delhi 2019 - One Day Conference (14 September), Bhanu Golconda & Vamsi Krishna presented their talk on "How Scrum Master can help the team in quitting 'SMOKING'". Check out the exclusive Interview of Bhanu Golconda & Vamsi Krishna at the last slide.
Talk description: We all know ‘Smoking is injurious to health’ but in this session we are going to discuss about ‘How SMOKING is injurious to teams’ health’ and how Scrum Master can help the team in quitting 'SMOKING'.
-Are you satisfied with mediocre or above par performance? No?
-Do you need the best out of everyone? Yes?
-Have you ever realized about the bad practices that crept in. Yes or No?
We have brainstormed with more than 30 Scrum teams and collated the SMOKING patterns. So, in this session we are going to discuss in detail about tried and tested recommendations to trash those SMOKING patterns with which we can increase efficiency and also break the monotony in Scrum events.
Culture and You - Talk by Hariharaganesh (Discuss Agile Day Delhi 2019)oGuild .
During Discuss Agile Day Delhi 2019 - One Day Conference (14 September), Hariharaganesh presented his talk on Culture and You. Check out the exclusive Interview of Hariharganesh at the last slide.
Talk Description: Organization's culture is the sum of belief and behaviors of all employees. It is built on values and drives Organizational effectiveness through Competitive advantage. The visible part of cultural iceberg drives us to think what we see and believe in our Organization constitutes the culture. There is also big portion of cultural iceberg that is not visible to the employees that drives the hard reality.
Culture is a soft concept and like strategy it cannot be copied. Is there a way to measure culture? If not, then how do we say whether particular culture is good or bad? As an individual how often do we change our behavior to adapt to a new situation? If changing one’s behavior is tough, then how difficult is to change behavior of big Organization?
Discuss Agile an user group of Scrum Alliance conducted an One Day Conference On 14th of September, 2019. This was the 5th conference organized by Discuss Agile & sponsored by iZenBridge Consultancy in Delhi. Discuss Agile Day is an one day event of like-minded Agile practitioners, trainers, coaches, and enthusiasts.
Webinar on Big Data Challenges : Presented by Raj KasturioGuild .
Big data is huge! with billions and billions of data sets and a need to analyze and apply that to real-life problem-solving is a challenge. Are traditional methods successful in solving big data problems?
Let’s take a look at the current state of big data, if traditional methodologies are providing the necessary answers quick enough. Is Agile/Scrum a good fit for big data?
– big data in any industry
– high data availability, real time analytics, data warehousing
– agile spectrum and where do my projects fall?
– big data complexity and empirical process control theory
– current industry trends
– metrics
Leadership in Agile : by Karthik Mahadevan & Ramakrishnan SitaramanoGuild .
The bottom line to a agile (self organizing high performing) team is constant flow of energy. This guarantees optimal pace of quality deliverables.
To maintain this creative equilibrium, leaders can look at”Engaging” directly or “Enable” individuals or by “Empowering” the team without compromising team autonomy.
As a leader
When you “Engage” its not about you, its about the team / individual
When you “Enable” its not about who / what .. Its about Why
When you “Empower” its not about it being leaving for the team’s choice but its about setting the right stage / context for them to act.
Kanban for Self Development : Presented by Sundaresan SethuramanoGuild .
Sundaresan Sethuraman is an Agile-DevOps Solution Architect with over 16 years of experience who will discuss using Kanban for self-development. The presentation will cover using Kanban to manage time and achieve work-life balance, overcoming obstacles to growth, and integrating SMART goals into a personal Kanban system to facilitate holistic development. Videos will demonstrate Kanban and how Personal Kanban can increase productivity for tasks, activities, and goals.
The document discusses an upcoming Agile Day event in Chennai on August 20th, 2017. The event will feature a talk by Sasanka Kiran Ravula, an Agile Coach, on how coaches can change mindsets. Ravula has several Agile certifications and discusses concepts like the GROW model, mindset, and the DECAF "e" coaching model which involves discovering, exploring, communicating, analyzing, following up, and enabling. The talk aims to provide insight and awareness around how coaching can shift perspectives.
Art of Doing Effective Scrum : Presented by Mohammed JavidoGuild .
The team dynamics takes the team through the stages of transition from forming, storming, norming to performing.
Each member of the team also passes through the individual phases of forming, storming, norming to performing.
The Scrum guide has listed the roles, events, artifacts, rules in a short document which needs to be adhered, irrespective
of the stage that the team is or the stage that the individual team member is. It will quickly bring the visibility on the current stage of the team and will provide opportunity for inspection and adaption.
The topic will cover the scenarios related to the dynamics of the team and roles.
The suggestions(actionable guidance) will be provided along with the scenarios.
The message to the audience will be on the lines of ‘Own Your Baby’, Avoiding instances of ‘Operation Successful, but Patient Died’
The bottom line will be to refer back to Scrum guide as and when the team needs clarity on roles, events, artifacts, rules of Scrum. At the same time the target is not on doing Scrum but on being Scrum, the target is to get the working software and Scrum is one of the enablers towards it. Scrum too mentions the importance of working software at great depth.
Agility Beyond Framework and Dev Team : by Anubhav SinhaoGuild .
Agility and Lean-Agile practices plays a vital role if people understand and give a continuous learning pattern. We can have agility in Pre-sales for identifying Bid Cycle or, Employment Engagement Experience rather than only HR etc. Senior Folks to become Leader rather than bosses. Co-working folks to interact rather than Peer, that may lead to identification of a solution appearance rather than problem creator.
Key Takeaways:
– a role thought as Imaginary PO for Pre-sales engagements
– how all members of pre-sales coordinates
– how HR can turn to 3E
– Incremental and evolving – From 3S to Collaborative
– Few metrics to understand
Influential Leadership : Presented by Ramanathan YegyanarayananoGuild .
Leadership is the process of influencing others to understand and agree about what needs to be done and how to do it, and the process of facilitating individual and collective efforts to accomplish shared objectives.
Influential Leadership is the KEY to developing a raving fan culture. Influential Leadership is the ability of a leader to incite action in others simply through mastering the skills of communication and motivation tailored to an individual person.
we can have a wonderful team if there is a right person who can influence others and groom a leader in the community. This is the intent of the topic being chosen for this conference by me.
Agile Inception Strategies : Presented by Khaarthigha SubramanianoGuild .
Agile Inception using Innovative and Collaborative techniques & Gamification came for rescue, But now this is also diluted a lot and becoming in-effective. But used well, this is highly effective even to discover more than what we are focusing and help channel the investments for the clients.
We took a real world problem that is meaningful to all attendees and used the following techniques as a real inception
– Describing the objectives of inception and inception outcomes
– Setting the vision
– Identify Competing constraints and decouple them
– Understand nuances of client relationship and being dynamic in modelling the solution
– Stakeholder mapping and communication plan
– Assumption mapping and hypotheses prioritisation
– Traceability of user needs to business goals through impact mapping.
Becoming Successful Product Owner : Presented by Arne AhlanderoGuild .
It is common for new Product Owners to be left without instructions or ideas of how to succeed. The role of the PO is different from traditional roles and in order to survive as a PO new learning is necessary. In order to become a successful PO you don’t only need a vision, you also need good tools, principles and practices.
Here Arne presents principles, tools and practices to help you become more successful in your role regardless if you are new or more experienced.
The Day I Realized I Was Not Yet An Agile Coach : Presented by Sylvain MaheoGuild .
I remember that morning, 6 or 7 years ago. I had been practicing Agile for a couple of years and I had decided to update my LinkedIn profile. I opened my profile, edited my headline and replaced “Scrum Master” with “Agile Coach”.
That was a lie. But I didn’t know it at that time. I really believed I had become a coach. In reality I was a consultant, a trainer, sometimes a mentor.
A few years later I decided to go back to school -a coaching school- and it changed my life.
In this talk, I shared my personal journey to become an (Agile) Coach and shared what I’ve learned along the way:
• What is the difference between consulting, training, coaching and why we should care?
• Why by calling ourselves coaches we are not doing any good to the coach profession?
• What can we do about it?
• How did I become a coach?
• What are my coaching tools?
• Does your organization really need a coach?
Introduction to Management 3.0 : Presented by Ralph van RoosmalenoGuild .
Management 3.0 is a movement of innovation, leadership and management. Management 3.0 is redefining the definition of leadership with management as a group responsibility. It’s about working together to find the most efficient way for a business to achieve its goals while maintaining the happiness of workers as a priority.
Management 3.0 is a global management revolution that brings together thousands of project managers, mid-level managers, CEOs and entrepreneurs, developing solutions together, using games to encourage employee feedback and team collaboration.
Your Coach is Killing Your Agility : Presented by Madhur KathuriaoGuild .
The document describes three different ways that project managers reacted to the introduction of agile practices in their organization. The first project manager became miserable and left when agile took away their control over decision making. The second project manager actively worked to undermine agile and return to the old ways of working. The third project manager embraced their new role as a coach and mentor under agile, which improved productivity and relationships with their team.
Classical Approach to Agile Coaching : Presented by Sateesh Sindogi oGuild .
EmpiRadical Consulting provides project management and agile coaching services. They help clients own up project management, coach agile teams, and implement custom delivery models. EmpiRadical also develops educational products like DeltaLearn. The document discusses how a classical project manager like Rahul Dravid was able to adapt to new cricket formats and have success coaching teams, suggesting that a classic PM with the right mindset can also coach agile teams by focusing on fundamentals, building confidence, sticking to process, and embracing change. It provides a checklist for coaches to help teams with skills, mindset, process, experimentation, and innovation.
Decoding the ‘Pair Testing’ in Agile ! Presented by Krishna and Rama oGuild .
Software projects, especially the product development teams, today are fast moving away from the traditional development methodology and adopting Agile for obvious advantages that it brings to the table. However, as always, advantages are accompanied by a number of challenges. The session emphasised on ‘The Power of Two’
· Practical testing challenges in Agile
· Deep dive into Agile testing technique – Pair Testing
· Pragmatic approaches & applicability of Pair Testing
· Factors for successful implementation
· Pros & Cons of Pair Testing
Agile for Embedded & System Software Development : Presented by Priyank KS oGuild .
Priyank shared the experience of challenges in being Agile in Embedded/System software development. The effective approaches to handling such challenges were discussed. The importance of eXtreme Programming practices in solving the challenges was highlighted.
Psychology of Motivation and Change : Presented by Sanjay KumaroGuild .
More than new process adoption, experts say Agile is a mindset change. But, as many of us may have experienced, changing people is tough. And, mindset change even tougher, at times almost impossible.
In this session we reviewed some important concepts related to human motivation and their inclination to change, that in turn helps us answer some of the following questions:
What motivates people?
Difference between intrinsic motivation and extrinsic motivation?
Can people change? Do they even want to change?
If yes, what kind of changes they might prefer?
Are there ways to make people amenable to change?
Introduction to Disciplined Agile Delivery (DAD) : Presented by Dr. Sanjay Sa...oGuild .
The document introduces Disciplined Agile Delivery (DAD), a hybrid agile framework that leverages proven strategies from agile methodologies. It provides an overview of DAD's key characteristics and decision-making framework. The presentation also describes DAD's basic lifecycle, roles, and emphasis on continuous learning and tailoring practices based on context. Finally, it outlines the Disciplined Agile Consortium's certification program, which recognizes three levels of proficiency - Disciplined Agile (DA), Certified Disciplined Agile (CDA), and Certified Disciplined Agile Professional (CDAP) and Certified Disciplined Agile Coach (CDAC).
When to Embrace Behavior Driven Development : Presented by Ranjith TharayiloGuild .
Behaviour Driven Development (BDD) is a collaborative and disciplined technique to help us build the right product. In the last decade BDD has had her own bit of glory and criticism. Many teams in the recent past have reaped benefits from this technical practice, while some teams complain that are yet to find any value. This article focuses on answering two questions; Why BDD might not always be the right choice? What are the ideal conditions when teams should adopt it?
In this talk we come up with a BDD adoption matrix to help us answer the above questions. We also assert that for successful product development it is crucial to bridge the gap between the problem space and solution space, each of which has its own set of complexities. We conclude that Behavior Driven Development can be one of the effective techniques to bridge this gap especially if the problem space is complex. In case the problem space is simple it might be an over kill and teams might not find real value practicing BDD. We also observe that teams whose problem space is simple can continue to document scenarios and automate acceptance testing but they need not spend elaborate time and effort towards discussing and debating scenarios.
Understanding Inductive Bias in Machine LearningSUTEJAS
This presentation explores the concept of inductive bias in machine learning. It explains how algorithms come with built-in assumptions and preferences that guide the learning process. You'll learn about the different types of inductive bias and how they can impact the performance and generalizability of machine learning models.
The presentation also covers the positive and negative aspects of inductive bias, along with strategies for mitigating potential drawbacks. We'll explore examples of how bias manifests in algorithms like neural networks and decision trees.
By understanding inductive bias, you can gain valuable insights into how machine learning models work and make informed decisions when building and deploying them.
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...IJECEIAES
Medical image analysis has witnessed significant advancements with deep learning techniques. In the domain of brain tumor segmentation, the ability to
precisely delineate tumor boundaries from magnetic resonance imaging (MRI)
scans holds profound implications for diagnosis. This study presents an ensemble convolutional neural network (CNN) with transfer learning, integrating
the state-of-the-art Deeplabv3+ architecture with the ResNet18 backbone. The
model is rigorously trained and evaluated, exhibiting remarkable performance
metrics, including an impressive global accuracy of 99.286%, a high-class accuracy of 82.191%, a mean intersection over union (IoU) of 79.900%, a weighted
IoU of 98.620%, and a Boundary F1 (BF) score of 83.303%. Notably, a detailed comparative analysis with existing methods showcases the superiority of
our proposed model. These findings underscore the model’s competence in precise brain tumor localization, underscoring its potential to revolutionize medical
image analysis and enhance healthcare outcomes. This research paves the way
for future exploration and optimization of advanced CNN models in medical
imaging, emphasizing addressing false positives and resource efficiency.
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024Sinan KOZAK
Sinan from the Delivery Hero mobile infrastructure engineering team shares a deep dive into performance acceleration with Gradle build cache optimizations. Sinan shares their journey into solving complex build-cache problems that affect Gradle builds. By understanding the challenges and solutions found in our journey, we aim to demonstrate the possibilities for faster builds. The case study reveals how overlapping outputs and cache misconfigurations led to significant increases in build times, especially as the project scaled up with numerous modules using Paparazzi tests. The journey from diagnosing to defeating cache issues offers invaluable lessons on maintaining cache integrity without sacrificing functionality.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
ACEP Magazine edition 4th launched on 05.06.2024Rahul
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...IJECEIAES
Climate change's impact on the planet forced the United Nations and governments to promote green energies and electric transportation. The deployments of photovoltaic (PV) and electric vehicle (EV) systems gained stronger momentum due to their numerous advantages over fossil fuel types. The advantages go beyond sustainability to reach financial support and stability. The work in this paper introduces the hybrid system between PV and EV to support industrial and commercial plants. This paper covers the theoretical framework of the proposed hybrid system including the required equation to complete the cost analysis when PV and EV are present. In addition, the proposed design diagram which sets the priorities and requirements of the system is presented. The proposed approach allows setup to advance their power stability, especially during power outages. The presented information supports researchers and plant owners to complete the necessary analysis while promoting the deployment of clean energy. The result of a case study that represents a dairy milk farmer supports the theoretical works and highlights its advanced benefits to existing plants. The short return on investment of the proposed approach supports the paper's novelty approach for the sustainable electrical system. In addition, the proposed system allows for an isolated power setup without the need for a transmission line which enhances the safety of the electrical network
A review on techniques and modelling methodologies used for checking electrom...nooriasukmaningtyas
The proper function of the integrated circuit (IC) in an inhibiting electromagnetic environment has always been a serious concern throughout the decades of revolution in the world of electronics, from disjunct devices to today’s integrated circuit technology, where billions of transistors are combined on a single chip. The automotive industry and smart vehicles in particular, are confronting design issues such as being prone to electromagnetic interference (EMI). Electronic control devices calculate incorrect outputs because of EMI and sensors give misleading values which can prove fatal in case of automotives. In this paper, the authors have non exhaustively tried to review research work concerned with the investigation of EMI in ICs and prediction of this EMI using various modelling methodologies and measurement setups.
KuberTENes Birthday Bash Guadalajara - K8sGPT first impressionsVictor Morales
K8sGPT is a tool that analyzes and diagnoses Kubernetes clusters. This presentation was used to share the requirements and dependencies to deploy K8sGPT in a local environment.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
2. ABOUT ME
An accomplished Agile coach and
corporate trainer having 9+ years
of experience in agile and
waterfall project management.
Over past 9 years I have worked
in various roles such as Enterprise
Agile Coach and Transformation
consultant, Corporate Trainer,
Project Manager, Product Owner,
Business Analyst, Scrum Master,
and Quality Assurance Analyst
3. AGENDA
What is devops
Why devops
The three ways
Devops as culture
Get involved
4. DEV+OPS (CAN DO AMAZING THINGS
TOGETHER
Hi, I am Dev Hi, I am Ops
8. WE HAVE THE BEST DEV TEAM
A team that plans together, build together, demo
together and learn together
How about deploying together….. That’s devops
9. WHAT IS DEVOPS
DevOps is a cultural and professional
movement that stresses communication,
collaboration and integration between
software developers and IT operations
professionals – Devops Institute
10. ORIGIN OF DEVOPS
At the Agile 2008 conference, Andrew Clay Shafer and
Patrick Debois discussed "Agile Infrastructure“. The term
"DevOps" was popularized through a series of
devopsdays starting in 2009 in Belgium. Since then,
there have been devopsdays conferences held in many
countries worldwide
11. THE THREE WAYS
The Three Ways are introduced in ‘The Phoenix
Project: A Novel About IT, DevOps, And Helping Your
Business Win’ by Gene Kim, Kevin Behr and George
Spafford. The Three Ways are an effective way to
frame the processes, procedures and practices of
DevOps, as well as the prescriptive steps.
12. THE THREE WAYS
The First Way – Flow • Understand and increase the flow of work (left to right)
The Second Way – Feedback • Create short feedback loops that enable
continuous improvement (right to left)
13. THE THREE WAYS
The Third Way – Continuous experimentation and
learning • Create a culture that fosters Experimentation,
taking risks and learning from failure
Understanding that repetition and practice is the
prerequisite to mastery
14. DEVOPS CULTURE
It is important to understand the Why – for your organization in terms of adopting a devops
culture
Key steps in dev ops implementation
Get the right people together – ensure core stakeholders are engaged; particularly early adopters
who are committed to experimentation and learning.
Get everyone on the same page – seek to understand each other’s perspectives and concerns,
determine what outcomes you want to achieve and set measurable goals – be realistic!
Build capabilities that lead to lasting change – use education to introduce a common vocabulary,
provide ongoing, just in time training, leverage early adopters and informal networks of peer
motivators, build trust through transparency, and generate and celebrate short-term wins.
Focus on critical behaviors - Every culture has behaviors that help enable change and others that
hinder it. Find ways to nurture the enabling behaviors that matter most.
15. DEVOPS CULTURE
Experiment and learn – prioritize improvement opportunities, take a holistic
approach (i.e., address people, process and technology-related
improvements), select and run pilots, capture lessons learned and share,
rather than enforce, improved practices
Consolidate gains and produce more change – in the spirit of transparency,
communicate successes, failures and lessons learned. Document and make
available reusable artifacts and measurements. Continuously invest in needed
education, training and technologies, and expand your cycles of
improvement.
Avoid inertia – use metrics to prove that the new way of doing things is
better. Reinforce new behaviors with incentives and rewards
16. ADDITIONAL RESOURCES
www.devops.com
www.devopsinstitute.com
2014 State of DevOps Report. Puppet Labs, IT Revolution Press,
ThoughtWorks
Lean Enterprise: Adopting Continuous Delivery, DevOps, and Lean
Startup at Scale. J. Humble, et al, O'Reilly Media, 2014
The Phoenix Project. G. Kim, et al, IT Revolution Press, 2013
Continuous Delivery. J. Humble, et al. Addison-Wesley Professional,
2010
Lean IT: Enabling and Sustaining Your Lean Transformation. S. Bell
and M Orzen. Productivity Press, 2010
Editor's Notes
10 seconds
10 seconds
Let’s start with our foundation
15mins
1 minute
10 minutes
10 minutes
10 minutes
With this action we are observing two major component of human cardio vascular system interacting with each other. This is a micro level view of the system (2 minutes)