Presented by Irfan Ikram
This is a walk through of how Dealogic has adopted agile processes and more importantly scaled them as it has grown as a business.
Topics covered include:
- DevOps Culture (You Build it, You Run it )
- Rapid Delivery
- Minimizing Collaboration
- Empowering Teams
- Scaling Agile across Teams
- Breaking down the monolith product
- Managing Continuous Improvement
- Effective MVP
- Showing Value Delivered
This document provides tips for facilitating efficient and effective meetings. It begins by advising facilitators to ensure they can remain neutral on discussion topics and to prepare by understanding meeting attendees and objectives. It recommends clarifying expectations, goals, agendas and notes responsibilities. The tips suggest paying attention to time limits and participant engagement and understanding. Facilitators should help capture action items and decisions clearly and ensure commitments are obtained. The overall message is the importance of preparation, clarity and participant involvement to achieve meeting goals.
Seven elements of technical Agility - Gil Broza - Agile Israel 2013AgileSparks
This document discusses technical agility in agile software development. It outlines seven elements of technical agility: evolutionary design, rapid feedback, small safe steps, simplicity, clean code, ownership vs rental mentality, and shared responsibility. It provides examples of how each element can improve a team's ability to evolve software quickly while maintaining quality. The document is aimed at helping teams address technical challenges that can arise when insufficient attention is paid to the technical aspects of agile.
What is quality, and how do we build it in Maryam Umar
The document discusses quality and how to build it into software development processes. It begins by noting that quality is subjective and depends on many factors. It then recommends starting by creating a quality vision, selecting some metrics to measure, and evolving those metrics over time based on learnings. Common mistakes like adding extensive testing late or creating separate quality teams are noted. The document provides suggestions for areas to measure like releases, product quality, and process quality to improve software delivery performance. It emphasizes the importance of culture and psychological safety.
The document discusses a startup company that is looking for a development partner to help build their disruptive product idea. They outline 10 criteria for what they need in a partner, including sharing risks, experience building products, flexibility, and delivering on time and budget. The document is from Cuelogic Technologies, an Indian software development company, positioning themselves as a potential partner that meets all of the criteria through their agile approach, offshore pricing model, and past success working with other startups and businesses.
What Patterns to Avoid in Agile Ceremonies?Inflectra
This is a presentation delivered by Dr. Sriram Rajagopalan of Inflectra as part of Inflectra's webinar 4-part series called: Journey into Agile with Inflectra
To learn more about the webinar series, visit: http://www.inflectra.com/Ideas/Entry/agile-with-inflectra-a-webinar-course-753.aspx
Individuals and interactions - Gil Broza - Agile Israel 2013AgileSparks
This document outlines 10 lessons for putting people before process in agile development environments. It begins by discussing the traditional "waterfall" development model and the need for a new approach prioritizing individuals and interactions. The lessons then focus on treating people as more than resources, maintaining focus through small cycles and frequent delivery, nurturing the joy of delivering value to customers, taking small safe steps with feedback, tailoring environments to individuals, investing in high-performing teams, leading collaboratively instead of strictly managing, and allowing human conduct to guide practices over rigid adherence to "best practices". An online conference is promoted to learn more about these people-centric lessons.
Seven Keys to Navigating Your Agile Testing TransitionTechWell
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? And when things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join seasoned agile testing coach Bob Galen as he share lessons from his most successful agile testing transitions. You’ll explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale stories of agile testing excellence. You’ll examine the mistakes, adjustments, and the successes—so you’ll learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
This document discusses how Agile development practices that started in development functions are now spreading to other departments in technology companies. While Agile has benefits, its effects on relationships between development teams and other departments need to be addressed consciously. The document advocates for a more deliberate adoption of Agile practices across product-related functions to fully realize Agile's potential and avoid unintended consequences. It notes that Agile development naturally leads to the need for Agile engagement across the entire company.
This document provides tips for facilitating efficient and effective meetings. It begins by advising facilitators to ensure they can remain neutral on discussion topics and to prepare by understanding meeting attendees and objectives. It recommends clarifying expectations, goals, agendas and notes responsibilities. The tips suggest paying attention to time limits and participant engagement and understanding. Facilitators should help capture action items and decisions clearly and ensure commitments are obtained. The overall message is the importance of preparation, clarity and participant involvement to achieve meeting goals.
Seven elements of technical Agility - Gil Broza - Agile Israel 2013AgileSparks
This document discusses technical agility in agile software development. It outlines seven elements of technical agility: evolutionary design, rapid feedback, small safe steps, simplicity, clean code, ownership vs rental mentality, and shared responsibility. It provides examples of how each element can improve a team's ability to evolve software quickly while maintaining quality. The document is aimed at helping teams address technical challenges that can arise when insufficient attention is paid to the technical aspects of agile.
What is quality, and how do we build it in Maryam Umar
The document discusses quality and how to build it into software development processes. It begins by noting that quality is subjective and depends on many factors. It then recommends starting by creating a quality vision, selecting some metrics to measure, and evolving those metrics over time based on learnings. Common mistakes like adding extensive testing late or creating separate quality teams are noted. The document provides suggestions for areas to measure like releases, product quality, and process quality to improve software delivery performance. It emphasizes the importance of culture and psychological safety.
The document discusses a startup company that is looking for a development partner to help build their disruptive product idea. They outline 10 criteria for what they need in a partner, including sharing risks, experience building products, flexibility, and delivering on time and budget. The document is from Cuelogic Technologies, an Indian software development company, positioning themselves as a potential partner that meets all of the criteria through their agile approach, offshore pricing model, and past success working with other startups and businesses.
What Patterns to Avoid in Agile Ceremonies?Inflectra
This is a presentation delivered by Dr. Sriram Rajagopalan of Inflectra as part of Inflectra's webinar 4-part series called: Journey into Agile with Inflectra
To learn more about the webinar series, visit: http://www.inflectra.com/Ideas/Entry/agile-with-inflectra-a-webinar-course-753.aspx
Individuals and interactions - Gil Broza - Agile Israel 2013AgileSparks
This document outlines 10 lessons for putting people before process in agile development environments. It begins by discussing the traditional "waterfall" development model and the need for a new approach prioritizing individuals and interactions. The lessons then focus on treating people as more than resources, maintaining focus through small cycles and frequent delivery, nurturing the joy of delivering value to customers, taking small safe steps with feedback, tailoring environments to individuals, investing in high-performing teams, leading collaboratively instead of strictly managing, and allowing human conduct to guide practices over rigid adherence to "best practices". An online conference is promoted to learn more about these people-centric lessons.
Seven Keys to Navigating Your Agile Testing TransitionTechWell
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? And when things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join seasoned agile testing coach Bob Galen as he share lessons from his most successful agile testing transitions. You’ll explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale stories of agile testing excellence. You’ll examine the mistakes, adjustments, and the successes—so you’ll learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
This document discusses how Agile development practices that started in development functions are now spreading to other departments in technology companies. While Agile has benefits, its effects on relationships between development teams and other departments need to be addressed consciously. The document advocates for a more deliberate adoption of Agile practices across product-related functions to fully realize Agile's potential and avoid unintended consequences. It notes that Agile development naturally leads to the need for Agile engagement across the entire company.
The core of the practice of Agile is the delivery of individual projects; it's where most practitioners start out, and it fundamentally changes the way a project team works together and works with their stakeholders.
Scrum is one of the most popular Agile delivery approaches at the moment. In this APN session, Carolyn uses one of her recent projects as a way to illustrate each facet of Scrum and how it panned out in real life, from start to finish.
Agile Testing is nonsense, because Agile is about testing!Andrea Tomasini
Testing is an attitude which brings us to trust results based on the fact that we can validate them. Testing is an approach which allows us to think about how to verify we did the right thing even before starting. Testing is a practice which allows us to write effective tests that can be repeated indefinitely while systematically producing consistent results.
Agile is built around the idea of managing complex projects, recognizing the importance of emerging results and verifying in a very disciplined way the assumptions and hypothesis we make as often and as thoroughly as possible. This means testing everything we do, every day ... So if you are truly Agile, you are living testing in every second of your life!
A survey of the Agile landscape, and examination of Agile practices at several levels of detail within the project lifecycle.
Presented at PMI Auckland Branch meeting on 21 May 2009.
For discussion and Q&A please visit fronde.com/blog
Eind augustus is het Accelerate: State of DevOps Report 2018 uitgebracht. Zoals in dit rapport wordt aangegeven is IT belangrijk voor veel organisaties, en door goed te zijn op IT gebied wordt het eenvoudiger om (commerciële) bedrijfsdoelstellingen te behalen. Goed presteren als organisatie kan worden bereikt door goed te zijn (en elke dag beter te worden) DevOps gebied. Beter worden in DevOps betekent dat je elke dag moet werken aan het verbeteren van competenties die belangrijk zijn wanneer je in DevOps werkt. Maar welke competenties moet je ontwikkelen? En hoe presteer je daar vandaag op? Hoe kun je verbeteren op deze competenties zodat je morgen, volgende week en volgende maand beter wordt?
In deze sessie zal ik een overzicht geven van het DevOps Acceleration Program zoals wij deze hebben ontwikkelen. Dit programma zal een antwoord geven op voorgaande vragen en helpen te bepalen waar je welke verbetering kunt en moet doorvoeren. Belangrijk onderdeel van dit programma is het DevOps Assessment ontwikkeld door DevOps Research and Assessment (DORA), maar het is meer dan dat. Door een gezamenlijk een verbeterplan voor de komende 6 maanden op maat op te stellen en te focussen op een beperkt aantal competenties kun je daadwerkelijk verbeteren. Na 6 maanden doen we een meting om de gerealiseerde voortgang te bepalen en input te geven voor een nieuw verbeterplan.
During the Agile Austria Conference 2017.
Speaker: Rainer Wendt
For years there has been a trench warfare about which way is better, faster and cheaper - Agile or Waterfall; Hybrid projects will finally make it!
Seven Keys to Navigating Your Agile Testing TransitionTechWell
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? When things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join Bob Galen and Mary Thorn as they share lessons from their most successful agile testing transitions. Explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale—all building agile testing excellence. Examine the mistakes, adjustments, and the successes, and learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
Communicating agile project status to executive managersAgileDad
The document discusses communicating agile project status to executive managers. It provides tips for establishing trust between management and agile teams. It also outlines appropriate roles for executives, managers, and teams in an agile environment. The document recommends focusing reporting on working software demonstrations and metrics like burn down charts and velocity, rather than intensive intra-sprint reporting.
Scrum Patterns: The New Defacto Scrum StandardJames Coplien
This is the talk I gave at the Japanese Scrum Gathering on 28 February 2015. I'm uploading it at the request of Osamu Tomita who thought that others would like to see it. Sorry it's only a PDF — Slideshare is still living in the Microsoft dark ages, and can't handle even the PowerPoint export that I generated.
Agile Project Failures: Root Causes and Corrective ActionsTechWell
Agile initiatives always begin with the best of intentions—accelerate delivery, better meet customer needs, or improve software quality. Unfortunately, some agile projects do not deliver on these expectations. If you want help to ensure the success of your agile project or get an agile project back on track, this session is for you. Jeff Payne discusses the most common causes of agile project failure and how you can avoid these issues—or mitigate their damaging effects. Poor project management, ineffective requirements development, failed communications, software development problems, and (non)agile testing can all contribute to project failure. Learn practical tips and techniques for identifying early warning signs that your agile project might be in trouble and how you can best get your project back on track. Gain the knowledge you need to guide your organization toward agile project implementations that serve the business and the stakeholders.
Building Gender Diversity in Organizations to Deliver Award-Winning ProductsVMware Tanzu
The document summarizes a presentation about a program called the IT Circle launched by OneMagnify to build gender diversity in IT. The IT Circle aims to empower and enable women in IT to build leadership capabilities and technical excellence through knowledge sharing and networking opportunities. It discusses challenges women face in IT and how the IT Circle identifies opportunities to address these challenges. Examples of IT Circle events and programs delivered so far to develop women's personal brands, technical skills, and career awareness are provided. The summary concludes by noting positive results seen so far including more women moving into IT roles and departments at OneMagnify and long term goals to further increase women in leadership and IT positions and their retention.
More than five years ago, Frequentis introduced agile development methods in the department of air traffic management to coordinate projects and product development of safety-critical applications out of dispersed and distributed teams in two countries.
This talk presents the approach used, questions that arose, decisions taken, the observed results, impact on team motivation, and lessons learned throughout the process.
Since then, agile methodologies have rolled out across the company into all departments, and into dispersed and distributed teams in several countries. Agility as a core value is dispersing throughout the company – from team level to corporate overview.
Witness the transformation of a waterfall-driven business into an increasingly agile organization!
This document discusses strategies for transitioning large enterprises to agile practices. It introduces the ADAPT framework which involves creating Awareness of issues, building Desire for change, developing Ability to work in agile ways, promoting early successes, and transferring agile practices throughout the organization. Key challenges in enterprise agile adoption are mixing agile with traditional processes, compliance issues, distributed teams, and individual resistance. The document advocates establishing an Enterprise Transition Community and Improvement Communities to guide the transition through iterative improvements.
Balancing the tension between Lean and AgileJames Coplien
Many people equate Lean and agile or claim that one is a subset of the other. In fact, they have almost opposite emphases: thinking versus doing; teams versus individuals; planning versus reacting; and many more. This talk will help you clarify the distinction in a way that will help you focus soberly on how to improve your environment, team, product and process, by going beyond the buzzwords to the fundamental building blocks.
Skiing and boxing: coaching product and enterprise teamsSergey Prokhorenko
Successful Agile transitions depend on a coaching approach just as much as the development of a good sports team. One is not going to assign the same exercise programs to a pro skier and a boxer; the same applies to different software development teams.
In this study we summarize experiences from two Agile transformation projects, a travel website and investment bank risk management software. We discuss common points and distinctive features in requirements management, innovations, customer collaboration and team motivation.
The Myriad faces of Agile Training & CertificationSunil Mohal
The document provides an overview of agile training and certifications. It begins with the origins and principles of agile software development. It then discusses several agile frameworks like Scrum and SAFe and the associated certifications offered by organizations like Scrum Alliance, Scrum.org, ICAgile, and Lean Kanban University. It provides details on popular certifications for roles like Scrum Master, Product Owner, and Agile coach and levels from foundation to expert.
Will Agile work in my embedded development environment?bmyllerup
Agile approaches like Scrum is designed for software development, but will it also work when we add electronics development and mechanical construction to the practices? Come and get insights from the experiences of a Certified Scrum Trainer who actually did the work himself. You will learn about how to setup teams that have the combined skill-set of software, electronics and mechanical engineers...
The document discusses techniques from Extreme Programming (XP) without code examples. It advocates that technical practices like test-driven development, continuous integration, refactoring, and mob programming are important for agile adoption and should not be treated as secondary to management practices. Test-driven development is discussed as an alternative to just unit testing that provides a safety net and documents what a system should do. Continuous integration and integrating code several times a day is recommended to detect problems early.
Mike Cohn gave a presentation on leading self-organizing teams at the Norwegian Developer's Conference. He discussed what self-organizing teams are and how they operate as complex adaptive systems. Cohn explained that managers can subtly influence self-organizing teams without direct control through containers, differences among team members, and transforming exchanges between members. He provided examples of how to apply this model to influence how a team evolves over time, such as selecting the team's environment, defining performance metrics, and energizing the team with a clear goal.
Technical stream: Moving to test- and behaviour-driven development
In this session Kim will be going over the benefits of introducing TDD and BDD: How to introduce them, their differences, how to deal with push back from team members and upper management.
The benefits of driving our development with tests, how it helps the quality and maintainability of our software, how it helps the business and the client. The types of tests that best serve us for the different layers of our application development and how business people can get benefit from TDD and especially BDD.
When Kim’s not working at his day job as a senior software engineer, consultant, Scrum Master, you can find him indulging his passions of software architecture, creating and exploiting software and networks. In order to develop and release software faster, it's Kim’s aim to increase the awareness for the need of higher quality incremental software releases.
Agile Chennai 2021 | Achieving High DevOps Maturity through Platform Engineer...AgileNetwork
Agile Chennai 2021
Achieving High DevOps Maturity through Platform Engineering Practices - by Satish Chandran
Director, DevOps and IT Security, Gain Credit
Casro Presentation Project And Change Management 1st June 2011sam_inamdar
This presentation shares experiences from a collaborative approach to creating innovative solutions through technology, including insights on management of a technology project life cycle; using tracking tools for change management; managing communications for a virtual team; and other means to
foster collaboration.
The core of the practice of Agile is the delivery of individual projects; it's where most practitioners start out, and it fundamentally changes the way a project team works together and works with their stakeholders.
Scrum is one of the most popular Agile delivery approaches at the moment. In this APN session, Carolyn uses one of her recent projects as a way to illustrate each facet of Scrum and how it panned out in real life, from start to finish.
Agile Testing is nonsense, because Agile is about testing!Andrea Tomasini
Testing is an attitude which brings us to trust results based on the fact that we can validate them. Testing is an approach which allows us to think about how to verify we did the right thing even before starting. Testing is a practice which allows us to write effective tests that can be repeated indefinitely while systematically producing consistent results.
Agile is built around the idea of managing complex projects, recognizing the importance of emerging results and verifying in a very disciplined way the assumptions and hypothesis we make as often and as thoroughly as possible. This means testing everything we do, every day ... So if you are truly Agile, you are living testing in every second of your life!
A survey of the Agile landscape, and examination of Agile practices at several levels of detail within the project lifecycle.
Presented at PMI Auckland Branch meeting on 21 May 2009.
For discussion and Q&A please visit fronde.com/blog
Eind augustus is het Accelerate: State of DevOps Report 2018 uitgebracht. Zoals in dit rapport wordt aangegeven is IT belangrijk voor veel organisaties, en door goed te zijn op IT gebied wordt het eenvoudiger om (commerciële) bedrijfsdoelstellingen te behalen. Goed presteren als organisatie kan worden bereikt door goed te zijn (en elke dag beter te worden) DevOps gebied. Beter worden in DevOps betekent dat je elke dag moet werken aan het verbeteren van competenties die belangrijk zijn wanneer je in DevOps werkt. Maar welke competenties moet je ontwikkelen? En hoe presteer je daar vandaag op? Hoe kun je verbeteren op deze competenties zodat je morgen, volgende week en volgende maand beter wordt?
In deze sessie zal ik een overzicht geven van het DevOps Acceleration Program zoals wij deze hebben ontwikkelen. Dit programma zal een antwoord geven op voorgaande vragen en helpen te bepalen waar je welke verbetering kunt en moet doorvoeren. Belangrijk onderdeel van dit programma is het DevOps Assessment ontwikkeld door DevOps Research and Assessment (DORA), maar het is meer dan dat. Door een gezamenlijk een verbeterplan voor de komende 6 maanden op maat op te stellen en te focussen op een beperkt aantal competenties kun je daadwerkelijk verbeteren. Na 6 maanden doen we een meting om de gerealiseerde voortgang te bepalen en input te geven voor een nieuw verbeterplan.
During the Agile Austria Conference 2017.
Speaker: Rainer Wendt
For years there has been a trench warfare about which way is better, faster and cheaper - Agile or Waterfall; Hybrid projects will finally make it!
Seven Keys to Navigating Your Agile Testing TransitionTechWell
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? When things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join Bob Galen and Mary Thorn as they share lessons from their most successful agile testing transitions. Explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale—all building agile testing excellence. Examine the mistakes, adjustments, and the successes, and learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
Communicating agile project status to executive managersAgileDad
The document discusses communicating agile project status to executive managers. It provides tips for establishing trust between management and agile teams. It also outlines appropriate roles for executives, managers, and teams in an agile environment. The document recommends focusing reporting on working software demonstrations and metrics like burn down charts and velocity, rather than intensive intra-sprint reporting.
Scrum Patterns: The New Defacto Scrum StandardJames Coplien
This is the talk I gave at the Japanese Scrum Gathering on 28 February 2015. I'm uploading it at the request of Osamu Tomita who thought that others would like to see it. Sorry it's only a PDF — Slideshare is still living in the Microsoft dark ages, and can't handle even the PowerPoint export that I generated.
Agile Project Failures: Root Causes and Corrective ActionsTechWell
Agile initiatives always begin with the best of intentions—accelerate delivery, better meet customer needs, or improve software quality. Unfortunately, some agile projects do not deliver on these expectations. If you want help to ensure the success of your agile project or get an agile project back on track, this session is for you. Jeff Payne discusses the most common causes of agile project failure and how you can avoid these issues—or mitigate their damaging effects. Poor project management, ineffective requirements development, failed communications, software development problems, and (non)agile testing can all contribute to project failure. Learn practical tips and techniques for identifying early warning signs that your agile project might be in trouble and how you can best get your project back on track. Gain the knowledge you need to guide your organization toward agile project implementations that serve the business and the stakeholders.
Building Gender Diversity in Organizations to Deliver Award-Winning ProductsVMware Tanzu
The document summarizes a presentation about a program called the IT Circle launched by OneMagnify to build gender diversity in IT. The IT Circle aims to empower and enable women in IT to build leadership capabilities and technical excellence through knowledge sharing and networking opportunities. It discusses challenges women face in IT and how the IT Circle identifies opportunities to address these challenges. Examples of IT Circle events and programs delivered so far to develop women's personal brands, technical skills, and career awareness are provided. The summary concludes by noting positive results seen so far including more women moving into IT roles and departments at OneMagnify and long term goals to further increase women in leadership and IT positions and their retention.
More than five years ago, Frequentis introduced agile development methods in the department of air traffic management to coordinate projects and product development of safety-critical applications out of dispersed and distributed teams in two countries.
This talk presents the approach used, questions that arose, decisions taken, the observed results, impact on team motivation, and lessons learned throughout the process.
Since then, agile methodologies have rolled out across the company into all departments, and into dispersed and distributed teams in several countries. Agility as a core value is dispersing throughout the company – from team level to corporate overview.
Witness the transformation of a waterfall-driven business into an increasingly agile organization!
This document discusses strategies for transitioning large enterprises to agile practices. It introduces the ADAPT framework which involves creating Awareness of issues, building Desire for change, developing Ability to work in agile ways, promoting early successes, and transferring agile practices throughout the organization. Key challenges in enterprise agile adoption are mixing agile with traditional processes, compliance issues, distributed teams, and individual resistance. The document advocates establishing an Enterprise Transition Community and Improvement Communities to guide the transition through iterative improvements.
Balancing the tension between Lean and AgileJames Coplien
Many people equate Lean and agile or claim that one is a subset of the other. In fact, they have almost opposite emphases: thinking versus doing; teams versus individuals; planning versus reacting; and many more. This talk will help you clarify the distinction in a way that will help you focus soberly on how to improve your environment, team, product and process, by going beyond the buzzwords to the fundamental building blocks.
Skiing and boxing: coaching product and enterprise teamsSergey Prokhorenko
Successful Agile transitions depend on a coaching approach just as much as the development of a good sports team. One is not going to assign the same exercise programs to a pro skier and a boxer; the same applies to different software development teams.
In this study we summarize experiences from two Agile transformation projects, a travel website and investment bank risk management software. We discuss common points and distinctive features in requirements management, innovations, customer collaboration and team motivation.
The Myriad faces of Agile Training & CertificationSunil Mohal
The document provides an overview of agile training and certifications. It begins with the origins and principles of agile software development. It then discusses several agile frameworks like Scrum and SAFe and the associated certifications offered by organizations like Scrum Alliance, Scrum.org, ICAgile, and Lean Kanban University. It provides details on popular certifications for roles like Scrum Master, Product Owner, and Agile coach and levels from foundation to expert.
Will Agile work in my embedded development environment?bmyllerup
Agile approaches like Scrum is designed for software development, but will it also work when we add electronics development and mechanical construction to the practices? Come and get insights from the experiences of a Certified Scrum Trainer who actually did the work himself. You will learn about how to setup teams that have the combined skill-set of software, electronics and mechanical engineers...
The document discusses techniques from Extreme Programming (XP) without code examples. It advocates that technical practices like test-driven development, continuous integration, refactoring, and mob programming are important for agile adoption and should not be treated as secondary to management practices. Test-driven development is discussed as an alternative to just unit testing that provides a safety net and documents what a system should do. Continuous integration and integrating code several times a day is recommended to detect problems early.
Mike Cohn gave a presentation on leading self-organizing teams at the Norwegian Developer's Conference. He discussed what self-organizing teams are and how they operate as complex adaptive systems. Cohn explained that managers can subtly influence self-organizing teams without direct control through containers, differences among team members, and transforming exchanges between members. He provided examples of how to apply this model to influence how a team evolves over time, such as selecting the team's environment, defining performance metrics, and energizing the team with a clear goal.
Technical stream: Moving to test- and behaviour-driven development
In this session Kim will be going over the benefits of introducing TDD and BDD: How to introduce them, their differences, how to deal with push back from team members and upper management.
The benefits of driving our development with tests, how it helps the quality and maintainability of our software, how it helps the business and the client. The types of tests that best serve us for the different layers of our application development and how business people can get benefit from TDD and especially BDD.
When Kim’s not working at his day job as a senior software engineer, consultant, Scrum Master, you can find him indulging his passions of software architecture, creating and exploiting software and networks. In order to develop and release software faster, it's Kim’s aim to increase the awareness for the need of higher quality incremental software releases.
Agile Chennai 2021 | Achieving High DevOps Maturity through Platform Engineer...AgileNetwork
Agile Chennai 2021
Achieving High DevOps Maturity through Platform Engineering Practices - by Satish Chandran
Director, DevOps and IT Security, Gain Credit
Casro Presentation Project And Change Management 1st June 2011sam_inamdar
This presentation shares experiences from a collaborative approach to creating innovative solutions through technology, including insights on management of a technology project life cycle; using tracking tools for change management; managing communications for a virtual team; and other means to
foster collaboration.
This proposal from Canang Technologies outlines a Developer to Developer (D2D) training program to upskill an organization's technical staff. The objectives are to align IT with business units, equip staff with new skills like Java Enterprise and agile development, and help deliver the organization's application while mentoring the team. The customized, hands-on training uses techniques like domain modeling, code reviews, and pairing developers with Canang's experts. A sample 12-month timeline details biweekly sessions addressing topics such as requirements, architecture, and security. Case studies show Canang helped a university team successfully build 3 internal apps while increasing their skills and engagement over 40 sessions.
This document introduces DevOps, including how the DevOps movement took place originating from practices like continuous integration and infrastructure as code. It describes challenges of traditional software delivery approaches and how DevOps aims to reduce gaps through practices like integrating development and operations processes. DevOps benefits continuous delivery through collaboration between dev and ops and supporting tools. It promotes principles like system thinking, amplifying feedback loops, and continual learning.
This document discusses DevOps tools and practices. It covers DevOps toolchains, building deployment pipelines gradually through automation, and the importance of knowledge over tools. Continuous integration, continuous delivery, and deploying changes frequently are emphasized. Visualizing processes, integrating changes daily, keeping builds fast and tests automated, and deploying to production-like environments are presented as core DevOps practices.
The document discusses digitalization through the use of domain-specific languages (DSLs). It suggests that DSLs can help accelerate development, simplify customization, and express business goals, requirements, design, and implementation in a single language. The document outlines considerations for whether an organization needs a DSL, how to structure a proof of concept, and how to ensure long term maintenance and adoption of the DSL approach.
DevOps is a practice that aims to break down barriers between development and operations teams. It originated as teams adopted Agile methodologies and moved toward continuous delivery of software. DevOps aims to speed up delivery through practices like continuous integration, infrastructure as code, and breaking down silos between teams. The document outlines the history and benefits of DevOps, including increased speed, reliability, collaboration and security. It also defines key DevOps practices and provides examples of how they work.
Tester’s considerations when moving towards successful CI/CDDerk-Jan de Grood
These are the slides of the tutorial I gave at QA&Testing in Bilbao on 17 October 2018
Continuous integration and deployment (CI/CD) empowers organizations to bring their solution in production fast and frequent. This interactive session will share the benefits of this concept and introduce eight conditions that need to be met in order to make CI/CD a success. After this brief introduction, we will make small groups and explore these conditions, exchange experiences and you will get an understanding what needs to be improved in your organization. Talk to your peers and learn where they stand. Of course each of the groups will share their learnings, so we all go home with an understanding of how you can benefit from CI/CD and what needs to be done to make it work.
Finally we will see what test strategy we would advise if our company would decide to move towards CI/CD and this cover we consider much more than just automate our tests…
STRIVING FOR CONTINUOUS INTEGRATION AND DEPLOYMENT
Continuous integration and deployment (CI/CD) empowers organizations to bring their solution in production fast and frequent. This interactive session will share the benefits of this concept and introduce eight conditions that need to be met in order to make CI/CD a success. After this brief introduction, we will make small groups and explore these conditions, exchange experiences and you will get an understanding what needs to be improved in your organization. Talk to your peers and learn where they stand. Of course each of the groups will share their learnings, so we all go home with an understanding of how you can benefit from CI/CD and what needs to be done to make it work.
The document discusses DevOps, which aims to improve collaboration between development and operations teams. It notes past failed attempts to implement systems where operations took 9 months to set up virtual machines but they were not ready for development teams. Similarly, development once spent 2 months on automated deployments but operations still wanted a user interface. The document advocates adopting a DevOps culture and mindset to continuously deliver value to customers by reducing time to market through collaboration between teams and automation. DevOps integrates development and operations to improve productivity and measure application performance.
Buddy, partnered with industry leaders such as Amazon, Docker, Github, Microsoft, and Google, is a winning development automation platform that serves a rapidly growing market valued to become $345 billion by 2022. Over 7,000 developers use Buddy every day across 120+ countries. Featured customers: INC. Magazine, CGI.com & ING Bank. Our vision is to become the backbone on which talented people can build world-altering apps & services. Our goal is to take the load off millions of developers by offloading everything that can be automated – giving them back the time for being creative.
This document outlines a 5 step process for DevOps success developed by Copado. The steps are:
1. Visibility - Teams need visibility into the entire development pipeline from planning to deployment to customer adoption. This situational awareness helps improve processes and address bottlenecks.
2. Quality - With improved visibility, teams can identify quality gaps and shift testing left to reduce defects and speed recovery.
3. Speed - A foundation of visibility and quality allows teams to move faster by automating processes and eliminating downtime to rapidly deploy changes.
4. Innovation - Fast and reliable deployments free up teams to focus on high impact innovations by prioritizing work, tracking adoption, and enabling collaboration.
Measure and Accelerate Your Software DeliveryAnand Chauhan
Many companies adopt the DevOps practices, but struggle to realize the impact the DevOps investment is making to improve software delivery. Disconnected teams, tools and increasing complexity leads to no visibility into how and where to optimize the process, deliver value to customers and maximize return on that investment. The session covers industry trends, critical need for measurement and touches on CloudBees DevOptics solution purpose built to provide immediate transparency you need to measure, optimize and improve your software delivery process.
Scale Continuous Deployment to Production with DeployHub and CloudBeesDeborah Schalm
Moving from a simple Jenkins CI workflow to Continuous Delivery requires a focus on Continuous Deployment. Join us for a discussion on how to integrate DeployHub, an open source application release automation solution, into your CloudBees pipeline to support automated deployments across dev, test and production. You will see how to create a Continuous Feedback loop, track change request and support rollback and version jumping all orchestrated via the CloudBees platform. Maturing your CD process to support continuous deployment using ARA has always been possible, but extremely expensive. DeployHub OSS solves the budget problem, integrated into CloudBees - and it is agentless for fast easy implementation.
Scale Continuous Deployment to Production with DeployHub and CloudBeesDevOps.com
Moving from a simple Jenkins CI workflow to Continuous Delivery requires a focus on Continuous Deployment. Join us for a discussion on how to integrate DeployHub, an open source application release automation solution, into your CloudBees pipeline to support automated deployments across dev, test and production. You will see how to create a Continuous Feedback loop, track change request and support rollback and version jumping all orchestrated via the CloudBees platform. Maturing your CD process to support continuous deployment using ARA has always been possible, but extremely expensive. DeployHub OSS solves the budget problem, integrated into CloudBees - and it is agentless for fast easy implementation.
Agile .NET Development with BDD and Continuous IntegrationQuan Truong Anh
Introducing BDD - Behavior Driven Development
Introducing CI - Continuous Integration
Demo using Open Source Software tools (Git, Jenkins, SonarQube) with configuration for .NET (MSBuild)
Agile .NET Development with BDD and Continuous IntegrationTung Nguyen Thanh
Agile .NET Development with BDD and Continuous Integration
Áp dụng CI là một phần không thể thiếu nếu bạn mong muốn nâng cao năng suất và giảm thiểu lỗi lầm khi phát triển cũng như deploy sản phẩm qua việc sử dụng các practices và tools để tự động hóa các khâu
Bài trình bày của anh Trương Anh Quân tại Meetup của Ha Noi .NET Group.
Chi tiết vui lòng xem tại: http://tungnt.net
Similar to How Dealogic Scaled Agile &; Delivers Effectively (20)
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
2. Dealogic Limited 2017 Page 2
About Dealogic
Founded: 1983 in the United Kingdom
Ownership: The Carlyle Group (majority) and co-investors
CEO: Thomas Fleming
Offices London, New York, Hong Kong, Tokyo, Sydney, Mumbai,
Budapest, Sao Paulo, Beijing
Staff: >800
4. Dealogic Limited 2017 Page 4
How is our software is used?
Find Client:
Analytics
Software
Pitch to
clients:
Ranking
tables
Find
Investors:
Conference
s/w
Research
Investors/Co
mpanies:
Mobile App
Execute Deal:
Transaction
S/w
Track Orders:
Pulse App
Bonus: Based
on DL
rankings
IPO Example
5. Dealogic Limited 2017 Page 5
Delivering once a
quarter to…..
…30 global
teams each
delivering every
two weeks
Well how do we
do it?
11. Dealogic Limited 2017 Page 11
Dev & That Ops Thing
Ops learnt late of change
No Feedback loop
It works on Dev so it will work on Prod ?
Dev teams knew nothing of Ops
Ops knew nothing of Dev
No one was over the software from Dev to Production.
The problem we needed to solve
13. Dealogic Limited 2017 Page 13
Dev & That Ops Thing
Aligned Cadence
Common Tooling
Kanban
Area matter experts
Ops team empowered to say No
Team lead between Dev & Ops
The Delivery aligned Ops team
14. Dealogic Limited 2017 Page 14
Dev & That Ops Thing
The Good Part
Ops Alignment
The Ops Ambassadors
Changed known early
Dev reached out
Happier & more Innovative
Little but often approach
Boring Deployments
The Delivery aligned Ops team
15. Dealogic Limited 2017 Page 15
Dev & That Ops Thing
Something was still missing
Roadblocks
Post Sign-Off Disconnect
Regular Feedback but late
The Delivery aligned Ops team
17. Dealogic Limited 2017 Page 17
Dev & That Ops Thing
An embedded Dev & Ops team was Created
Dev team with added members from Ops
Team followed You Build It, You Run It…
Ops members were empowered to be T shaped & Dev to look at Prod
The Dev with Ops Team
19. Dealogic Limited 2017 Page 19
Dev & That Ops Thing
Diagnostics & Usage Logs
Event Log, Databases, Google Analytics
OMS
Dev
MTM
Visual Studio
Deployments
PowerShell automated Deployment mechanism
MS Orchestrator Runbooks with PowerShell to deploy to production
Infrastructure
System Center Operations Manager
Microsoft Azure
Source control management
TFS
GitHub
Finally the Tooling to Support this
20. Dealogic Limited 2017 Page 20
Deploy Regularly & Safely
No matter how good the code, if no one can see it then it doesn’t exist ?
We deploy to production every 2 weeks
A typical Pipeline at Dealogic
The technology stack
PowerShell based installer framework
MTM to run automated tests
MS Orchestrator to build production stages
This differentiates successful companies from everyone else
Integration Test
Platform
Integration
Staging Production
Perf Test Pen Test
21. Dealogic Limited 2017 Page 21
Deploy Regularly & Safely
Integration Test
Deployed once an hour
Runs all automated installation and mock based integration tests
Health Check tests
Deployment takes 30 minutes
We are breaking this stage up into many smaller ones now
Platform Integration
Deployed twice a day
Used for Manual testing by QA team
Aim to have a staging deployment candidate each day. Full sign off.
Deployment takes 50 minutes
Spotlight on Dev
Integration Test
Platform
Integration
Staging Production
Perf Test Pen Test
22. Dealogic Limited 2017 Page 22
Deploy Regularly & Safely
Deployed Every 2 weeks with QA passed Build
Staging deploy is part of the iteration
Deployment takes 60 minutes
Blue/Green Deployment
Staging & Production a full likeness of each other with all the relevant Infra setup
This is production * 2
Once Staging is signed off we switch Staging & Production
Now staging is Live (Production)
Rollback means switching the other way in the worst case
Downtime is around 30 minutes between switches at the moment.
Spotlight on Staging & Production
Integration Test
Platform
Integration
Staging Production
Perf Test Pen Test
23. Dealogic Limited 2017 Page 23
Deploy Regularly & Safely
Perf Test
This is run every few weeks, usually on request
Indications given of performance on production
Requests made for this when larger changes are made that could impact performance
Microsoft Load Test framework used
Pen Test
This is run every quarter
Experience Pen Tester brought in
Helps understand where any security holes may exist
Spotlight on Perf & Pen Test
Integration Test
Platform
Integration
Staging Production
Perf Test Pen Test
24. Dealogic Limited 2017 Page 24
Deploy Regularly & Safely
We are currently evolving our deployment practices for Rapid Releases.
Micro pipelines around a very small code base.
Code is managed by a single team
Testing is quicker as less to sign off and more targeted
Each package is independent
Others parts can go to production even if one part fails.
Rapid Release Pipelines
25. Dealogic Limited 2017 Page 25
Deploy Regularly & Safely
Deployable
Unit
CI Versioning
Nuget
Dependencies
Regression
tests
Deployment
Pipeline &
Installer Tech
A typical Deployable Unit setup
26. Dealogic Limited 2017 Page 26
Deploy Regularly & Safely
Rapid Release Pipeline
Component 1
Auto Test
Platform Integration Staging Production
Component 2
Auto Test
Platform Integration Staging Production
Component 3
Auto Test
Platform Integration Staging Production
Platform Integration/Staging/Production are shared environments
Each component has vigorous automated regression tests
Sign off now is at component level not product level
Dev – Prod is very rapid, team controls how often they go to prod
Run to prod every day
Run to prod every 3 days
Run to prod every week
28. Dealogic Limited 2017 Page 28
Teams empowered to Deliver
A Good team is one that knows WHAT IT CANNOT DO
Understanding what you can’t deliver is the most important question to ask…
Teams empowered to push back
Components are Open Source
The teams believe in the process we follow
Expert Domain Knowledge in their component.
Little but often philosophy
What the Team Cannot Do
29. Dealogic Limited 2017 Page 29
Teams empowered to Deliver
Our Typical Team Structure
Snr
Developer
Developer Developer QA
Snr QA
Dev
Manager
BA TA Guide, Protect & Drive
Steer Continuous Improvement
Drive Delivery
30. Dealogic Limited 2017 Page 30
Teams empowered to Deliver
Tech Debt
Teams at Dealogic are encouraged to track Tech Debt and manage it.
SonarQube used to track Debt metrics
Effective Leadership
Bi-Weekly grooming meetings are key for each team
Teams motivated to look ahead
Fail Fast
All teams are encouraged to not be afraid of failing
A big philosophy is to try new things and improve our tech/processes continuously
Self Improvement
31. Dealogic Limited 2017 Page 31
Minimizing Collaboration ?
Some Collaboration is cool…
32. Dealogic Limited 2017 Page 32
Minimizing Collaboration ?
Some Collaboration is required…
33. Dealogic Limited 2017 Page 33
Minimizing Collaboration ?
Maximizing the time teams are not blocked makes them Happier & More Productive
The Past
Multiple teams working across same code base
Teams building the same thing twice in different ways
No ownership -> Tech Debt build up
In case of an issue everyone pointed to each other
Code Overwriting became an issue
Matter experts were hard to identify
UX teams was pulled every which way and spread very thin. They were a blocker.
History
34. Dealogic Limited 2017 Page 34
Minimizing Collaboration ?
Some collaboration is still very important
36. Dealogic Limited 2017 Page 36
Minimizing Collaboration ?
We firstly broke down our product
37. Dealogic Limited 2017 Page 37
Minimizing Collaboration ?
Topology we are following now
Deal Alerts
Company List
Market Activity
Graphs
Framework
Deal Lookup
Report Selector
Team 1 Team 3
Team 2
Team 4
38. Dealogic Limited 2017 Page 38
Minimizing Collaboration ?
We Called it Componentization
Each team was given its own specific area
Ownership -> Pride and responsibility -> Expertise -> Innovation
Re-usable & separately deployable widgets
UX member aligned with teams to provide more personal attention
Separate Deployment pipelines & Cadences based on teams comfortability
All teams aligned to a common deliverable or set of deliverables
Giving Agile Teams Ownership of their own destiny
39. Dealogic Limited 2017 Page 39
Minimizing Collaboration ?
We set some basic ground rules
Every team has its own backlog and priority list for their component
A suite of automated regression tests need to be well defined on your component
Nuget is used for any code dependency outside of the team’s codebase
Being done now each team has to have its own pipeline to production for their component
LESS alignment between teams working together
Trust
A few things that make this all work
40. Dealogic Limited 2017 Page 40
Minimizing Collaboration ?
How it all comes together. Rapid Releases
Hey can you make
some style changes
in that company list
Company List
Auto Test
Platform Integration Staging Production
15 Minutes
Make style change
15 Minutes 15 Minutes
Dev Test Deploy
10 Minutes
All the dev/deployment is targeted around the company list and only that.
• Targeted Testing
• Targeted Deployment
Test style change Get to production
Deal Alerts
Company List
Market
Activity
Graphs
Framework
Deal Lookup
Report Selector
42. Dealogic Limited 2017 Page 42
When Introducing Tech Debt is ok ?
Why introduce Debt at all…
Sometimes we want fast feedback on items which requires introducing Debt
Very Fast Feedback
Large Business Opportunity
Strategic
WHEN it will not cause a bug in the system
NOT to squeeze more work in
43. Dealogic Limited 2017 Page 43
When Introducing Tech Debt is ok ?
The art of managing tech debt…
The reason we aren’t afraid of introducing Tech Debt is because we Manage It
Any debt that is introduced is acknowledged as what it is, Debt.
Items are created in the backlog to clean-up this debt with estimates
All Tech Debt is understood by BA and prioritized accordingly before new debt is introduced
Once new Debt is tackled existing Tech Debt prior to this is tackled and items created around that
Tech Debt isn’t always in code, it can be deployment, testing, operations etc..
Introducing Tech Debt shouldn’t feel good or natural but is a last resort to achieve something
44. Dealogic Limited 2017 Page 44
Quality
At Dealogic our Quality goals don’t stop at just confirming functionality
To maintain a great product we look at quality at all angles
Security
Performance
Automation
Installation
Security
Our clients expect us to secure our systems and by extension any data they supply us.
We run automated scans each iteration via a third party
We have a Pen Tester who manually checks security vulnerabilities every quarter
We align our security rules sets with our clients
Going beyond just logic testing…
45. Dealogic Limited 2017 Page 45
Quality
Performance
If no one can use your system because its un-responsive then no one will…
Performance Test team
Visual Studio Load Test
Load tests mimic usage
Server side applications put under stress
Agreed KPI’s maintained
Going beyond just logic testing…
46. Dealogic Limited 2017 Page 46
Quality
Automation
Why do the same thing 1000’s of time when a machine can do it…
UI
Java script tests using Jest & Junit
UX automated tests using Specflow & Selenium
Wiremock used to mock service returns
Back End
Unit Tests written in Visual Studio
SQL Tests written using MS Test
Integration Tests written using MS Test
Going beyond just logic testing…
47. Dealogic Limited 2017 Page 47
Quality
Installation
We like to be confident that we think we have installed we actually have
Automated health check tests pings each installed component
MTM used to run test post deployment
Health Checks are made to be detailed enough to give clear indication to state of
component
Going beyond just logic testing…
48. Dealogic Limited 2017 Page 48
Quality
We work hard to automate our UI tests around regression
These save our QA team a lot of time every time we run a deployment.
Automated smokes tests run every deployment to Platform environment
Automated regression tests run in Auto Test environment
Tests only confirm UX not data consistency
KeyNote used to test product on mobile & tablet platforms
A little about our UX Testing…
49. Dealogic Limited 2017 Page 49
MVP
Give your users what
they want based on
feedback; not what
you think they want
52. Dealogic Limited 2017 Page 52
Teams empowered to Deliver
• Roadmap alignment across teams
• revised each quarter (flexibility to respond to
new opportunities)Yearly
• 3 month forward feature forecast to
manage inter-team dependencies
and review milestones
6
Weekly
• Post planning walkthrough
• Mid-Iteration progress demo
• Next iteration Backlog review
2
Weekly
Scrum and Kanban are great at an individual team level, but what about multiple teams?
54. Dealogic Limited 2017 Page 54
Teams empowered to Deliver
Our teams do so well due in part to the continued support we provide them
Dealogic's Agile Center of Excellence
Each team member is put through Internal agile training to create team alignment
Agile Center helps any teams struggling with any aspect of Agile delivery
Regular Presentations given around agile delivery trends
Built from enthusiasts within company
Talent Management
A group that runs workshops to allow staff to better themselves
Leaderships courses
Company Domain Knowledge courses
Presentation classes
And much more…
Help & Support
Dealogic is a financial markets platform offering integrated content, analytics, and technology via a single solution to top financial firms worldwide.
Global deal execution network; biggest transactions on record in every major financial center
Comprehensive content on debt and equity offerings, loans, and M&A transactions
The industry-standard Dealogic proprietary fee model, now used by more than 40 global banks and the top-ranked analysts covering those banks
Predictive analytics; help clients originate their strategic decision making
Its not your drinking buddy….
Its not the master of everything ….
This is something I used to hear all the time…
The two departments trying to work together.
How it would work if we all played well together and both division were aligned
Late Changes
Just throw it over the fence. Lots of Manual Steps -> Long Upgrades -> Unhappy staff…
Dev not aware of prod
- Why do we have more than one of the same server ?
- Well my software won’t work in that setup
This was when we section out a part of Ops to focus on Cortex
Our first step towards a DevOps culture
Start off with:
Ops team section out from Ops department, put through same training as Dev teams in Agile delivery
Ops supporting Dev
Bi-Weekly alignment on changes required for next release
-Ops team became more aligned with the working of the software
-They were Ambassadors from the Ops division and acted as an important bridge
-Changes were known earlier so production made ready to accommodate
-Dev became more accustomed to reaching out to aligned Ops team
-Ops team ran happier with more understanding of the workings of the larger system.
-Innovations were put into the pipelines into prod to streamline software delivery by Ops team
-Kanban process was working and team started appreciating doing little changes often
-Deployments to prod became stable and like clockwork
Roadblocks
There was no dev experience so team felt blocked in innovating in areas where no dev.
After sign off dev disconnected
Feedback did come from Ops team but it was usually mid way through next iteration a little late to react to things
This is when we brough Ops members into already well functioning Dev team. True DevOps.
How is it going ?
Feedback from prod systems is much better. Team regularly looks at prod logs to catch hidden issues
Ops members have engaged in doing a little Dev where they want to learn more
Dev members are thinking of software setup on prod when planning requirements
Retrospectives include feedback from upgrades , support and dev.
Planning includes thoughts and tasks from Dev to Prod.
Upgrade Automation is the current priority
Team is looking to align Dev Pipeline with production to catch upgrade issues earlier
A real team motivation exists from both sides where they are delivering business value through Ops & Dev work
Pipeline at Dealogic
7-10 teams deploy in a single pipeline
A single Trunk Branch represents the pipeline
Pipeline is at a product level
Rapid Releases
Current process is now a little slow for us, we want to go faster
With so many moving parts and teams involved its easy for a small failure to stop a release
Spend 5 minutes here at most
Empower to push Back
The output will not match our quality goals in the time given
The incoming work is wildly changing daily
The features are not understood well and your blocked before you begin
Team work in other teams domains
We encourage an open source model where possible
Tech Debt
When debt introduced it is acknowledged and Backlog items created to fix it
Debt reduction is celebrated through KPI’s that are visible company wide
We do not aim for 0% tech debt, but it would be great to be there…
Effective Leadership
Bi Weekly meetings - DM, TA, BA & Snr QA align on teams upcoming priorities
Fail Fast
If you never fail maybe your not being challenged enough ?
Try and Fail Fast is our motto so you learn and move on quickly to what works
This works so its not all bad
This is a family affair
Working against each other is also not good
This is when everyone is doing a little too much collaboration
This is something similar to what Spotify do
Teams now could go at pace comfortable to them
Start with:
Each teams interfaces are well defined and versioned
LESS is large scale scrum
-Teams sometimes want client feedback on an item quickly and all dependencies are not in place
- fail fast
-There is a large business opportunity if missed could be a disaster. Be careful with this one!
-Strategic
- The correct way Debt free is much longer and we rather tackle that slowly across several iterations
-Debt is only every introduced when it will not cause a bug in the system
-Only Ok when its not to squeeze more work on to an already under pressure team.
We manage debt:
This ultimately means all teams make a commitment to clean-up the new debt in the near future
Tackling exiting debt:
This is continuous improvement
MVP = Minimum Viable Product
Focus on the viable; what would your customers accept as usable and useful functionality?
It is not the minimum we can get away and still charge the suckers for!
The MVP is not the final product; it’s the first iteration of a ever evolving process.
Ensure you monetize but perhaps charge a different price for early adopters
Crossing the chasm is the biggest challenge between MVP and the fully chargeable model.
Before?
Tech focussed meetings; dev driven
Business users loose interest and stop attending
Now
Use Case/Client focussed videos
Targeted, searchable, accessible any time
Living “documentation” of our functionality
Understandable and relevant to the client facing teams
How we got to these?
Replaced vague statements with calls to action
Established via a bottom up approach
Well marketed and instilled into every day work
Value ambassadors
Why it matters?
Shapes our culture
Influence overall behaviour and provide
Help differentiate against our competitors
Plenty of Collaborative space -> essential in Agile
Space to host meetups like this one!
Higher morale -> more productive
Shows visitors the kind of company we are -> differentiate from competitors and in house dev
Enforces the Dealogic Brand and attracts people to want to work with and for us
Highly active
Promotes cross team and regional collaboration
Spread messages to a wider audience than emails
Pull over Push model
Permanence of messages with basic knowledge base created
Range of badges awarded by Execs/Managers/peer; great way to show appreciation
Points means prizes….days off, team lunches etc.