It Automation: Doing it Wrong - Mykel Alvis
•
2 likes•763 views
Mykel Alvis of Momentum SI talks about "IT Automation: Doing it Wrong" at Puppet Camp Silicon Valley 2012.
Report
Share
Report
Share
Download to read offline
Recommended
IT Automation: You're doing it Wrong
The document discusses enterprise automation and common problems with how enterprises approach it. It notes that enterprise applications are often slow, expensive, and inefficient. It then discusses who the target audience is for enterprise automation (those working on large, complex enterprise systems), what they are looking for (faster delivery, more reliability), and what they actually get (failure, partial success). The document argues the key issues are apathy towards delivery and lack of focus on and support for automation. It provides recommendations like starting small and incrementally, continually refining processes, keeping automation up to date, and combating apathy.
Agile hacks for product managers
gineering teams. This workshop will cover everything you need to know to work seamlessly with engineering teams that use agile principles and practices.
What you will learn:
• Basics of the agile methods.
• Tips you can apply the very next day at work.
• Actionable tools and tactics to handle different product team scenarios that a product manager face.
Who is this workshop for:
• Software engineers who want to transition to Product Management
• MBAs with a finance/consulting background who want to work in high-tech companies as a Product Manager
• Project Managers, Marketers, Designers who are seeking for new opportunities in Product Management
Getting To Product Market Fit Quickly
This 1-hour workshop marries the best practices from product strategy with those of fast and efficient technology teamwork and delivery. You’ll learn how to get your product organization working as a single cohesive, well-oiled machine to deliver the right product to market as quickly as possible. We will cover how to use both qualitative and quantitative measures to ensure that your product is solving the right problem; how to optimize and streamline the way your team designs, builds, and deploys software to your customers; and, how to beat the competition in strategy and execution.
Creative services 101
This document discusses common problems that creative services departments face and provides tips for improving workflows and processes. It notes that creative services is challenging due to unpredictable schedules, tight deadlines, and team burnout. It recommends that departments identify the root problems, not just symptoms, filter any proposed fixes, map out new processes clearly, and thoroughly test changes before implementing them live to ensure long-term success. The overall message is that tweaking workflows and changing processes can help creative teams run more smoothly and productively.
A quick guide to manage your remote team efficiently
Managing a remote team for the first time during the COVID-19 pandemic can be challenging, but defining clear expectations, using communication tools consistently, and maintaining trust are key. It is important to specify employees' daily activities, the tools being used, and work hours so remote work isn't "business as usual" and everything is written down rather than discussed verbally. Managers should also seek feedback on how to improve managing their remote teams.
LeanKit Webinar: Evolving Your Daily Standup with Kanban by Brendan Wovchko
Have your daily standups become stale? Discover how to reinvigorate the conversation by focusing on the core principles of Kanban.
Brendan Wovchko of HUGE I/O will explain how to engage teams with meaningful questions that surface problems, reduce process waste and improve the flow of work.
You'll learn how to:
- “Walk the board” with Kanban
- Experiment with fresh questions and techniques
- Decide if your daily standup really needs to be daily
Enabling your team to identify improvement opportunities on a daily basis promotes self-organization and keeps the focus on delivering value.
Strategic Portfolio Management With Kanban
Presentation made during the 2017 Gatineau-Ottawa Agile Tour by Nicolas Mercier and Frédéric Paquet.
Portfolio management is a key aspect of organizational performance. The ability to visualize upcoming projects, projects in progress, the process of value creation, the dependencies, the ability to share a common vision and to throttle the work in progress based on organizational capacity are all contributing elements to the effectiveness of an organization.
Unfortunately, the shared vision of a portfolio is too often buried in a tool shared with too few people and does not help the organization build a global and cohesive plan of action.
But when we think about it... Value chain, limiting work in progress, transparency, flow... have you ever thought about using Kanban for portfolio management? Seems like a great idea!
Create alignment around what delivers value to your end-users, use cadence to move forward, help shape a new organizational culture, support innovation, continuous improvement, and leadership and unite people around a shared mission, that is what Kanban at the strategic level can bring.
The Web and Beyond - Chrissy Welsh
This document provides a quick start guide to Lean UX. It outlines organizing hypotheses, aligning ideas with brand goals through wireframes, rapidly building rough prototypes, and using metrics to determine if ideas should be developed further or discarded to allow for failing fast. The goal is to get ideas in front of users quickly to learn what works best and focus efforts accordingly.
Recommended
IT Automation: You're doing it Wrong
The document discusses enterprise automation and common problems with how enterprises approach it. It notes that enterprise applications are often slow, expensive, and inefficient. It then discusses who the target audience is for enterprise automation (those working on large, complex enterprise systems), what they are looking for (faster delivery, more reliability), and what they actually get (failure, partial success). The document argues the key issues are apathy towards delivery and lack of focus on and support for automation. It provides recommendations like starting small and incrementally, continually refining processes, keeping automation up to date, and combating apathy.
Agile hacks for product managers
gineering teams. This workshop will cover everything you need to know to work seamlessly with engineering teams that use agile principles and practices.
What you will learn:
• Basics of the agile methods.
• Tips you can apply the very next day at work.
• Actionable tools and tactics to handle different product team scenarios that a product manager face.
Who is this workshop for:
• Software engineers who want to transition to Product Management
• MBAs with a finance/consulting background who want to work in high-tech companies as a Product Manager
• Project Managers, Marketers, Designers who are seeking for new opportunities in Product Management
Getting To Product Market Fit Quickly
This 1-hour workshop marries the best practices from product strategy with those of fast and efficient technology teamwork and delivery. You’ll learn how to get your product organization working as a single cohesive, well-oiled machine to deliver the right product to market as quickly as possible. We will cover how to use both qualitative and quantitative measures to ensure that your product is solving the right problem; how to optimize and streamline the way your team designs, builds, and deploys software to your customers; and, how to beat the competition in strategy and execution.
Creative services 101
This document discusses common problems that creative services departments face and provides tips for improving workflows and processes. It notes that creative services is challenging due to unpredictable schedules, tight deadlines, and team burnout. It recommends that departments identify the root problems, not just symptoms, filter any proposed fixes, map out new processes clearly, and thoroughly test changes before implementing them live to ensure long-term success. The overall message is that tweaking workflows and changing processes can help creative teams run more smoothly and productively.
A quick guide to manage your remote team efficiently
Managing a remote team for the first time during the COVID-19 pandemic can be challenging, but defining clear expectations, using communication tools consistently, and maintaining trust are key. It is important to specify employees' daily activities, the tools being used, and work hours so remote work isn't "business as usual" and everything is written down rather than discussed verbally. Managers should also seek feedback on how to improve managing their remote teams.
LeanKit Webinar: Evolving Your Daily Standup with Kanban by Brendan Wovchko
Have your daily standups become stale? Discover how to reinvigorate the conversation by focusing on the core principles of Kanban.
Brendan Wovchko of HUGE I/O will explain how to engage teams with meaningful questions that surface problems, reduce process waste and improve the flow of work.
You'll learn how to:
- “Walk the board” with Kanban
- Experiment with fresh questions and techniques
- Decide if your daily standup really needs to be daily
Enabling your team to identify improvement opportunities on a daily basis promotes self-organization and keeps the focus on delivering value.
Strategic Portfolio Management With Kanban
Presentation made during the 2017 Gatineau-Ottawa Agile Tour by Nicolas Mercier and Frédéric Paquet.
Portfolio management is a key aspect of organizational performance. The ability to visualize upcoming projects, projects in progress, the process of value creation, the dependencies, the ability to share a common vision and to throttle the work in progress based on organizational capacity are all contributing elements to the effectiveness of an organization.
Unfortunately, the shared vision of a portfolio is too often buried in a tool shared with too few people and does not help the organization build a global and cohesive plan of action.
But when we think about it... Value chain, limiting work in progress, transparency, flow... have you ever thought about using Kanban for portfolio management? Seems like a great idea!
Create alignment around what delivers value to your end-users, use cadence to move forward, help shape a new organizational culture, support innovation, continuous improvement, and leadership and unite people around a shared mission, that is what Kanban at the strategic level can bring.
The Web and Beyond - Chrissy Welsh
This document provides a quick start guide to Lean UX. It outlines organizing hypotheses, aligning ideas with brand goals through wireframes, rapidly building rough prototypes, and using metrics to determine if ideas should be developed further or discarded to allow for failing fast. The goal is to get ideas in front of users quickly to learn what works best and focus efforts accordingly.
ToT17 UK: When Things Go Wrong - Dave Wilson, Hollywood Bowl
In this presentation, Dave Wilson shares his experience in when things go wrong in ITSM - server outage, unexpected occurences - and how to best deal with them in a calm, structured manner.
Step Up Your Data Security Against Third-Party Risks
This presentation was delivered to the Hacks & Hops event attendees in the Spring of 2019. The event featured a short keynote following by a moderated panel discussion. The panel experts provided excellent guidance for all risk managers, CISOs, vendor managers, etc.
DevOps for the sysadmin
What is DevOps and how do SysAdmins participate in it? Explains what DevOps is and is not and provides tools, tips, and tricks for SysAdmins to participate and find value. Presented at Indianapolis VMUG's November 2014 meeting.
Five Upcoming Leadership Trends
Leadership trends will continue to evolve over the next several years. In order to make the most out of your resources and team, you need to understand how to adapt to these changes in 2019 and beyond. Here is what you should be on the lookout for and apply to your own style:
How to Sell Kanban to Your Boss
In this webinar, I’ll share my experiences with helping teams communicate the value of Kanban in a way that makes sense to management.
Flow, the Universe and Everything
The document discusses the concept of "flow" or being fully immersed in an activity. It provides characteristics of flow including clear goals, strong concentration, intrinsic reward, loss of self-consciousness and time distortion. The document then discusses how teams and organizations can achieve flow through optimizing their processes to reduce bottlenecks and wait times, using techniques like Scrum of Scrums and PI planning. Key aspects that can disrupt flow are discussed, like fractionalized work and excessive work in progress. The document emphasizes the need for intentional design of work systems and value streams to achieve organizational flow at scale.
Software Economies of Scale
Software development does not benefit from economies of scale and instead experiences diseconomies of scale. Developing in small batches provides several advantages: it accelerates feedback, makes debugging easier, allows for better visualization of progress, de-risks projects, improves estimation, enables more pivoting, gives more opportunities to inspect and adapt work, and delivers value to customers more efficiently.
Observation of the wastes in shipping and receiving - Continuous Improvement ...
Our shipping and receiving department is the busiest department in our plant. I've spent a lot of time to observe why our inventory accuracy is low. This slide show is based on some data I gathered and my opinion. This slide show has been presented to the manager. If you have a better suggestions or idea for the improvement, I would like to know about it. Thanks.
Process Mapping, System Insight
This document discusses process mapping and diagrams for explaining complex systems and processes. It begins by outlining reasons for creating explanatory diagrams at work, such as to invent, propose, demonstrate, instruct, and repair systems. Potential reasons for not diagramming are discussed, such as perceptions that it is boring or unnecessary. The document then provides examples of different types of diagrams - including flowcharts, state diagrams, data flow diagrams, mind maps - and discusses their appropriate uses for capturing different types of processes and systems. Guidelines are presented for effective process mapping, including starting informally and progressing to more formal diagrams, as well as different roles in collaborative process mapping projects.
Winnipeg Agile Users Group March 10 2011
1) The document describes an agile workshop where participants introduced themselves and played a ball passing game to warm up.
2) They discussed an article about how slow IT can slow business innovation, and how reducing delays between ideas and results provides better returns than just getting better at individual tasks.
3) In relation to agile, the group discussed how practices like reducing handoffs, co-located teams, continuous improvement through retrospectives, and embracing experimentation can help speed up delivery of working software.
Enterprise Project Management
This document discusses enterprise project management from multiple perspectives in a series of short sections. It addresses what enterprise project management is and is not, some common challenges organizations face without it, and potential benefits of implementing it. It also considers different views on implementing and sustaining an enterprise project management solution, and whether the technology itself or how it is applied matters most.
#resources(1)(2)Kanban
Kanban is a tool used to manage workflow and optimize the flow of tasks from not started to completed. It uses a visual board to display the status of work - tasks move from "to do" to "doing" to "done". Key principles of Kanban include limiting work in progress to avoid bottlenecks and measuring flow through metrics to identify areas for improvement to maximize efficiency. Implementing Kanban can help improve workflow by optimizing flow, making timely decisions, and focusing on completing individual tasks rather than just starting work.
Lean Prod Development ProductCamp Vancouver Feb15
The document discusses the need for delivery at the speed of market changes, sufficient predictability, and alignment of efforts to maximize customer value. It notes that traditional development approaches rely on large batches, centralized control, and plans which can lead to delays, wasted knowledge, and missed opportunities. While Agile helps, it faces challenges with coordination, scaling, and stress on the rest of the organization. The document recommends taking an economic view by making work visible, limiting work-in-progress, reducing batch sizes, controlling queues, accelerating feedback, and standardizing where possible to optimize flow and throughput.
Pixelz TaaS - eCommerce Images
Scale product image post-production effortlessly with talent and tech.
Our Talent-as-a-Service model provides all benefits you need to leverage your online business.
TaaS
TaaS offers an image editing and retouching service that allows customers to outsource work while maintaining control through their Talent-as-a-Service solution. With TaaS, customers can upload images before leaving the office and have them ready the next morning with edits from TaaS's full-time team of retouchers. TaaS provides time-saving online tools, assured quality, US-based support and flexibility between in-house and outsourced options to help brands streamline image editing.
Why Executives Can't Change
The document discusses why executives have difficulty changing strategies and processes, even when presented with compelling data showing alternatives would be better. It explains that organizations often fall into "bad equilibriums" where individually rational strategies combine to produce poor collective outcomes. This happens because organizations converge on processes that are faster, cheaper and better for each individual player, but do not optimize the desired outcomes of reliability, collaboration, risk management etc. for the organization as a whole. The document advocates using tools from "game theory" and "Lean" like value stream mapping to help executives understand these dynamics and make changes through techniques like establishing a "Dojo" for hands-on learning and coaching.
Acnl2015 maarten hoppe-red bead experiment
The document summarizes key principles from the theory of variation:
1. Variation exists in all systems and performance will naturally vary over time.
2. Understanding sources of variation allows managers to set appropriate targets and expectations.
3. The majority of variation is caused by the system, not individual performers. Improving the system design and processes can reduce variation.
4. Statistical process control methods help distinguish common from special causes of variation and determine when meaningful changes have occurred.
Principles of Lean UX
This document discusses Lean UX principles for building digital products, including:
- Using cross-functional teams that are small, dedicated, and co-located.
- Focusing on outcomes rather than outputs and getting out of the deliverables business.
- Engaging in rapid prototyping and continuous discovery to learn through building minimum viable products and measuring results.
- Deferring decisions when possible and using small batch sizes to reduce waste and failure costs.
See the New Features in MindFire Studio Marketing Automation Platform
This webinar from MindFire Studio discusses their Q1-13 marketing automation software release. The webinar agenda includes a review of new features and use cases, how to get started with onboarding, and a question and answer session. Key areas covered are campaign automation improvements like lead nurturing and scoring, campaign management safety features, dashboard enhancements, and new outbound apps for print and voice.
Agile consortium nl annual congress 2016 vx company - winkle case study
The document describes Winkle's transition from a chaotic, uncontrolled project management process to implementing Kanban. It outlines the problems they faced with long lead times, errors, and siloed teams. They introduced Kanban to provide visibility, limit work in progress, and encourage collaboration. After initial training and setting up their board, they saw improvements like shorter lead times, increased revenue with the same team size, and less rework. The challenges included resistance to change and continuously improving their Kanban system and processes.
Nasty Impediments: Unclog the Pipe for Business Agility
This presentation goes into details about impediments, how to identify them, how to create a strategy for, escalate, and ultimately - if not removing them entirely - moving the needle to improve the situation. Apologies for the outdated styling - it's on my backlog to improve it!
05. Zeal agile - Kim Oostvoghels - #ScaBru18
Metamorphosis or Mutation? All about agile workplaces for sustainable, desirable and disruptive organization.
More Related Content
What's hot
ToT17 UK: When Things Go Wrong - Dave Wilson, Hollywood Bowl
In this presentation, Dave Wilson shares his experience in when things go wrong in ITSM - server outage, unexpected occurences - and how to best deal with them in a calm, structured manner.
Step Up Your Data Security Against Third-Party Risks
This presentation was delivered to the Hacks & Hops event attendees in the Spring of 2019. The event featured a short keynote following by a moderated panel discussion. The panel experts provided excellent guidance for all risk managers, CISOs, vendor managers, etc.
DevOps for the sysadmin
What is DevOps and how do SysAdmins participate in it? Explains what DevOps is and is not and provides tools, tips, and tricks for SysAdmins to participate and find value. Presented at Indianapolis VMUG's November 2014 meeting.
Five Upcoming Leadership Trends
Leadership trends will continue to evolve over the next several years. In order to make the most out of your resources and team, you need to understand how to adapt to these changes in 2019 and beyond. Here is what you should be on the lookout for and apply to your own style:
How to Sell Kanban to Your Boss
In this webinar, I’ll share my experiences with helping teams communicate the value of Kanban in a way that makes sense to management.
Flow, the Universe and Everything
The document discusses the concept of "flow" or being fully immersed in an activity. It provides characteristics of flow including clear goals, strong concentration, intrinsic reward, loss of self-consciousness and time distortion. The document then discusses how teams and organizations can achieve flow through optimizing their processes to reduce bottlenecks and wait times, using techniques like Scrum of Scrums and PI planning. Key aspects that can disrupt flow are discussed, like fractionalized work and excessive work in progress. The document emphasizes the need for intentional design of work systems and value streams to achieve organizational flow at scale.
Software Economies of Scale
Software development does not benefit from economies of scale and instead experiences diseconomies of scale. Developing in small batches provides several advantages: it accelerates feedback, makes debugging easier, allows for better visualization of progress, de-risks projects, improves estimation, enables more pivoting, gives more opportunities to inspect and adapt work, and delivers value to customers more efficiently.
Observation of the wastes in shipping and receiving - Continuous Improvement ...
Our shipping and receiving department is the busiest department in our plant. I've spent a lot of time to observe why our inventory accuracy is low. This slide show is based on some data I gathered and my opinion. This slide show has been presented to the manager. If you have a better suggestions or idea for the improvement, I would like to know about it. Thanks.
Process Mapping, System Insight
This document discusses process mapping and diagrams for explaining complex systems and processes. It begins by outlining reasons for creating explanatory diagrams at work, such as to invent, propose, demonstrate, instruct, and repair systems. Potential reasons for not diagramming are discussed, such as perceptions that it is boring or unnecessary. The document then provides examples of different types of diagrams - including flowcharts, state diagrams, data flow diagrams, mind maps - and discusses their appropriate uses for capturing different types of processes and systems. Guidelines are presented for effective process mapping, including starting informally and progressing to more formal diagrams, as well as different roles in collaborative process mapping projects.
Winnipeg Agile Users Group March 10 2011
1) The document describes an agile workshop where participants introduced themselves and played a ball passing game to warm up.
2) They discussed an article about how slow IT can slow business innovation, and how reducing delays between ideas and results provides better returns than just getting better at individual tasks.
3) In relation to agile, the group discussed how practices like reducing handoffs, co-located teams, continuous improvement through retrospectives, and embracing experimentation can help speed up delivery of working software.
Enterprise Project Management
This document discusses enterprise project management from multiple perspectives in a series of short sections. It addresses what enterprise project management is and is not, some common challenges organizations face without it, and potential benefits of implementing it. It also considers different views on implementing and sustaining an enterprise project management solution, and whether the technology itself or how it is applied matters most.
#resources(1)(2)Kanban
Kanban is a tool used to manage workflow and optimize the flow of tasks from not started to completed. It uses a visual board to display the status of work - tasks move from "to do" to "doing" to "done". Key principles of Kanban include limiting work in progress to avoid bottlenecks and measuring flow through metrics to identify areas for improvement to maximize efficiency. Implementing Kanban can help improve workflow by optimizing flow, making timely decisions, and focusing on completing individual tasks rather than just starting work.
Lean Prod Development ProductCamp Vancouver Feb15
The document discusses the need for delivery at the speed of market changes, sufficient predictability, and alignment of efforts to maximize customer value. It notes that traditional development approaches rely on large batches, centralized control, and plans which can lead to delays, wasted knowledge, and missed opportunities. While Agile helps, it faces challenges with coordination, scaling, and stress on the rest of the organization. The document recommends taking an economic view by making work visible, limiting work-in-progress, reducing batch sizes, controlling queues, accelerating feedback, and standardizing where possible to optimize flow and throughput.
Pixelz TaaS - eCommerce Images
Scale product image post-production effortlessly with talent and tech.
Our Talent-as-a-Service model provides all benefits you need to leverage your online business.
TaaS
TaaS offers an image editing and retouching service that allows customers to outsource work while maintaining control through their Talent-as-a-Service solution. With TaaS, customers can upload images before leaving the office and have them ready the next morning with edits from TaaS's full-time team of retouchers. TaaS provides time-saving online tools, assured quality, US-based support and flexibility between in-house and outsourced options to help brands streamline image editing.
Why Executives Can't Change
The document discusses why executives have difficulty changing strategies and processes, even when presented with compelling data showing alternatives would be better. It explains that organizations often fall into "bad equilibriums" where individually rational strategies combine to produce poor collective outcomes. This happens because organizations converge on processes that are faster, cheaper and better for each individual player, but do not optimize the desired outcomes of reliability, collaboration, risk management etc. for the organization as a whole. The document advocates using tools from "game theory" and "Lean" like value stream mapping to help executives understand these dynamics and make changes through techniques like establishing a "Dojo" for hands-on learning and coaching.
Acnl2015 maarten hoppe-red bead experiment
The document summarizes key principles from the theory of variation:
1. Variation exists in all systems and performance will naturally vary over time.
2. Understanding sources of variation allows managers to set appropriate targets and expectations.
3. The majority of variation is caused by the system, not individual performers. Improving the system design and processes can reduce variation.
4. Statistical process control methods help distinguish common from special causes of variation and determine when meaningful changes have occurred.
Principles of Lean UX
This document discusses Lean UX principles for building digital products, including:
- Using cross-functional teams that are small, dedicated, and co-located.
- Focusing on outcomes rather than outputs and getting out of the deliverables business.
- Engaging in rapid prototyping and continuous discovery to learn through building minimum viable products and measuring results.
- Deferring decisions when possible and using small batch sizes to reduce waste and failure costs.
See the New Features in MindFire Studio Marketing Automation Platform
This webinar from MindFire Studio discusses their Q1-13 marketing automation software release. The webinar agenda includes a review of new features and use cases, how to get started with onboarding, and a question and answer session. Key areas covered are campaign automation improvements like lead nurturing and scoring, campaign management safety features, dashboard enhancements, and new outbound apps for print and voice.
Agile consortium nl annual congress 2016 vx company - winkle case study
The document describes Winkle's transition from a chaotic, uncontrolled project management process to implementing Kanban. It outlines the problems they faced with long lead times, errors, and siloed teams. They introduced Kanban to provide visibility, limit work in progress, and encourage collaboration. After initial training and setting up their board, they saw improvements like shorter lead times, increased revenue with the same team size, and less rework. The challenges included resistance to change and continuously improving their Kanban system and processes.
What's hot (20)
ToT17 UK: When Things Go Wrong - Dave Wilson, Hollywood Bowl
ToT17 UK: When Things Go Wrong - Dave Wilson, Hollywood Bowl
Step Up Your Data Security Against Third-Party Risks
Step Up Your Data Security Against Third-Party Risks
Observation of the wastes in shipping and receiving - Continuous Improvement ...
Observation of the wastes in shipping and receiving - Continuous Improvement ...
See the New Features in MindFire Studio Marketing Automation Platform
See the New Features in MindFire Studio Marketing Automation Platform
Agile consortium nl annual congress 2016 vx company - winkle case study
Agile consortium nl annual congress 2016 vx company - winkle case study
Similar to It Automation: Doing it Wrong - Mykel Alvis
Nasty Impediments: Unclog the Pipe for Business Agility
This presentation goes into details about impediments, how to identify them, how to create a strategy for, escalate, and ultimately - if not removing them entirely - moving the needle to improve the situation. Apologies for the outdated styling - it's on my backlog to improve it!
05. Zeal agile - Kim Oostvoghels - #ScaBru18
Metamorphosis or Mutation? All about agile workplaces for sustainable, desirable and disruptive organization.
LeanKaizenTraining
This document provides an overview of Lean and Kaizen concepts and tools for process improvement. It discusses key Lean principles like eliminating waste, continuous flow and pull systems, visual management, and standardizing work. The document emphasizes that the primary goals of Lean are to maximize value added work and human development by empowering employees and changing management styles.
Dev up 2016 Demystifying the scaled agile framework
Just when companies seems to be warming up to agile, here comes SCALED agile. But how is SAFe really different than agile? Does using the SAFe framework undermine the scrum teams? Isn’t SAFe just a glorified version of waterfall that companies adopt when they can’t handle “real” agile? I decided the best solution was to go through the training and spend some time practicing it in the field. What I found was that SAFe leverages the best of Lean, Kanban, and scrum. SAFe is intended for large, enterprise customers delivering extremely complex and interdependent systems, but that doesn’t mean it offers nothing to smaller teams. Since becoming a Safe program consultant, I have coached a number of my smaller customers on improving their software development and delivery processes leveraging techniques from SAFe. In this interactive session, I plan to quickly walk through the tenets of SAFe, share some of my learnings with you, and help you to understand when and how SAFe can benefit your team!
Let's Talk About Agile
This document discusses overcoming confusion about Agile and the business value of adopting Agile ways of working. It begins by addressing common Agile myths that spread confusion. The author then discusses what Agile values really mean and what an Agile way of working entails. The document emphasizes that true Agility cannot be achieved with the same roles, strategies, processes, etc. and that change is required within the organization. It outlines some of the changes involved and reasons why organizations need to become more Agile. Finally, it discusses different perspectives on Agile adoption and how to communicate the benefits to various stakeholders.
Empowering Agile Self-Organized Teams With Design Thinking
My experience and research has shown that design thinking empowers employees and teams, enabling them to create a more resilient, value-focused organizational culture.
Innovation-driven growth at the organizational level requires a multidisciplinary approach to designing systems that create the right conditions for self-organizing teams to explore and create while maintaining system hygiene. To achieve that growth, leaders and managers must adopt a strategy for fostering new thinking, practices, and processes that convert strategy both laterally and vertically into new value. To foster the right kind of environment, you must manage the boundaries of the teams, establishing the right cadence and rituals to ensure trust and psychological safety.
“Organizations that operate from the authoritarian, hierarchical, command and control model, where the top leaders control the work, information, decisions, and allocation of resources, produce employees that are less empowered, less creative, and less reductive.” – Journal of Strategic Studies, Creativity and Innovation: The Leadership Dynamics.
In this talk, we’ll discuss boundaries, policies, cadence for self-organizing teams, then cover the key principles and practices of design thinking and how it can be leveraged by agile teams to collaboratively test new options and create new value. Design thinking all comes down to the collaboration utilizing divergence and convergence: acquire and synthesize insights, formulate hypotheses, prototype solutions, and ruthlessly test them with real customers.
We’ll cover that with a case study of how an infrastructure engineering team transformed themselves from waterfall to agile, while learning the key practices of design thinking to reduce the lead time for delivering services and systems from 9 months to days, and in some cases, hours.
The key aspects of Design Thinking we’ll cover:
The importance of trust, boundaries, and candor for team dynamics;
Customer-Centricity. Who are they? What are their challenges? What are their ‘jobs-to-be-done’?
Empathy and Understanding to engaging with customers in their context;
Validate through experimentation that the team is solving the right problem;
Bringing the whole team together to collaboratively explore the problem space and engage in divergent and convergent exercises;
Prototype lightweight solution hypotheses to ensure that the problems are solved before scaling out and investing in delivering the product or service to customers;
When design thinking is appropriate, and when it’s a waste of time (when a user story is simple, simply do it!)
What did i learn trying to migrate teams from legacy to modern?
Session on the psychology behind change in software transformation efforts. First held at Limerick .NET Azure User Group.
Learn Spotify (an Agile Framework)
Learn and be inspired by how Spotify does Agile at scale with squads, chapters, tribes, guilds and more as you want to scale your agile environment Understand the processes and decisions behind Spotify’s organizational design as well as the lessons learned and the changes made the last five years.
Selenium Users Anonymous
This document summarizes a presentation on best practices for using Selenium for test automation. The presentation covers 12 steps: 1) Admit you have a problem; 2) Take a deep breath; 3) Try looking at things differently; 4) Pump some tech iron; 5) Find your inner Napoleon and develop a strategy; 6) Break down the wall between QA and development; 7) Learn the terrain; 8) Test less but test well; 9) Keep it lean and optimize; 10) Pay it forward by sharing knowledge; 11) Resources for learning Selenium; 12) Recap of the 12 steps. The document provides additional details on each step and recommendations for learning more.
'My Case for Agile Methods & Tranformation' : Presented by Saikat Das
This paper describes Saikat's experiences with Agile values, tranforamtion and my implementation of them. He describes the circumstances that have led him to believe passionately that Agile Frameworks will best assure the success of his projects.
Competency models for the team and how to choose specific practices against the model.
He describes what has worked for him and why, and he describes what hasn’t worked and why.
Highlights:
A different Approach to look into Agile practices and Transformation.
The difference between Agile Adoption and Agile Transformation.
The real goal of Agile change initiatives.
Adapting Practices in Agile.
2022 Subsistence Agile - Sustainability and Self-Sufficiency for Thriving Tea...
Does ‘subsistence’ carry a negative connotation for you—scarcity, poverty, barely scraping by? In this era of enterprise scaling and big digital transformations, our trusty old agile often feels the same. It’s easy to get stuck when it seems like every retrospective action item worth doing requires an executive sponsor who isn’t coming.
Our planetary challenges require us to think of ‘subsistence’ differently. The ability to produce what we need, sustainably, using the resources available in our communities, is powerful! Are you getting the best from the ecosystem you already have?
This session explores practical tips for nurturing and growing your agile practice hyper-locally, using techniques accessible at the team level.
Learning outcomes:
- Build and strengthen the supportive agile community already around you
- Reduce your dependence on expensive faraway ‘imports’
- Expand your influence and capabilities by developing ‘trade’ networks nearby
- Focus on what’s most important for you and your team to thrive!
2010 10 15 the lean startup at tech_hub london
The document discusses the key principles of the Lean Startup methodology for building startups under conditions of extreme uncertainty. It advocates for an approach of continuous experimentation through building minimum viable products, obtaining rapid customer feedback through metrics like split testing, and using this validated learning to iteratively pivot or evolve the product or business model. The goal is to minimize the time required to progress through the build-measure-learn feedback loop in order to increase the chances of success before running out of resources.
How BMC is Scaling Agile Development
The document discusses BMC's transition to adopting agile development practices across the entire organization over twelve months. Some key lessons learned included ensuring teams stayed able to release working software frequently, empowering teams but also providing support, and gaining executive sponsorship for the significant changes required by the agile transition. The transition involved scaling agile practices up from individual teams to entire departments and business units.
Natalie Yadrentseva - Fix the process not the problem public
This document discusses fixing processes rather than problems by using process visualization. It recommends visualizing the current process using workshops to understand how work is done. This helps establish a shared understanding and identify challenges. The next steps are to pilot improvements, learn through experiments, and establish feedback loops to continuously learn and prevent future problems. The goal is to shift from "fixing as it fails" to anticipating issues through understanding customers, training, and small improvements to maximize value while increasing stability and predictability.
Fix the process, not the problem
Better Software, Florence'15
- Benefits of the processes visualization in an organization
- How to synchronize teams, get all departments at the same page and understand the responsibility
- How to start: build a Process Map step-by-step at the Process Visualization workshop (phases, people, timing)
Test Automation in Agile: A Successful Implementation
Many teams feel that they are forced to make an either/or decision when it comes to investing time to automate tests versus executing them manually. Sometimes a “silver bullet” tool is purchased, and testers are forced to use it when there may be a better option; other times unskilled team members are designated the automation engineers; and often there is a lack of good guidance on what to automate. These pitfalls cause product owners to de-prioritize those tasks when there’s a better way. Melissa Tondi shares how test teams should evaluate automated tools, both open source and commercial; areas to be aware of when traditional manual testers transition to automation engineers; and recommended priorities for automating tests. By streamlining automation tasks in your project and incorporating these recommendations, you’ll find that your automation intersection becomes a clearly marked thruway to a successfully released product.
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...
Agile Project Management: From Agile Teams to Agile Organizations
We will present the tools and strategies for adopting agile project management practices that connect business, management and delivery teams. We propose a framework that maintains an executive focus on managing investment and risk, introduces enterprise-level agile product development lifecycle and separates project governance from operational delivery while loosely coupling these activities.
À propos de Steve Mercier
Steve est un professionnel du développement de produits logiciels, comptant plus de 20 ans d’expérience. Il a développé et mis en place des lignes de production logicielles assurant une meilleure efficacité de livraison, une adhésion croissante aux meilleures pratiques définies et une qualité accrue des produits entraînant la satisfaction des clients. Il applique les méthodes de travail Agile au quotidien depuis bientôt 10 ans. Il aime les défis techniques, apprécie être responsable de livrer, avec des gens de talents, en équipe, des produits qui comptent vraiment. Au fil des années il s'est spécialisé dans les champs suivants: Bonnes pratiques de développement de logiciel, Intégration et livraison continue, Lignes de production logicielles, Infrastructure gérée comme du code, Méthodes Agile et amélioration continue. Il oeuvre en ce moment comme gestionnaire d’une équipe de 15 DevOps bourrés de talent chez Lightspeed.
À propos de Jean-Paul Chauvet
President, Lightspeed
With over 20 years' experience as a marketing and sales executive in the technology sector, JP has been a key element in the continued growth of Lightspeed. By developing and leading Lightspeed's product strategy, go-to-market direction and taking a direct approach to engaging independent businesses, he has helped Lightspeed increase revenue, strengthen partner relations and achieve success month over month.
Acceleration & Focus - A Simple Approach to Faster Execution
#projectcon #agilecon
PROJECTCON | AGILECON Midwest 2019 in Indianapolis on May 10, 2019
Presenter: Michael Hannan
Acceleration & Focus - A Simple Approach to Faster Execution
Many articles & books emphasize the importance of focus to getting more done, but not many offer proven techniques to achieve big jumps in focus for entire teams—and thus accelerate the speed of execution dramatically. This session will provide a simple, common-sense method to achieve such acceleration for teams of any size, and at any scale.
Event Website: https://projectconevent.com
LinkedIn: https://www.linkedin.com/company/projectcon-llc
Facebook: http://www.facebook.com/ProjectConEvent
Twitter: http://www.twitter.com/projectconevent
YouTube: https://www.youtube.com/channel/UCLLG1SGPs1L5YLoFndvGGhQ
Instagram: https://www.instagram.com/projectconevent
Presentation Slides: https://slideshare.com/projectcon
Post Event Trailer: https://youtu.be/1_RzFBnZ7bo
ProjectCon AgileCon Project Management
Bottom-up adoption through the prism of Flow
Flow by Donald Reinertsen offers insights into how scrum should work. Considering the scenario of a team trying to "go agile" within a large corporate environment, What insights does Flow grant us?
SDEC15: Help the Scrum Master *IS* the Impediment
Talk on how scrum masters can avoid becoming impediments to their agile teams. Presented at SDEC 2015.
Similar to It Automation: Doing it Wrong - Mykel Alvis (20)
Nasty Impediments: Unclog the Pipe for Business Agility
Nasty Impediments: Unclog the Pipe for Business Agility
Dev up 2016 Demystifying the scaled agile framework
Dev up 2016 Demystifying the scaled agile framework
Empowering Agile Self-Organized Teams With Design Thinking
Empowering Agile Self-Organized Teams With Design Thinking
What did i learn trying to migrate teams from legacy to modern?
What did i learn trying to migrate teams from legacy to modern?
'My Case for Agile Methods & Tranformation' : Presented by Saikat Das
'My Case for Agile Methods & Tranformation' : Presented by Saikat Das
2022 Subsistence Agile - Sustainability and Self-Sufficiency for Thriving Tea...
2022 Subsistence Agile - Sustainability and Self-Sufficiency for Thriving Tea...
Natalie Yadrentseva - Fix the process not the problem public
Natalie Yadrentseva - Fix the process not the problem public
Test Automation in Agile: A Successful Implementation
Test Automation in Agile: A Successful Implementation
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...
Acceleration & Focus - A Simple Approach to Faster Execution
Acceleration & Focus - A Simple Approach to Faster Execution
More from Puppet
Puppet camp2021 testing modules and controlrepo
This document discusses testing Puppet code when using modules versus a control repository. It recommends starting with simple syntax and unit tests using PDK or rspec-puppet for modules, and using OnceOver for testing control repositories, as it is specially designed for this purpose. OnceOver allows defining classes, nodes, and a test matrix to run syntax, unit, and acceptance tests across different configurations. Moving from simple to more complex testing approaches like acceptance tests is suggested. PDK and OnceOver both have limitations for testing across operating systems that may require customizing spec tests. Infrastructure for running acceptance tests in VMs or containers is also discussed.
Puppetcamp r10kyaml
This document appears to be for a PuppetCamp 2021 presentation by Corey Osman of NWOPS, LLC. It includes information about Corey Osman and NWOPS, as well as sections on efficient development, presentation content, demo main points, Git strategies including single branch and environment branch strategies, and workflow improvements. Contact information is provided at the bottom.
2021 04-15 operational verification (with notes)
The document discusses operational verification and how Puppet is working on a new module to provide more confidence in infrastructure health. It introduces the concept of adding check resources to catalogs to validate configurations and service health directly during Puppet runs. Examples are provided of how this could detect issues earlier than current methods. Next steps outlined include integrating checks into more resource types, fixing reporting, integrating into modules, and gathering feedback. This allows testing and monitoring to converge by embedding checks within configurations.
Puppet camp vscode
This document provides tips and tricks for using Puppet with VS Code, including links to settings examples and recommended extensions to install like Gitlens, Remote Development Pack, Puppet Extension, Ruby, YAML Extension, and PowerShell Extension. It also mentions there will be a demo.
Modules of the twenties
- The document discusses various patterns and techniques the author has found useful when working with Puppet modules over 10+ years, including some that may be considered unorthodox or anti-patterns by some.
- Key topics covered include optimization of reusable modules, custom data types, Bolt tasks and plans, external facts, Hiera classification, ensuring resources for presence/absence, application abstraction with Tiny Puppet, and class-based noop management.
- The author argues that some established patterns like roles and profiles can evolve to be more flexible, and that running production nodes in noop mode with controls may be preferable to fully enforcing on all nodes.
Applying Roles and Profiles method to compliance code
This document discusses adapting the roles and profiles design pattern to writing compliance code in Puppet modules. It begins by noting the challenges of writing compliance code, such as it touching many parts of nodes and leading to sprawling code. It then provides an overview of the roles and profiles pattern, which uses simple "front-end" roles/interfaces and more complex "back-end" profiles/implementations. The rest of the document discusses how to apply this pattern when authoring Puppet modules for compliance - including creating interface and implementation classes, using Hiera for configuration, and tools for reducing boilerplate code. It aims to provide a maintainable structure and simplify adapting to new compliance frameworks or requirements.
KGI compliance as-code approach
This document discusses Kinney Group's Puppet compliance framework for automating STIG compliance and reporting. It notes that customers often implement compliance Puppet code poorly or lack appropriate Puppet knowledge. The framework aims to standardize compliance modules that are data-driven and customizable. It addresses challenges like conflicting modules and keeping compliance current after implementation. The framework generates automated STIG checklists and plans future integration with Puppet Enterprise and Splunk for continued compliance reporting. Kinney Group cites practical experience implementing the framework for various military and government customers.
Enforce compliance policy with model-driven automation
This document discusses model-driven automation for enforcing compliance. It begins with an overview of compliance benchmarks and the CIS benchmarks. It then discusses implementing benchmarks, common challenges around configuration drift and lack of visibility, and how to define compliance policy as code. The key points are that automation is essential for compliance at scale; a model-driven approach defines how a system should be configured and uses desired-state enforcement to keep systems compliant; and defining compliance policy as code, managing it with source control, and automating it with CI/CD helps achieve continuous compliance.
Keynote: Puppet camp compliance
This document discusses how organizations can move from a reactive approach to compliance to a proactive approach using automation. It notes that over 50% of CIOs cite security and compliance as a barrier to IT modernization. Puppet offers an end-to-end compliance solution that allows organizations to automatically eliminate configuration drift, enforce compliance at scale across operating systems and environments, and define policy as code. The solution helps organizations improve compliance from 50% to over 90% compliant. The document argues that taking a proactive automation approach to compliance can turn it into a competitive advantage by improving speed and innovation.
Automating it management with Puppet + ServiceNow
As the leading IT Service Management and IT Operations Management platform in the marketplace, ServiceNow is used by many organizations to address everything from self service IT requests to Change, Incident and Problem Management. The strength of the platform is in the workflows and processes that are built around the shared data model, represented in the CMDB. This provides the ‘single source of truth’ for the organization.
Puppet Enterprise is a leading automation platform focused on the IT Configuration Management and Compliance space. Puppet Enterprise has a unique perspective on the state of systems being managed, constantly being updated and kept accurate as part of the regular Puppet operation. Puppet Enterprise is the automation engine ensuring that the environment stays consistent and in compliance.
In this webinar, we will explore how to maximize the value of both solutions, with Puppet Enterprise automating the actions required to drive a change, and ServiceNow governing the process around that change, from definition to approval. We will introduce and demonstrate several published integration points between the two solutions, in the areas of Self-Service Infrastructure, Enriched Change Management and Automated Incident Registration.
Puppet: The best way to harden Windows
This document promotes Puppet as a tool for hardening Windows environments. It states that Puppet can be used to harden Windows with one line of code, detect drift from desired configurations, report on missing or changing requirements, reverse engineer existing configurations, secure IIS, and export configurations to the cloud. Benefits of Puppet mentioned include hardening Windows environments, finding drift for investigation, easily passing audits, compliance reporting, easy exceptions, and exporting configurations. It also directs users to Puppet Forge modules for securing Windows and IIS.
Simplified Patch Management with Puppet - Oct. 2020
Does your company struggle with patching systems? If so, you’re not alone — most organizations have attempted to solve this issue by cobbling together multiple tools, processes, and different teams, which can make an already complicated issue worse.
Puppet helps keep hosts healthy, secure and compliant by replacing time-consuming and error prone patching processes with Puppet’s automated patching solution.
Join this webinar to learn how to do the following with Puppet:
Eliminate manual patching processes with pre-built patching automation for Windows and Linux systems.
Gain visibility into patching status across your estate regardless of OS with new patching solution from the PE console.
Ensure your systems are compliant and patched in a healthy state
How Puppet Enterprise makes patch management easy across your Windows and Linux operating systems.
Presented by: Margaret Lee, Product Manager, Puppet, and Ajay Sridhar, Sr. Sales Engineer, Puppet.
Accelerating azure adoption with puppet
The document discusses how Puppet can be used to accelerate adoption of Microsoft Azure. It describes lift and shift migration of on-premises workloads to Azure virtual machines. It also covers infrastructure as code using Puppet and Terraform for provisioning, configuration management using Puppet Bolt, and implementing immutable infrastructure patterns on Azure. Integrations with Azure services like Key Vault, Blob Storage and metadata service are presented. Patch management and inventory of Azure resources with Puppet are also summarized.
Puppet catalog Diff; Raphael Pinson
This document discusses using Puppet Catalog Diff to analyze the impact of changes between Puppet environments or catalogs. It provides the command line usage and options for Puppet Catalog Diff. It also discusses how to integrate Puppet Catalog Diff into CI/CD pipelines for automated impact analysis when merging code changes. Additional resources like GitHub projects and Dev.to posts are provided for learning more about diffing Puppet environments and catalogs.
ServiceNow and Puppet- better together, Kevin Reeuwijk
ServiceNow and Puppet can be integrated in four key areas: 1) Self-service infrastructure allows non-Puppet experts to control infrastructure through a ServiceNow interface; 2) Enriched change management automatically generates ServiceNow change requests from Puppet changes and populates them with impact details; 3) Automated incident registration forwards details of configuration drift corrections in Puppet to ServiceNow to create incidents; and 4) Up-to-date asset management would periodically upload Puppet inventory data to ServiceNow to keep the CMDB accurate without disruptive discovery runs.
Take control of your dev ops dumping ground
This document discusses how Puppet Relay uses Tekton pipelines to orchestrate containerized workflows. It provides an overview of how Tekton fits into the Relay architecture, with Tekton controllers managing taskrun pods to execute workflow steps defined in YAML. Triggers can initiate workflows based on events, with reusable and composable steps for tasks like provisioning infrastructure or clearing resources. Relay also includes features for parameters, secrets, outputs, and approvals to customize workflows. An ecosystem of open source integrations provides sample workflows and steps for common use cases.
100% Puppet Cloud Deployment of Legacy Software
This document discusses deploying legacy software into the AWS cloud using Puppet. It proposes modeling AWS resources like security groups, autoscaling groups, and launch configurations as Puppet resources. This would allow Puppet to provision the underlying AWS infrastructure and configure servers launched in autoscaling groups. It acknowledges challenges around server reboots but suggests they can be addressed. In summary, it argues custom Puppet resources can easily model AWS resources and using Puppet to configure autoscaling servers is possible despite some challenges around rebooting servers during deployment.
Puppet User Group
This document discusses a partnership between Republic Polytechnic's School of Infocomm and Puppet to promote DevOps practices. It introduces several people involved with the partnership and outlines their mission to prepare more IT companies and individuals for jobs in the DevOps field through training courses. The document describes some short courses offered on DevOps topics and using the Puppet and Microsoft Azure platforms. It provides an example of how Republic Polytechnic has automated infrastructure configuration using Puppet to save time and reduce errors. There is a request at the end for readers to register their interest in DevOps by completing a survey.
Continuous Compliance and DevSecOps
This document discusses continuous compliance and DevSecOps best practices followed by financial services organizations.
Continuous compliance is defined as an ongoing process of proactive risk management that delivers predictable, transparent, and cost-effective compliance results. It involves continuously monitoring compliance controls, providing real-time alerts for failures and remediation recommendations, and maintaining up-to-date policies. Best practices for continuous compliance discussed include defining CIS controls and benchmarks, achieving transparent compliance dashboards and automated fixes for breaches.
DevSecOps is introduced as bringing security earlier in the application development lifecycle to minimize vulnerabilities. It aims to make everyone accountable for security. Challenges discussed include security teams struggling to keep up with DevOps pace and
The Dynamic Duo of Puppet and Vault tame SSL Certificates, Nick Maludy
The document discusses using Puppet and Vault together to dynamically manage SSL certificates. Puppet can use the vault_cert resource to request signed certificates from Vault and configure services to use the certificates. On Windows, some additional logic is needed to retrieve certificates' thumbprints and bind services to certificates using those thumbprints. This approach provides automated certificate renewal and distribution across platforms.
More from Puppet (20)
Applying Roles and Profiles method to compliance code
Applying Roles and Profiles method to compliance code
Enforce compliance policy with model-driven automation
Enforce compliance policy with model-driven automation
Simplified Patch Management with Puppet - Oct. 2020
Simplified Patch Management with Puppet - Oct. 2020
ServiceNow and Puppet- better together, Kevin Reeuwijk
ServiceNow and Puppet- better together, Kevin Reeuwijk
The Dynamic Duo of Puppet and Vault tame SSL Certificates, Nick Maludy
The Dynamic Duo of Puppet and Vault tame SSL Certificates, Nick Maludy
Recently uploaded
UiPath Test Automation using UiPath Test Suite series, part 5
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
By Design, not by Accident - Agile Venture Bolzano 2024
As presented at the Agile Venture Bolzano, 4.06.2024
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Recently uploaded (20)
UiPath Test Automation using UiPath Test Suite series, part 5
UiPath Test Automation using UiPath Test Suite series, part 5
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
By Design, not by Accident - Agile Venture Bolzano 2024
By Design, not by Accident - Agile Venture Bolzano 2024
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
It Automation: Doing it Wrong - Mykel Alvis
- 1. Enterprise Automation ur doin’ it wrong
- 2. who is this guy? § Mykel Alvis (@mykelalvis) § Sr. Consultant at MomentumSI § MomentumSI is a leading IT consultancy focused on enterprise transformation § http://www.momentumsi.com § malvis@momentumsi.com
- 3. enterprise? § slow, expensive, sluggish, inefficient § "Enterprise applications are about the display, manipulation, and storage of large amounts of often complex data and the support or automation of business processes with that data.” – Martin Fowler § !entertainment, !productivity § software that costs money, generally lots of it, if it doesn’t work properly
- 4. who are you? § enterprise automation, not webops § relatively slow SDLC § non-cloud, maybe even totally non-virtual § agile, agile-sounding, or maybe just (fr)agile § probably a lot of brownfield dev § process weight doesn’t really matter
- 5. what are you looking for? § cheap/fast/correct § faster time-to-delivery § more reliable and/or correct pushes § less expensive cycles § ease the pain
- 6. what do you really get? § failure § partial success § eventual acquiescence and redefinition of success § reduced happiness
- 7. who wants to be happy? § executive management § mid-level management § business analysts § development § operations
- 8. who gets to be happy? § nobody § precious few § people who actually understand deployment
- 9. how you aren’t happy § delivery cycles are long § successful deployments are rare § replicability is uncommon or unknown
- 10. how ur doin’ it wrong § apathy § lack of focus on delivery § lack of support for automation
- 11. apathy ap·a·thy § [ap-uh-thee] § noun, plural ap·a·thies. 1. absence or suppression of passion, emotion, or excitement. § 2. lack of interest in or concern for things that others find moving or exciting. § 3. Also, ap·a·thei·a, ap·a·thi·a [ap-uh-thee-uh]. Stoicism. freedom from emotion of any kind. -- Dictionary.com
- 12. Enterprise-level Apathytm § code isn’t written to be deployed and nobody cares about that § code promotion transition is not smooth and management does not make that a priority § general apathy is rampant, especially within larger organizations
- 13. causes of apathy § lack of clear goals § lack of motivation for your goal § lack of power to achieve goals
- 14. overcoming apathy (or whatever) § apathy is a bit (lot?/exactly?) like depression § do something (anything!) § gain a new goal § try to make small positive differences § extract yourself from negative groupthink
- 15. lack of focus on delivery § delivery is, or at least should be, part of the satisfaction of requirement § without delivery, there is no software § “elegant” is unfortunately often a synonym for “unintelligible” § delivery really means re-delivery § delivery, and especially easy delivery, is an essential part of practically all testing schemes
- 16. focusing on delivery § SLAs for everyone (analysis, development, QA, ops) § upgrades should be automatic through delivery § start from known quantities § feature-poor code that delivers beats feature-rich code that does not § things that impede the delivery are Bad Things § don’t forget non-delivery concerns
- 17. lack of support for automation § leadership support § tool support § training support
- 18. increasing automation support § utilize tools to control configuration § collect time and success metrics § build management is essential to a delivery pipeline
- 19. common solution elements § start from the top § find a champion § start small and deliver incrementally § continually refactor your process § keep your automation current
- 20. uncommon solution elements § start from the bottom § hire your champion § hide your talents under a bushel (for a while) § think big, then start small and deliver incrementally § continually refactor your process § keep your automation current
- 21. (some of) The Right Waytm § plan for automation from the start § processes that enable, but don’t disable § use semantic versions § manage your source intelligently § manage your dependencies intelligently § define environments as source code § baseline environments from known states § avoid “frankensystems” § seek smooth transitions § define SLAs for developers as well as operations
- 22. fin