For effective, modern, Cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
A talk given at JAX DevOps London - April 2017
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
In summary, this talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible.
Takeaways:
• The implications of Conway’s Law for software teams
• Cognitive Load for teams
• Effective team topologies
• Team evolution
How and why to design your teams for modern software - Sheffield DevOps - Jul...Matthew Skelton
From a talk given at Sheffield DevOps meetup group - http://www.sheffielddevops.org.uk/
How and Why to Design your Teams for Modern Software Systems.
For effective, modern, cloud-connected software systems we need to organise our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organisation design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
WORKSHOP: Organisation Design for Effective Software Systems – Weds 25 October, London - https://ti.to/skelton-thatcher-consulting/ - use DEVOPS25 for 25% discount
What Makes Your Agile Team Self-Organizing? by Dr. Rashina HodaAgile ME
Self-organizing teams is one of fundamental principles of the Agile Manifesto and a critical success factor on Agile projects. But what makes an agile team self-organizing? Based on an industry-based doctoral research involving nearly 60 Agile practitioners from 23 software organizations, this talk presents the informal, implicit, transient, and spontaneous roles —Mentor, Coordinator, Translator, Champion, Promoter, and Terminator— that provide initial guidance and encourage continued adherence to Agile methods; effectively manage customer expectations and coordinate customer collaboration; secure and sustain senior management support; and identify and remove team members threatening the self-organizing ability of the team. Understanding these roles will help Agile teams and their managers better execute their roles and harness their self-organizing potential.
Mind&Matter 2015 builds on the success of Mindfulnet.org’s hugely successful “Mindfulness at Work”
conference, now in its third year, which last year attracted more than 220 attendees from 14 countries.
Addressing the nascent and increasingly hot topic of how to lead
mindfully and introduce and embed sustainable mindfulness
interventions at work, this event will explore the ever-emerging evidence base for corporate mindfulness and introduce practitioners to new workable solutions.
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
In summary, this talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible.
Takeaways:
• The implications of Conway’s Law for software teams
• Cognitive Load for teams
• Effective team topologies
• Team evolution
How and why to design your teams for modern software - Sheffield DevOps - Jul...Matthew Skelton
From a talk given at Sheffield DevOps meetup group - http://www.sheffielddevops.org.uk/
How and Why to Design your Teams for Modern Software Systems.
For effective, modern, cloud-connected software systems we need to organise our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organisation design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
WORKSHOP: Organisation Design for Effective Software Systems – Weds 25 October, London - https://ti.to/skelton-thatcher-consulting/ - use DEVOPS25 for 25% discount
What Makes Your Agile Team Self-Organizing? by Dr. Rashina HodaAgile ME
Self-organizing teams is one of fundamental principles of the Agile Manifesto and a critical success factor on Agile projects. But what makes an agile team self-organizing? Based on an industry-based doctoral research involving nearly 60 Agile practitioners from 23 software organizations, this talk presents the informal, implicit, transient, and spontaneous roles —Mentor, Coordinator, Translator, Champion, Promoter, and Terminator— that provide initial guidance and encourage continued adherence to Agile methods; effectively manage customer expectations and coordinate customer collaboration; secure and sustain senior management support; and identify and remove team members threatening the self-organizing ability of the team. Understanding these roles will help Agile teams and their managers better execute their roles and harness their self-organizing potential.
Mind&Matter 2015 builds on the success of Mindfulnet.org’s hugely successful “Mindfulness at Work”
conference, now in its third year, which last year attracted more than 220 attendees from 14 countries.
Addressing the nascent and increasingly hot topic of how to lead
mindfully and introduce and embed sustainable mindfulness
interventions at work, this event will explore the ever-emerging evidence base for corporate mindfulness and introduce practitioners to new workable solutions.
Lecture about Leadership methods and tools for Master of Information Manageme...Frank Willems
For the TIAS School for Business and Society Master of Information Management this lecture is part of my series of 4 lectures about Leadership and Change Management. This lecture is about leadership tools and methods for personal leadership development and team development
Mind & Matter 2015 - 3rd December 2015
The UK’s most authoritative business mindfulness conference, now in its third year, will explore:
From clinical psychology to sustainable organisational interventions: emerging evidence base to generate sustainable workplace solutions.
Register your interest to speak, sponsor or attend at http://www.mindandmatter2015.com
Managers and the land of the lost 2016 octSteven Martin
hat should you be doing as a Manager who is transitioning / managing in an Agile environment? Learn an exercise you can do with your Managers to help them determine what their role is in a changing Agile environment.
Genesis Group China - Leadership development keynote 2013Chris Jansen
This is a presentation that I have just made at four large HR forums in Beijing, Shanghai, Nanjing and Guangshou in China. As you can see on the slides it was all translated into Mandarin as the audience of 300 were all Chinese speakers. What a wonderfully rich cultural experience!
Building Hyperproductive Agile Teams: Leveraging What Science KnowsTechWell
The key impediments that prevent many organizations from ever realizing the promise of agile and lean aren’t rooted in processes or tools. The impediments stem from the organization’s leaders. Sharing an interdisciplinary overview of the most compelling science and research in the aspects of team performance, Michael DePaoli shows that it is largely ignored. Michael presents a holistic model for building lean/agile teams that combines what science knows enables teams to achieve that elusive state of “flow.” He describes the key external forces—safety for learning, team formation, team tasking, the motivational system, and leadership style—that affect an agile team’s ability to achieve flow. Learn the basics of this model and how Michael is applying it with clients today. Use this model to build your teams and drive agile at scale while evolving the broader organization to harness the promise of agile and lean product development.
Speech Social sourcing @sail startup frank willemsFrank Willems
This is my 15 minutes presentation at the kickoff of the Interreg Sail project for developing sustainable cargoships. I help this project with creating social sourcing communities and research
Top 10 reasons why Agile fails and some optionsAjay Reddy
Even as Agile has become more a marketing term and Agile adoptions commercialized by body shops, several Agile transformations have been seen to fail and sold as successes. This documents some of the reasons why Agile fails.
Team Design for Modern Software Systems - DevOps meetups in Portugal - Nov 2017Matthew Skelton
From talks given at DevOps Lisbon https://www.meetup.com/DevOps-Lisbon/events/242127726/ and DevOps Porto https://www.meetup.com/devopsporto/events/244550405/ meetups.
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
For effective, modern, Cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Talk given at DevOpsCon Munich 2016 - https://devopsconference.de/session/how-and-why-to-design-your-teams-for-modern-software-systems/
Team Topologies - how and why to design your teams - AllDayDevOps 2017Matthew Skelton
From the AllDayDevOps 2017 live stream https://www.youtube.com/watch?v=XqowSG2Jxqc
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Takeaways:
- The implications of Conway’s Law for software teams
- Cognitive Load for teams
- Effective team topologies
- Team evolution
Lecture about Leadership methods and tools for Master of Information Manageme...Frank Willems
For the TIAS School for Business and Society Master of Information Management this lecture is part of my series of 4 lectures about Leadership and Change Management. This lecture is about leadership tools and methods for personal leadership development and team development
Mind & Matter 2015 - 3rd December 2015
The UK’s most authoritative business mindfulness conference, now in its third year, will explore:
From clinical psychology to sustainable organisational interventions: emerging evidence base to generate sustainable workplace solutions.
Register your interest to speak, sponsor or attend at http://www.mindandmatter2015.com
Managers and the land of the lost 2016 octSteven Martin
hat should you be doing as a Manager who is transitioning / managing in an Agile environment? Learn an exercise you can do with your Managers to help them determine what their role is in a changing Agile environment.
Genesis Group China - Leadership development keynote 2013Chris Jansen
This is a presentation that I have just made at four large HR forums in Beijing, Shanghai, Nanjing and Guangshou in China. As you can see on the slides it was all translated into Mandarin as the audience of 300 were all Chinese speakers. What a wonderfully rich cultural experience!
Building Hyperproductive Agile Teams: Leveraging What Science KnowsTechWell
The key impediments that prevent many organizations from ever realizing the promise of agile and lean aren’t rooted in processes or tools. The impediments stem from the organization’s leaders. Sharing an interdisciplinary overview of the most compelling science and research in the aspects of team performance, Michael DePaoli shows that it is largely ignored. Michael presents a holistic model for building lean/agile teams that combines what science knows enables teams to achieve that elusive state of “flow.” He describes the key external forces—safety for learning, team formation, team tasking, the motivational system, and leadership style—that affect an agile team’s ability to achieve flow. Learn the basics of this model and how Michael is applying it with clients today. Use this model to build your teams and drive agile at scale while evolving the broader organization to harness the promise of agile and lean product development.
Speech Social sourcing @sail startup frank willemsFrank Willems
This is my 15 minutes presentation at the kickoff of the Interreg Sail project for developing sustainable cargoships. I help this project with creating social sourcing communities and research
Top 10 reasons why Agile fails and some optionsAjay Reddy
Even as Agile has become more a marketing term and Agile adoptions commercialized by body shops, several Agile transformations have been seen to fail and sold as successes. This documents some of the reasons why Agile fails.
Team Design for Modern Software Systems - DevOps meetups in Portugal - Nov 2017Matthew Skelton
From talks given at DevOps Lisbon https://www.meetup.com/DevOps-Lisbon/events/242127726/ and DevOps Porto https://www.meetup.com/devopsporto/events/244550405/ meetups.
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
For effective, modern, Cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Talk given at DevOpsCon Munich 2016 - https://devopsconference.de/session/how-and-why-to-design-your-teams-for-modern-software-systems/
Team Topologies - how and why to design your teams - AllDayDevOps 2017Matthew Skelton
From the AllDayDevOps 2017 live stream https://www.youtube.com/watch?v=XqowSG2Jxqc
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Takeaways:
- The implications of Conway’s Law for software teams
- Cognitive Load for teams
- Effective team topologies
- Team evolution
DOES15 - Damon Edwards - DevOps Kaizen Practical Steps to Start & Sustain a T...Gene Kim
Damon Edwards, Managing Partner, DTO Solutions, Inc
We all love the aspirational DevOps talks about organizations achieving blistering speed and dazzling nimbleness, right? But what can you do when you look internally at your own organization and everything feels complicated, contentious, and stuck? How do you overcome the silos, the legacy, and the entrenched behaviors that are making your DevOps problems seem so intractable?
This talk is about how to start and sustain a DevOps transformations in large and complex organizations using a methodical — and totally reasonable — Kaizen (Continuous Improvement) approach. This talk isn’t about mythical silver bullets or vague philosophies. This talk is about taking a fresh look at proven Lean techniques and empowering teams to find and fix what is getting in the way.
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.
Work is not a Dare: Tips for Building Inclusive TeamsShawn Rider
All too often, working on a team becomes a never ending sequence of dares. This applies to all teams, but for development teams the problem has some recognizable patterns: Changes are submitted, approved and merged with discussions that take place over the heads of most of the team members -- or without explanation at all; projects lack the supportive tooling that makes work efficient and pleasurable for all of the roles on a team; developers are told to “own” a problem and sent off alone as if on some mythical hero quest. This is a set of dares. We dare you to speak up. We dare you to ask for explanation of code you do not understand. We dare you to figure out how to create your own tools. We dare you to find an end-to-end solution in isolation that the rest of the group will deem worthy.
The dares may not be explicit, but the implied risk involved in speaking up, asking for help, or seeking collaboration is often real: Our reactions to the behaviors listed above are used as indicators of how smart and good we are. These behaviors, and many others that follow along the same lines, create significant barriers to building and operating inclusive teams that can successfully leverage members from varying backgrounds, with varying levels of training, and with varying subject matter expertise.
This presentation will offer ideas for how teams can become more inclusive in order to create a positive, productive environment that allows all members to maximize their efficiency and pleasure. There are quite a few steps an organization can take to improve team structure and processes, but to create an inclusive environment the key concept is support. Putting mutual support, whether requested or not, at the base of every decision we make is the best way to create an inclusive team that builds the commitment and investment of its members while building a product that represents them.
SkyeNets Technologies and Valo Software
Agenda
- Transformation of the Modern workplace
What is Microsoft Teams
- Get an understanding of what Microsoft Teams can do for your organization
- Key features to help increase your organizations productivity
- User Adoption Best Practices and how to manage the risks of Team sprawl
- Demo: Microsoft Teams - Current State
- Demo: Valo Teamwork 2.0 - Future State
- Questions & Answers
A minimum of 100 words each question and References Response #1 – .docxsleeperharwell
A minimum of 100 words each question and References Response #1 – 6) KEEP RESPONSE WITH ANSWER
Make sure the Responses includes the Following: (a) an understanding of the weekly content as supported by a scholarly resource, (b) the provision of a probing question. (c) stay on topic
1) Do you feel the 10 Commandments helps balance chaos and order in this world? Why or Why not? (support your answer with an example)
2) The account of biblical creation can be viewed as a model for innovative and creative leaders when managing chaos because it describes how one is capable of doing great things even when they are faced with many obstacles. Imaging there is a entrepreneur who wants to create his own business. He has to start from ground zero like Jesus did. He has to decide first what he is going to create and what he is going to call it. He then has to establish how the company will survive. For instance, where will it live? What will it need to survive? Then he will go even further to decide the small details all like Jesus did, one step at a time. The story of creation is a great way to think of innovation and leadership. All things are possible through faith and hard work.
3) Creation is the original innovation, it is when everything we know came to be and because of creation we now live in a world where innovation is constant. Biblical creation was the catalyst for all innovation, the past and future belong together including tradition and innovation. God began all living things out of nothing, therefore giving us the ability to innovate as well. During creation, God had a method and was very systematic and because of this, we have what we do today (Rowe, 2019). In terms of chaos, biblical creation shows how the chaos was not only managed but utilized to create something incredible. God managed chaos beautifully in order to create the world we live in today. When God was creating life, he did it in an organized way. This was how he manage chaos in order to create the world. In terms of chaos, staying organized and having a systematic approach is a great way to ensure everything stays managed.
4) I believe that when chaos is created and/or enabled individuals are able to be pushed out of their comfort zones and create, this can ultimately spark innovation. Also when there is a good amount of chaos present, there are many individuals that will feel an urgency to make things right or put things back into place, this healthy amount of chaos can spark excitement and passion into individuals. It is also important that when these times of chaos are made/enabled that as a leader (or someone within the organization) everyone understands what the ultimate goal is. The reason that this is important is because everyone as a team needs to have a clear understanding of what they are working towards and what key role they play in helping the organization to get there.
5) When there is order, that is just what it is, coming to work doing the same thing.
Beyond the spotify model - Team Topologies - Agile Scotland 2019-03-11 - Matt...Matthew Skelton
Beyond the Spotify Model: using team topologies for fast flow and organisation evolution
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway's Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.
About Team Topologies
Team Topologies is a clear, easy-to-follow approach to modern software delivery with an emphasis on optimizing team interactions for flow. Four fundamental types of team - team topologies - and three core team interaction modes combine with awareness of Conway’s Law, team cognitive load, and responsive organization evolution to define a no-nonsense, team-friendly, humanistic approach to building and running software systems.
Devised by experienced IT consultants Matthew Skelton and Manuel Pais, the Team Topologies approach is informed by the well-known DevOps Team Topologies patterns (also authored and curated by Matthew and Manuel). Matthew and Manuel have worked with many organizations around the world to help them shape their teams for modern software delivery, and Team Topologies is the result of that experience.
teamtopologies.com
From a talk given at Agile Scotland on 11 March 2019
In this talk, Matthew Skelton (Skelton Thatcher Consulting) explores five practical, tried-and-tested, real-world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT.
Logging as a live diagnostics vector with sparse event IDs
Operational checklists and 'run book dialogue sheets' as a discovery mechanism for teams
Endpoint healthchecks as a way to assess runtime dependencies and complexity
Correlation IDs beyond simple HTTP calls
Lightweight 'User Personas' as drivers for operational dashboards
These techniques work very differently with different technologies. For instance, an IoT device has limited storage, processing, and I/O, so generation and shipping of logs and metrics looks very different from the cloud or 'serverless' case. However, the principles - logging as a live diagnostics vector, event IDs for discovery, etc - work remarkably well across very different technologies.
From a talk at Agile in the City Bristol 2017 http://agileinthecity.net/2017/bristol/sessions/index.php?session=44
Modern software systems now increasingly span cloud and on-premises deployments and remote embedded devices and sensors. These distributed systems bring challenges with data, connectivity, performance, and systems management; to ensure success, you must design and build with operability as a first-class property.
Matthew Skelton shares five practical, tried-and-tested techniques for improving operability with many kinds of software systems, including the cloud, serverless, on-premises, and the IoT: logging as a live diagnostics vector with sparse event IDs; operational checklists and runbook dialog sheets as a discovery mechanism for teams; endpoint health checks as a way to assess runtime dependencies and complexity; correlation IDs beyond simple HTTP calls; and lightweight user personas as drivers for operational dashboards.
These techniques work very differently with different technologies. For instance, an IoT device has limited storage, processing, and I/O, so generating and shipping of logs and metrics looks very different from cloud or serverless cases. However, the principles—logging as a live diagnostics vector, event IDs for discovery, etc.—work remarkably well across very different technologies.
Drawing from his experience helping teams improve the operability of their software systems, Matthew explains what works (and what doesn’t) and how teams can expand their understanding and awareness of operability through these straightforward, team-friendly techniques.
From a talk given by Matthew Skelton at Velocity Conference EU 2017 - https://conferences.oreilly.com/velocity/vl-eu/public/schedule/detail/61954
Modern software systems now increasingly span cloud, on-premise, and remote embedded devices & sensors. These distributed systems bring challenges with data, connectivity, performance, and systems management, so for business success we need to design and build with operability as a first class property.
In this talk, we explore five practical, tried-and-tested, real world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT:
- Logging as a live diagnostics vector with sparse Event IDs
- Operational checklists and 'Run Book dialogue sheets' as a discovery mechanism for teams
- Endpoint healthchecks as a way to assess runtime dependencies and complexity
- Correlation IDs beyond simple HTTP calls
- Lightweight 'User Personas' as drivers for operational dashboards
These techniques work very differently with different technologies. For instance, an IoT device has limited storage, processing, and I/O, so generation and shipping of logs and metrics looks very different from the cloud or Serverless case. However, the principles - logging as a live diagnostics vector, Event IDs for discovery, etc. - work remarkably well across very different technologies.
Presenters: Matthew Skelton and Rob Thatcher, Skelton Thatcher Consulting
Webinar: Operability is all about making software work well in Production. In this webinar, we explore practical, tried-and-tested, real world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT: logging with Event IDs, Run Book dialogue sheets, endpoint healthchecks, correlation IDs, and lightweight User Personas.
Target audience: Software Developer, Tester, Software Architect, DevOps Engineer, Delivery Manager, Head of Delivery, Head of IT.
Benefits: Attendees will gain insights into operability and why this is important for modern software systems, along with practical experience of techniques to enhance operability in almost any software system they encounter.
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart? By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
Talk given at London DevOps meetup group - June 2017 - https://www.meetup.com/London-DevOps/events/238827763/
Tools like GoCD and TeamCity are excellent components of advanced Continuous Delivery deployment systems. They help us focus on deployment pipelines and the flow of changes, rather than "builds" or "environments". We can further enhance these tools by using frameworks like Rancher to manage GoCD and TeamCity as highly available, always-on deployment services. In this talk, we'll see how to use Rancher to run deployment pipeline tooling like GoCD and TeamCity, and how this lets us focus on the important parts of Continuous Delivery: getting changes to Production safely and rapidly.
How to break apart a monolithic system safely without destroying your team - talk at Velocity Eu Amsterdam on 7 Nov 2016
You'll learn some team-first heuristics to use when decomposing large or monolithic software into smaller pieces.
http://conferences.oreilly.com/velocity/devops-web-performance-eu/public/schedule/detail/52879
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
How to break apart a monolithic system safely without destroying your team
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
Matthew Skelton is co-founder of Skelton Thatcher Consulting / @matthewpskelton
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not measuring delays between value-add activities
- Ignoring Cost-of-Delay and job size
- Not funding the build/test/deployment capability properly
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
Attendees will learn:
1. Why Continuous Delivery (CD) is useful for almost all modern software
2. How to approach CD for databases
3. How to make CD really 'fly' within the organisation
4. How to 'sell' CD to business stakeholders
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not measuring delays between value-add activities
- Ignoring Cost-of-Delay and job size
- Not funding the build/test/deployment capability properly
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
(Talk given at Continuous Lifecycle London 2016)
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not funding the build/test/deployment capability properly
- No effective logging or application metrics
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
Modern log aggregation & search tools provide significant new capabilities for teams building, testing, and running software systems. By treating logging as a core system component, and using techniques such as unique event IDs, transaction tracing, and structured log output, we gain rich insights into application behaviour and health. This talk explains why it is valuable to test aspects of logging and how to do this with modern log aggregation tooling.
Forget the gap between Dev and Ops - the gap between Devs and DBAs is a chasm. Here are some observations from the field about the causes of the rift and some ideas about how to close the gap (and even whether the gap is worth closing). Oh, and I'm writing a book about it.
Treating operational aspects of software as 'non-functional requirements' and 'an Ops problem' rather than a core part of the software product leads to poor live service and unexplained errors in Production.
Traceability, deployability, recoverability, diagnosability, monitorability, and high quality logging are key features of a software system, along with user-visible features surfaced via the UI, or a capability of an API endpoint.
However, many Product Owners understandably feel uneasy about taking on the (necessary) responsibility for prioritising operational features alongside user-visible and API features.
This session brings Scrum Masters and Product Owners up to speed on operational features and covers proven practices for improving operability in an Agile context, empowering Product Owners to make effective prioritisation choices about all kinds of product features, whether user-visible or operational.
How do team topologies influence a DevOps culture? In this talk, we explore different kinds of organisational structures - some good for DevOps, some bad - and see how they affect the kind of collaboration and interaction between teams. Warning: hats are also involved.
Talk at TechUG day in Leeds on 22nd October 2015
The way in which many (most?) software teams use logging needs a re-think as we move into a world of microservices and remote sensors. Instead of using logging merely to dump out stack traces, our logs become a continuous trace of application state, with unique-enough identifiers for every interesting point of execution. We also use transaction identifiers to trace calls across components, services, and queues, so that we can reconstruct distributed calls after the fact. Logging becomes a rich source of insight for developers and operations people alike, as we 'listen to the logs' and tighten feedback cycles to improve our software systems.
Treating operational aspects of software as 'non-functional requirements' and 'an Ops problem' rather than a core part of the software product leads to poor live service and unexplained errors in Production.
Deployability, recoverability, diagnosability, monitorability, and high quality logging are simply features of a software system, along with user-visible features surfaced via the UI, or a capability of an API endpoint.
However, many Product Managers understandably feel uneasy about taking on the (necessary) responsibility for prioritising operational features alongside user-visible and API features.
This session aims to bring Scrum Masters and Product Owners up to speed on operational features, empowering them to make effective prioritisation choices about all kinds of product features, whether user-visible or operational.
The way in which many (most?) software teams use logging needs a re-think as we move into a world of microservices and remote sensors. Instead of using logging merely to dump out stack traces, our logs become a continuous trace of application state, with unique-enough identifiers for every interesting point of execution. We also use transaction identifiers to trace calls across components, services, and queues, so that we can reconstruct distributed calls after the fact. Logging becomes a rich source of insight for developers and operations people alike, as we 'listen to the logs' and tighten feedback cycles to improve our software systems.
What team configuration is right for DevOps to work? Devs doing Ops? Ops doing Dev? Everyone doing a bit of everything, or a special new silo doing Docker and Jenkins in the corner of the room?
In this talk, Matthew Skelton and Rob Thatcher joins speculation with practical in-the-trenches experience to arrive at some working 'team topologies' for effective DevOps.
Also involves audience participation. And hats :)
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
Into the Box Keynote Day 2: Unveiling amazing updates and announcements for modern CFML developers! Get ready for exciting releases and updates on Ortus tools and products. Stay tuned for cutting-edge innovations designed to boost your productivity.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns
Unlocking Business Potential: Tailored Technology Solutions by Prosigns
Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support.
Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth.
Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices.
AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making.
Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency.
DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration.
Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly.
Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business.
Join us on a journey of innovation and growth. Let's partner for success with Prosigns.
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Enhancing Project Management Efficiency_ Leveraging AI Tools like ChatGPT.pdfJay Das
With the advent of artificial intelligence or AI tools, project management processes are undergoing a transformative shift. By using tools like ChatGPT, and Bard organizations can empower their leaders and managers to plan, execute, and monitor projects more effectively.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTier1 app
Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.
SOCRadar Research Team: Latest Activities of IntelBrokerSOCRadar
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
Developing Distributed High-performance Computing Capabilities of an Open Sci...
How and why to design your teams for modern software - JAX DevOps - April 2017
1. How and why to design your
teams for modern software
systems
Matthew Skelton | Skelton Thatcher Consulting
@matthewpskelton | skeltonthatcher.com
JAX DevOps / JAX Finance - #jaxdevops / #jaxfinance
05 April 2017, London UK
2. Today
•Conway’s Law (or heuristic)
•Cognitive Load for teams
•Real-world Team Topologies
•Guidelines for team design
4. Organisation design for effective software systems
Tutorial / Workshop
Weds 24 May 2017, Manchester
https://ti.to/skelton-thatcher-consulting/organisation-design-for-effective-software-systems-tutorial-workshop
15. “organizations which design
systems ... are constrained to
produce designs which are copies
of the communication structures of
these organizations”
– Mel Conway, 1968
http://www.melconway.com/Home/Conways_Law.html
16. “if the architecture of the system and
the architecture of the organization
are at odds, the architecture of the
organization wins”
– Ruth Malan, 2008
http://traceinthesand.com/blog/2008/02/13/conways-law/
17. “We find strong evidence to support
the hypothesis that a product’s
architecture tends to mirror the
structure of the organization in
which it is developed.”
– MacCormack et al, 2012
MacCormack, Alan, Carliss Y. Baldwin, and John Rusnak. ‘Exploring the Duality Between Product and Organizational Architectures: A Test of the
“Mirroring” Hypothesis’, 1 October 2012. http://www.hbs.edu/faculty/Pages/item.aspx?num=43260.
29. Science since 1988
• Driskell et al, 1999 ‘Does Stress Lead to a Loss of Team Perspective?’ Group Dynamics:
Theory, Research, and Practice 3, no. 4 (1999): 291.
• Fan et al, 2010 ‘Learning HMM-Based Cognitive Load Models for Supporting Human-Agent
Teamwork’. Cognitive Systems Research 11, no. 1 (2010): 108–119.
• Ilgen & Hollenbeck, 1993 ‘Effective Team Performance under Stress and Normal Conditions:
An Experimental Paradigm, Theory and Data for Studying Team Decision Making in
Hierarchical Teams with Distributed Expertise’. DTIC Document, 1993.
• Johnston et al, 2002 ‘Application of Cognitive Load Theory to Developing a Measure of Team
Decision Efficiency’. DTIC Document, 2002.
• Sweller, John, 1994 ‘Cognitive Load Theory, Learning Difficulty, and Instructional Design’.
Learning and Instruction 4 (1994): 295–312.
• Sweller, John, 1988. ‘Cognitive Load during Problem Solving: Effects on Learning’. Cognitive
Science 12, no. 2 (1988): 257–285.
30. “stress impacts team
performance … by narrowing or
weakening the team-level
perspective required for
effective team behavior.”
– Driskell et al, 1999
Group Dynamics: Theory, Research, and Practice 1999, Vol. 3, No. 4,291-302
75. “stress impacts team
performance … by narrowing or
weakening the team-level
perspective required for
effective team behavior.”
– Driskell et al, 1999
Group Dynamics: Theory, Research, and Practice 1999, Vol. 3, No. 4,291-302
76. Match the team responsibility
to the cognitive load that the
team can handle
87. Organisation design for effective software systems
Tutorial / Workshop
Weds 24 May 2017, Manchester
https://ti.to/skelton-thatcher-consulting/organisation-design-for-effective-software-systems-tutorial-workshop