1. Agile engineering practices like continuous integration, test-driven development, refactoring, and pair programming can help software teams build higher quality code more efficiently.
2. Continuous integration involves developers integrating code changes frequently through automated builds and tests to quickly detect errors.
3. Test-driven development uses short development cycles where developers write automated tests before code and refactor code to maintain test coverage.
The document discusses technical debt in software development. It defines technical debt as deferred work that accumulates when high quality standards are not enforced or corners are cut to achieve velocity targets. This debt makes code complex and hard to change, reducing a team's ability to meet business needs. The document recommends practices like continuous integration, test-driven development, and refactoring to avoid debt. It also discusses strategies for identifying and paying off existing debt over time.
This document provides information about an advanced Agile Scrum online workshop taking place on February 27, 2021. It includes an introduction section for participants to provide their name, education, work experience and location. The bulk of the document outlines the workshop contents, covering topics like Agile fundamentals, the Agile investment model, the Agile manifesto, what Scrum is, Scrum values, the Scrum flow, Scrum events, and more. Tables of contents and headings are included to help navigate through the different sections.
Why Scale? When choose each scaling approach? SAFe? LeSS? Enterprise Kanban? Other? Scaling experts will compare the different approaches, share from their experience and answer questions from the audience.
This is the LeSS section presented by Sagi Smolarski
The document is the Scrum Guide, which provides the definition and framework of Scrum. It describes Scrum as an agile framework for managing complex work, with roles of Product Owner, Development Team and Scrum Master. It outlines Scrum events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective. It also describes Scrum artifacts like the Product Backlog, Sprint Backlog and Increment. The guide was created by Ken Schwaber and Jeff Sutherland, who developed the Scrum framework.
Deconstructing the scaled agile frameworkAngela Dugan
Delivered at the QAI Quest conference as a 90 minute workshop - With so many software delivery process frameworks and methodologies out there, it’s hard to know where to begin. And just when the industry seems to be warming up to agile, here comes SCALED agile with frameworks like SAFe, LESS, and a host of others. Should we all just be SAFe? But then maybe SAFe is just a glorified waterfall process for companies that “can’t handle real Agile”. SAFe, the Scaled Agile Framework, leverages the best of several well-established frameworks, including Lean, Kanban, and scrum. While SAFe is certainly intended for large, enterprise organizations delivering extremely complex and interdependent systems, many SAFe principles and practices can be used to improve much smaller teams. Join Angela in this workshop to gain a better understanding of the SAFe, and how teams can adopt SAFe principles and practices to improve the development, testing, and delivery of products.
The document outlines the 6 core roles in Scrum: ScrumMaster, Product Owner, Team, Customer, Manager, and End User. It describes each role and how they work together. The ScrumMaster protects the team and removes impediments. The Product Owner defines the product vision and backlog. The Team delivers working software each sprint. The Customer requests the product and provides feedback. The Manager establishes organizational structure. The End User provides requirements and feedback.
Large-Scale Scrum (LeSS) is scaling framework created by Craig Larman and Bas Vodde. I Presented a case study on LeSS to PlayScrum-Pune user group on 7th Nov.
1. Agile engineering practices like continuous integration, test-driven development, refactoring, and pair programming can help software teams build higher quality code more efficiently.
2. Continuous integration involves developers integrating code changes frequently through automated builds and tests to quickly detect errors.
3. Test-driven development uses short development cycles where developers write automated tests before code and refactor code to maintain test coverage.
The document discusses technical debt in software development. It defines technical debt as deferred work that accumulates when high quality standards are not enforced or corners are cut to achieve velocity targets. This debt makes code complex and hard to change, reducing a team's ability to meet business needs. The document recommends practices like continuous integration, test-driven development, and refactoring to avoid debt. It also discusses strategies for identifying and paying off existing debt over time.
This document provides information about an advanced Agile Scrum online workshop taking place on February 27, 2021. It includes an introduction section for participants to provide their name, education, work experience and location. The bulk of the document outlines the workshop contents, covering topics like Agile fundamentals, the Agile investment model, the Agile manifesto, what Scrum is, Scrum values, the Scrum flow, Scrum events, and more. Tables of contents and headings are included to help navigate through the different sections.
Why Scale? When choose each scaling approach? SAFe? LeSS? Enterprise Kanban? Other? Scaling experts will compare the different approaches, share from their experience and answer questions from the audience.
This is the LeSS section presented by Sagi Smolarski
The document is the Scrum Guide, which provides the definition and framework of Scrum. It describes Scrum as an agile framework for managing complex work, with roles of Product Owner, Development Team and Scrum Master. It outlines Scrum events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective. It also describes Scrum artifacts like the Product Backlog, Sprint Backlog and Increment. The guide was created by Ken Schwaber and Jeff Sutherland, who developed the Scrum framework.
Deconstructing the scaled agile frameworkAngela Dugan
Delivered at the QAI Quest conference as a 90 minute workshop - With so many software delivery process frameworks and methodologies out there, it’s hard to know where to begin. And just when the industry seems to be warming up to agile, here comes SCALED agile with frameworks like SAFe, LESS, and a host of others. Should we all just be SAFe? But then maybe SAFe is just a glorified waterfall process for companies that “can’t handle real Agile”. SAFe, the Scaled Agile Framework, leverages the best of several well-established frameworks, including Lean, Kanban, and scrum. While SAFe is certainly intended for large, enterprise organizations delivering extremely complex and interdependent systems, many SAFe principles and practices can be used to improve much smaller teams. Join Angela in this workshop to gain a better understanding of the SAFe, and how teams can adopt SAFe principles and practices to improve the development, testing, and delivery of products.
The document outlines the 6 core roles in Scrum: ScrumMaster, Product Owner, Team, Customer, Manager, and End User. It describes each role and how they work together. The ScrumMaster protects the team and removes impediments. The Product Owner defines the product vision and backlog. The Team delivers working software each sprint. The Customer requests the product and provides feedback. The Manager establishes organizational structure. The End User provides requirements and feedback.
Large-Scale Scrum (LeSS) is scaling framework created by Craig Larman and Bas Vodde. I Presented a case study on LeSS to PlayScrum-Pune user group on 7th Nov.
A very short presentation of SCRUM. It contains the most important concepts for a first introduction to SCRUM, and allows to specify the right vocabulary.
Agile Fundamentals and Best Practices (with Trello)Filippo Zanella
This document provides an overview of agile fundamentals and best practices. It outlines key concepts of Scrum like the product owner, development team, and sprint process. It also describes agile practices such as sprint planning, getting user feedback, testing, and using Trello for project management. The document is intended to recap agile concepts for the author's team.
2020 scrum-guide | The Definitive Guide to Scrum: The Rules of the GameLeanwisdom
This document provides an overview of the Scrum framework for project management. It defines Scrum and its core components: roles (Product Owner, Development Team, Scrum Master), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment). It describes how Scrum uses an empirical, iterative process based on transparency, inspection, and adaptation to manage complex work. The document serves as a guide for using Scrum and was developed by its creators, Ken Schwaber and Jeff Sutherland.
Scrum guide presentation (Scrum Guide in easy to read PPT format)Aloke Bhattacharya
This document provides a summary of the Scrum Guide in PowerPoint format. It was created by Aloke Bhattacharya based on the November 2017 version of the Scrum Guide. The presentation aims to make the key points of the Scrum Guide more memorable through additional diagrams, highlighting, and splitting long paragraphs. It includes all content from the Scrum Guide unchanged and in the same order, with page numbers provided for reference.
Scrum Day London 2016 - Empirical Management Explored (by Gunther Verheyen)Gunther Verheyen
More than 15 years ago, the Manifesto for Agile Software Development was created—the “Magna Carta” for agile development. And while this was a powerful document for development work, managers felt left out. To this day, some claim there is no place for managers in Agile. But the act of managing is not obsolete by any stretch in software development—it merely needs some refinement and an update in focus.
A core objective of the agile movement was to shift the focus of software development to creating more valuable software, frequently. It can be expected that the act of managing in an agile environment is different than traditional project or employee management: at its center, it must maximize the value that the software brings. Enter a new management culture, Empirical Management, thriving on evidence-based decision-making. Managers in product-development organizations are making the shift from predictive management, where plans and predictions prevail, to empirical management, where evidence and experience is used for better decision-making.
There is value in applying the Scrum stance in the managerial domain. Informed management decisions can be made if it is made transparent whether the software created is indeed valuable; valuable to the organization, its users and the wider ecosystem. Indicators of value become the primary source for inspection, in order to adapt how the software is being produced.
In the opening keynote of the first edition of the Scrum Day London event, Gunther Verheyen explored the idea of Empirical Management and the updated act of managing in today’s agile software development.
Remote Agility and Distributed Agile Team StructureKaty Slemon
Agile teams are self-managing & work best when your team works remotely. Discover the functioning of a remote agile teams as COVID forced strict rules on social distancing.
Building Cross-Functional Scrum-Teams in a Hardware ProjectStephanie Gasche
Presentation on Building Cross-Functional Scrum-Teams in a Hardware Project. Variations of this presentation were held at the conferences Global Scrum Gathering Berlin 2014 and Agile Bodensee 2014.
Scrum is a popular agile framework that helps development teams deliver value in small increments, typically 30 days or less, through short sprints. It provides a flexible framework for self-organizing teams to focus on delivering working software frequently. Key roles in Scrum include the product owner who prioritizes backlog items, the Scrum master who facilitates the process, and cross-functional teams of 7 plus or minus 2 members who are responsible for delivering working increments of software.
The document discusses the principles of Taylorism and how they are outdated for modern business needs. It argues that only by utilizing the intelligence of all employees, not just executives, can a company survive increasingly complex business environments. Konosuke Matsushita asserts that Japanese companies have moved beyond the Taylor model and will be more successful than Western companies still adhering to outdated Taylorist principles that separate thinking from doing work.
Scrum, Kanban and DevOps Sitting in a tree... Dave West and Yuval Yeret at Ag...Yuval Yeret
Should you use Scrum, Kanban, or DevOps? You don’t have to choose: Scrum teams improve when they look at flows inside and outside their sprints from a Lean/Kanban perspective. In this session we will talk about Kanban-related myths prevalent in the Scrum world and identify common ground between them. We will look at ways to bring Kanban flow into your Scrum: the Kanban-based Sprint/product backlog, flow-based daily Scrum, visualizing aging work, and flow-based Sprint planning .We will describe ways to wrap Scrum with a Kanban flow system, and at the higher-level picture of a DevOps culture and process.
You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with ideas for experiments to try when back at work.
Lost in Translation: The Product Manager in Agile Organizations (Ramon Guiu P...IT Arena
Lviv IT Arena is a conference specially designed for programmers, designers, developers, top managers, inverstors, entrepreneur and startuppers. Annually it takes place on 2-4 of October in Lviv at the Arena Lviv stadium. In 2015 conference gathered more than 1400 participants and over 100 speakers from companies like Facebook. FitBit, Mail.ru, HP, Epson and IBM. More details about conference at itarene.lviv.ua.
This document provides an overview of getting started with Scrum and examples of Scrum adoption. It discusses Silvana Wasitova's background working with Scrum. It then summarizes Yahoo's adoption of Scrum between 2004-2008, including increasing from one team to over 200 teams. Next, it summarizes a German IT company's Scrum adoption between 2010-2012, growing from one project to over 40 projects using Scrum. It then provides tips for successful Scrum adoption.
The document summarizes the author's experience with adopting Agile practices within her team. Initially, the team struggled with a partially ad-hoc Agile implementation that resulted in slow, poor quality work and budget overruns. Over time, as the team recomposed their practices to more closely align with Agile principles such as short stand-up meetings, estimating in story points, and continuous flow, they saw improvements in quality, time to market, and flexibility. Business stakeholders also reported benefits like increased visibility into work being done and opportunities to provide feedback. The author concludes by reflecting on further refinements to Agile practices in her current role, supported by a dedicated Agile center of excellence, external coaching, and executive sponsorship.
LeSS: why broader Product Definition, who is the Real PO and what we are scal...Artem Bykovets
Slides from talk: "LeSS: why broader Product Definition, who is the Real PO and what we are scaling?" from Online Project Management Day Ukraine conference (29/01/2022) by Artem Bykovets
In this talk:
The difference between Multiple Scrum Teams and Multi-Team Scrum
What is Product and what is not? Why LeSS recommends to use broader product definition
Why Feature Teams and what about specialization? What about dependencies?
Who is the Real Product Owner and (s)he should do?
And some stories, metaphors and jokes as usual :)
Scrum Day Europe 2014 - Evidence-Based Managing of SoftwareGunther Verheyen
During the past decade, the adoption of agile has grown incredibly. But the dependence of businesses and society on software has increased even more. Software is eating the world.
The survival and prosperity of many people and organizations depend on software. Complexity and unpredictability continue to increase. Yet, many organizations are stuck with old thinking like productivity, performance and blindly pushing more requirements out to the market.
The focus of managing has not shifted to, like was a core intent of the agile movement, optimizing the VALUE that the software brings to the organization. The urgency to do so grows.
The agile values and spirit are more needed than ever, but it's time to include management in the empirical thinking.
Gunther Verheyen directs the Professional Series at Scrum.org and is a partner of Ken Schwaber, Scrum co-creator. Gunther and Ken have developed a view on management in an agile context, "Evidence-Based Management" (EBM).
EBM has its roots in medical practice and promotes evidence-based decision-making in the managerial domain of software.
In his keynote presentation at Scrum Day Europe 2014, Gunther looked at the state of agile through the lens of EBM, and introduce how to apply its principles in a context of software.
If no evidence is collected on the value of software, informed management decisions to maximize it cannot be made. Software development deserves a professional way of managing, a way of managing that is more than mere intuition, opinion and position.
Scrum & Kanban - Better Together? Talk delivered at Agile Boston w/ Dave West of Scrum.org in October 2018
It's time to call an end to this stupid civil war within the agile camp. The best agile teams already know that it is not a choice between Scrum and Kanban, but they are complementary. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership.
In this session, we will look at:
Common Ground - The foundations that both approaches highlight
Complementary Practices - what can we add from Kanban to our Scrum and vice versa
Key differences - where you really need to make a choice
Myths - differences that are talked about which really are not there
YouTube Link: https://youtu.be/X95kqqaI9Fg
** Certified Scrum Master Training: https://www.edureka.co/certified-scrum-master-certification-training **
This Edureka PPT on "Scrum Master Roles and Responsibilities" will help you understand who scrum master exactly is and what role does he play in scrum product development.
Introduction to Scrum
Who is a Scrum Master?
Role of a Scrum Master
Responsibilities of a Scrum Master
Qualities of a Good Scrum Master
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
DevOps/Flow workshop for agile india 2015Yuval Yeret
This document discusses implementing DevOps flow by leveraging lean/agile practices across development, deployment, and operations. It emphasizes establishing continuous integration and delivery workflows to enable frequent, reliable releases through automation. Kanban techniques are presented as a way to visualize work and limit work-in-progress to improve collaboration between teams.
Learn how we saved 76% to 81% of our event costs by using virtual worlds, and how they can be used to do agile project management with distributed teams. Presented at the Agile2010 conference in Orlando.
Agile is often traditionally associated as being exclusively applicable to the field of software development. However, non-software development projects can take ownership and use agile values, principles and practices to great effect. In this session, I will offer some approaches, techniques and examples for introducing agile into parts of the organisation that traditionally may not have considered it such as central services like finance, HR, marketing, traditional business areas as well as other areas of IT like infrastructure and provide some real-life examples along the way.
A very short presentation of SCRUM. It contains the most important concepts for a first introduction to SCRUM, and allows to specify the right vocabulary.
Agile Fundamentals and Best Practices (with Trello)Filippo Zanella
This document provides an overview of agile fundamentals and best practices. It outlines key concepts of Scrum like the product owner, development team, and sprint process. It also describes agile practices such as sprint planning, getting user feedback, testing, and using Trello for project management. The document is intended to recap agile concepts for the author's team.
2020 scrum-guide | The Definitive Guide to Scrum: The Rules of the GameLeanwisdom
This document provides an overview of the Scrum framework for project management. It defines Scrum and its core components: roles (Product Owner, Development Team, Scrum Master), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment). It describes how Scrum uses an empirical, iterative process based on transparency, inspection, and adaptation to manage complex work. The document serves as a guide for using Scrum and was developed by its creators, Ken Schwaber and Jeff Sutherland.
Scrum guide presentation (Scrum Guide in easy to read PPT format)Aloke Bhattacharya
This document provides a summary of the Scrum Guide in PowerPoint format. It was created by Aloke Bhattacharya based on the November 2017 version of the Scrum Guide. The presentation aims to make the key points of the Scrum Guide more memorable through additional diagrams, highlighting, and splitting long paragraphs. It includes all content from the Scrum Guide unchanged and in the same order, with page numbers provided for reference.
Scrum Day London 2016 - Empirical Management Explored (by Gunther Verheyen)Gunther Verheyen
More than 15 years ago, the Manifesto for Agile Software Development was created—the “Magna Carta” for agile development. And while this was a powerful document for development work, managers felt left out. To this day, some claim there is no place for managers in Agile. But the act of managing is not obsolete by any stretch in software development—it merely needs some refinement and an update in focus.
A core objective of the agile movement was to shift the focus of software development to creating more valuable software, frequently. It can be expected that the act of managing in an agile environment is different than traditional project or employee management: at its center, it must maximize the value that the software brings. Enter a new management culture, Empirical Management, thriving on evidence-based decision-making. Managers in product-development organizations are making the shift from predictive management, where plans and predictions prevail, to empirical management, where evidence and experience is used for better decision-making.
There is value in applying the Scrum stance in the managerial domain. Informed management decisions can be made if it is made transparent whether the software created is indeed valuable; valuable to the organization, its users and the wider ecosystem. Indicators of value become the primary source for inspection, in order to adapt how the software is being produced.
In the opening keynote of the first edition of the Scrum Day London event, Gunther Verheyen explored the idea of Empirical Management and the updated act of managing in today’s agile software development.
Remote Agility and Distributed Agile Team StructureKaty Slemon
Agile teams are self-managing & work best when your team works remotely. Discover the functioning of a remote agile teams as COVID forced strict rules on social distancing.
Building Cross-Functional Scrum-Teams in a Hardware ProjectStephanie Gasche
Presentation on Building Cross-Functional Scrum-Teams in a Hardware Project. Variations of this presentation were held at the conferences Global Scrum Gathering Berlin 2014 and Agile Bodensee 2014.
Scrum is a popular agile framework that helps development teams deliver value in small increments, typically 30 days or less, through short sprints. It provides a flexible framework for self-organizing teams to focus on delivering working software frequently. Key roles in Scrum include the product owner who prioritizes backlog items, the Scrum master who facilitates the process, and cross-functional teams of 7 plus or minus 2 members who are responsible for delivering working increments of software.
The document discusses the principles of Taylorism and how they are outdated for modern business needs. It argues that only by utilizing the intelligence of all employees, not just executives, can a company survive increasingly complex business environments. Konosuke Matsushita asserts that Japanese companies have moved beyond the Taylor model and will be more successful than Western companies still adhering to outdated Taylorist principles that separate thinking from doing work.
Scrum, Kanban and DevOps Sitting in a tree... Dave West and Yuval Yeret at Ag...Yuval Yeret
Should you use Scrum, Kanban, or DevOps? You don’t have to choose: Scrum teams improve when they look at flows inside and outside their sprints from a Lean/Kanban perspective. In this session we will talk about Kanban-related myths prevalent in the Scrum world and identify common ground between them. We will look at ways to bring Kanban flow into your Scrum: the Kanban-based Sprint/product backlog, flow-based daily Scrum, visualizing aging work, and flow-based Sprint planning .We will describe ways to wrap Scrum with a Kanban flow system, and at the higher-level picture of a DevOps culture and process.
You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with ideas for experiments to try when back at work.
Lost in Translation: The Product Manager in Agile Organizations (Ramon Guiu P...IT Arena
Lviv IT Arena is a conference specially designed for programmers, designers, developers, top managers, inverstors, entrepreneur and startuppers. Annually it takes place on 2-4 of October in Lviv at the Arena Lviv stadium. In 2015 conference gathered more than 1400 participants and over 100 speakers from companies like Facebook. FitBit, Mail.ru, HP, Epson and IBM. More details about conference at itarene.lviv.ua.
This document provides an overview of getting started with Scrum and examples of Scrum adoption. It discusses Silvana Wasitova's background working with Scrum. It then summarizes Yahoo's adoption of Scrum between 2004-2008, including increasing from one team to over 200 teams. Next, it summarizes a German IT company's Scrum adoption between 2010-2012, growing from one project to over 40 projects using Scrum. It then provides tips for successful Scrum adoption.
The document summarizes the author's experience with adopting Agile practices within her team. Initially, the team struggled with a partially ad-hoc Agile implementation that resulted in slow, poor quality work and budget overruns. Over time, as the team recomposed their practices to more closely align with Agile principles such as short stand-up meetings, estimating in story points, and continuous flow, they saw improvements in quality, time to market, and flexibility. Business stakeholders also reported benefits like increased visibility into work being done and opportunities to provide feedback. The author concludes by reflecting on further refinements to Agile practices in her current role, supported by a dedicated Agile center of excellence, external coaching, and executive sponsorship.
LeSS: why broader Product Definition, who is the Real PO and what we are scal...Artem Bykovets
Slides from talk: "LeSS: why broader Product Definition, who is the Real PO and what we are scaling?" from Online Project Management Day Ukraine conference (29/01/2022) by Artem Bykovets
In this talk:
The difference between Multiple Scrum Teams and Multi-Team Scrum
What is Product and what is not? Why LeSS recommends to use broader product definition
Why Feature Teams and what about specialization? What about dependencies?
Who is the Real Product Owner and (s)he should do?
And some stories, metaphors and jokes as usual :)
Scrum Day Europe 2014 - Evidence-Based Managing of SoftwareGunther Verheyen
During the past decade, the adoption of agile has grown incredibly. But the dependence of businesses and society on software has increased even more. Software is eating the world.
The survival and prosperity of many people and organizations depend on software. Complexity and unpredictability continue to increase. Yet, many organizations are stuck with old thinking like productivity, performance and blindly pushing more requirements out to the market.
The focus of managing has not shifted to, like was a core intent of the agile movement, optimizing the VALUE that the software brings to the organization. The urgency to do so grows.
The agile values and spirit are more needed than ever, but it's time to include management in the empirical thinking.
Gunther Verheyen directs the Professional Series at Scrum.org and is a partner of Ken Schwaber, Scrum co-creator. Gunther and Ken have developed a view on management in an agile context, "Evidence-Based Management" (EBM).
EBM has its roots in medical practice and promotes evidence-based decision-making in the managerial domain of software.
In his keynote presentation at Scrum Day Europe 2014, Gunther looked at the state of agile through the lens of EBM, and introduce how to apply its principles in a context of software.
If no evidence is collected on the value of software, informed management decisions to maximize it cannot be made. Software development deserves a professional way of managing, a way of managing that is more than mere intuition, opinion and position.
Scrum & Kanban - Better Together? Talk delivered at Agile Boston w/ Dave West of Scrum.org in October 2018
It's time to call an end to this stupid civil war within the agile camp. The best agile teams already know that it is not a choice between Scrum and Kanban, but they are complementary. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership.
In this session, we will look at:
Common Ground - The foundations that both approaches highlight
Complementary Practices - what can we add from Kanban to our Scrum and vice versa
Key differences - where you really need to make a choice
Myths - differences that are talked about which really are not there
YouTube Link: https://youtu.be/X95kqqaI9Fg
** Certified Scrum Master Training: https://www.edureka.co/certified-scrum-master-certification-training **
This Edureka PPT on "Scrum Master Roles and Responsibilities" will help you understand who scrum master exactly is and what role does he play in scrum product development.
Introduction to Scrum
Who is a Scrum Master?
Role of a Scrum Master
Responsibilities of a Scrum Master
Qualities of a Good Scrum Master
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
DevOps/Flow workshop for agile india 2015Yuval Yeret
This document discusses implementing DevOps flow by leveraging lean/agile practices across development, deployment, and operations. It emphasizes establishing continuous integration and delivery workflows to enable frequent, reliable releases through automation. Kanban techniques are presented as a way to visualize work and limit work-in-progress to improve collaboration between teams.
Learn how we saved 76% to 81% of our event costs by using virtual worlds, and how they can be used to do agile project management with distributed teams. Presented at the Agile2010 conference in Orlando.
Agile is often traditionally associated as being exclusively applicable to the field of software development. However, non-software development projects can take ownership and use agile values, principles and practices to great effect. In this session, I will offer some approaches, techniques and examples for introducing agile into parts of the organisation that traditionally may not have considered it such as central services like finance, HR, marketing, traditional business areas as well as other areas of IT like infrastructure and provide some real-life examples along the way.
Seeing Constraints, Kanban Explained by Jon StahlLeanDog
I am passionate about kanban because without a lot of ceremony and time, I can get a team to self organize and communicating at a whole new level. Since constraints become visible, it allows people to be more willing to go out of their comfort zone and thus wear any hat that it takes to produce quality software. Seeing constraints, pulling value and eliminating waste is the goal of practicing kanban. This would be a "kanban explained" session for those who are not familiar with this practice. I use physical boards to illustrate the concepts and encourage good dialogue. We will discuss several types of kanban boards such as WIP, backlog and retrospectives.
This presentation has been tested at many user group meetings, at clients and conferences such as Agile 2009 & CodeMash 2010. The session takes 1 hour to present, 1 1/2 hours to have good dialogue during the presentation.
Kanban, while not a new concept, nor complex - it is often misunderstood by those who don't practice it. Intended audience is for people that understand agile story wall concepts and whole team. The best audience is a Scrum master who will learn how kanban can take their craft to the next level of a self organizing teams by seeing, not hearing about constraints.
In order to foster trust and credibility between a project team and its stakeholders, the team has the responsibility to clearly communicate the health of the project. As the leaders of a project, we can apply the metaphor of medical care and their use of "vital signs" to help form a holistic view of the state of the project. Come learn the five "Project Vital Signs", their associated quantitative metrics and how to enable a team to effectively use them as a tool to diagnose and treat project health problems.
How to own a really big complex product v3Mike Cottmeyer
The document discusses how to effectively manage the role of a product owner for large, complex products developed by multiple teams. It describes how the product owner role expands beyond a single person to encompass business analysis, engineering, and leadership capabilities across teams, projects, and the overall product portfolio. Different expressions of product ownership are explored, including scrum of scrums, product owner teams, integration teams, and lean/kanban approaches.
This document discusses techniques for software project estimation. It recommends providing estimates as ranges rather than specific numbers, and always clarifying what an estimate will be used for. It emphasizes aggregating independent estimates, using past project data to calibrate estimates, and not negotiating estimates or commitments. Key techniques include decomposing work into independently estimable units, using the "law of large numbers" for accuracy, and re-estimating regularly based on actual project velocity. Overall, the document provides guidance for creating estimates that are useful without being overly precise commitments.
Three games were presented to help Agile teams understand Agile principles and values: The Failure Bow, Go, and The Marshmallow Challenge. The Failure Bow involves teams of 10 people passing a ball around and allowing members to take each other's places. Go involves indicating someone you want to replace and waiting for "Go!" to take their space. The Marshmallow Challenge tasks building the tallest freestanding structure with a marshmallow on top within 18 minutes using materials like spaghetti, string or tape.
The document discusses how agile testing needs to change to keep up with agile development practices. It emphasizes involving testers early in projects and automating testing. It also stresses that quality must become everyone's responsibility and that the organization needs change through training, new roles and processes, tools, and communication to fully adopt agile. The presentation ends by taking questions from the audience.
Building an A-Team - I Love It When a Team Comes TogetherCraig Smith
Craig Smith presentation from Agile Australia 2010. High performing teams are something that all organisations aspire to, but how exactly do you turn a team from good to great? There is much discussion in the community about management versus leadership, working in a factory versus embracing a tribe and how to motivate a new generation of employees. In this presentation we will look at these topics and determine what makes a high performing team, how Agile techniques can help, what tools and techniques you can use to create this environment and how you can measure performance.
Why Scrum? Scrum is conceptually a very, very simple process framework. What is it about Scrum that is generating some much buzz in the software development community? Why are companies, both big and small, abandoning traditional approaches such as Water Fall and RUP, in favour of Scrum?
Scrum and Agile Engineering Practices - What every ScrumMaster needs to know
Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process.
This presentation was given at the Agile Australia 2011 (http://www.agileaustralia.com/)
Startup businesses face significant risk in the search for a sustainable, profitable and scalable business model. Consequently, the success rate for Startups is low, making them a typically high risk investment. Agile methods offer a way of reducing the risk for both the technical implementation and the development of customers. This is achieved by increasing the ability for a Startup to adapt to change and to incorporate the lessons learned from early customer engagement. In this presentation the nature of technology Startups is examined and the application of Agile principles, practices and tools discussed.
Modernize Development with Agile Engineering PracticesCollabNet
This document discusses modernizing development with agile engineering practices. It introduces Kevin Hancock, a senior director at CollabNet with over 15 years of experience helping large organizations transform into agile teams. The presentation covers establishing upstream practices like Scrum and downstream practices like continuous integration (CI) and continuous delivery (CD). It emphasizes establishing the right people, processes, and tools to connect teams and provide visibility and governance across the development lifecycle.
This document introduces Scrum and provides guidance on introducing Agile and Scrum to an organization. It defines Scrum roles and meetings. It notes that adopting Scrum requires systemic change that is difficult but can make an organization more productive and innovative. It recommends adopting Scrum both top-down with executive support and bottom-up driven by teams, starting small with at-risk projects to minimize risk while gaining support.
A short history of Agile software developmentKane Mar
My 'Short History of Agile Software Development' presentation at the Innovation Campus, University of Wollongong.
I only had 20 minutes to speak, so I did an overview of the origins of 'Software Engineering' ('68 NATO conference) through to some new and different approaches to software. Along the way I talked about the 'New New Product Development Game', Scrum, Extreme Programming, the Agile Manifesto and some thoughts about what the future holds.
Kaizen With GreenHopper: Visualising Agile & Kanban StorywallsCraig Smith
Best practices and lessons learned from a real-world software development team. Suncorp adopted a Kanban-based lean software development approach using JIRA, Greenhopper and other Atlassian tools.
Key Takeaways:
* Overview of agile software techniques
* How Kanban can be applied to software development, maintenance and support
* How to ensure kaizen (improvement) is part of your dev process.
Making decision in the presence of uncertainty requires estimating the impact of the outcome of those decisions. Here;s a collection of resources can can be used to guide that process
Starting with an EIA–748–C compliant Earned Value Management System, integrating an Agile Software Development Lifecycle (Agile) is straightforward when there is a Bright Line between the Performance Measurement Baseline (PMB) and the Sprints and Tasks of the Agile Software Development Process.
The document discusses different levels of project complexity and their alignment with agile project management approaches. It uses the analogy of piloting different types of aircraft to represent different levels of projects, from simple solo projects to highly complex projects critical to national security. The levels progress from having full autonomy to operating within strict rules and oversight, where mistakes are not tolerated due to high stakes and consequences. Agile approaches are best suited for self-contained teams with flexibility and autonomy, while larger, more complex projects require more formal processes and governance.
Changing business of testing - Testing Assembly Helsinki 2014Vasco Duarte
Testing jobs will move to cheaper countries unless the role of testing changes. This is a trend that is happening already, we see large teams of testers being moved to other countries, simply because it is cheaper to do bad testing there!
Testing is a critical part of the product and software development process, and if we don't change its role it will slowly become obsolete. The fact is, that the traditional view of testing endangers testing jobs: now here, and later also in cheaper countries.
I propose a different view of testing. I propose that testing is about enabling business results, not just technical quality. I propose that the tester's job goes far beyond finding issues to track, but also finding users to acquire, finding methods to succeed in the software business. Testing in my view is about making businesses succeed, not about avoid failures in software.
In this presentation I'll describe how a very simple change can profoundly transform the role of testing in a way that it directly enables and supports our businesses! Testing is about making our businesses succeed!
The road ahead is not easy, and not every tester is ready to embrace this view of testing. But the road ahead is inevitable. And we have to start on that journey now!
Jile | 10 road signs to watch out in an agile journeyJile
Buckled up and all set to kick-start your Agile transformation journey? Watch out for these Agile road signs to ensure a safe journey.
To know more, visit : https://www.jile.io/articles-agile-devops/ten-road-signs-in-agile-journey
To know more about Jile visit :www.jile.io
Innovation can be learned – with the most effective creativity methodology out there: SIT.
'Ideen finden' kann man lernen - Systematic Inventive Thinking
For more information and case studies, please visit: www.bold.group
Agile venture vimercate 2019 -
DevOps, Agile, eXtreme Programming, LeanUX, Site Reliability Engineer, DevSecOps... what a mess! Would it be because I love them? this would be a typical joke in Italy regarding an old famous lyric from the band 'Ricchi e Poveri'.
After more than 16 years of journey in this fantastic world, I feel on my the duty to share my experience with the Italian community and beyond to clarify some misbelieves.
I'll explain what I implemented in IBM CIO to embrace Rugged DevOps + DesignOps/LeanUX on our most advanced development teams.
Michele Brissoni
Java deployments in an enterprise environment whitepaper - xebialabsXebiaLabs
This whitepaper discusses the importance of proper deployment processes for Java applications in enterprise environments. It outlines eight common pitfalls that can undermine reliable deployment processes, such as infrastructure designs that do not consider deployment, development environments that differ from production, and the belief that full automation is not possible. To overcome these pitfalls, the whitepaper recommends adopting deployment automation solutions that provide comprehensive middleware support, best practice deployment scenarios, extensibility, scalability, cross-platform support, security, open APIs, and reporting capabilities. The whitepaper uses Air France KLM as a case study to show how deployment challenges can impact businesses. It then describes Deployit, a deployment automation product from XebiaLabs, as an example
WEBINAR: To Automate or Not to AutomateRainforest QA
In this webinar, To Automate or Not to Automate: 5 Things to Consider when Building your Test Automation Strategy, Sr. Data Scientist at Rainforest QA, Maciej Gryka, uncovers how to build a balanced test automation strategy to deliver stellar customer experiences.
Listen to the full webinar by following this link: https://bit.ly/2HsgITi
WEBINAR- To Automate or Not to Automate: 5 Things to Consider when Building Your Test Automation Strategy
In this webinar Data Science Manager at RainforestQA, Maciej Gryka, shares how teams determine when to use automation and when humans are needed to deliver amazing customer experiences.
Access the webinar via this link: http://ht.ly/hfTi30jrIlC
This document discusses continuous integration and continuous deployment (CI/CD) using cloud infrastructure. It notes that the cloud is well-suited for CD with standardized, automated deployments and rollbacks. Following CI/CD practices allows for robust applications through fast, frequent iterations that are easy to test. The future of CD involves more automation around testing, deployment, rollbacks, and deploying to staging environments, with the goal of automatically deploying to production.
DevOps in Practice: When does "Practice" Become "Doing"?Michael Elder
DevOps has emerged as the hot trend in development buzzword-ology. With a few quick paragraphs, it proposes to decimate all of the traditional problems you've encountered during your development experience.
In IBM UrbanCode, we build products to help customers follow good DevOps practices. You may think DevOps is about the release process, but really it's about applying a mix of automation and operational practices earlier in your development life cycle so that rolling out to production becomes easier. DevOps promotes a focus on small-batch changes over large complex updates which are harder to predict and harder to roll back when problems occur. With greater velocity, rolling out smaller changes becomes more common place. Additionally, IBM UrbanCode makes extensive application of cloud technology that intercepts well with practices in DevOps around production-like environments.
In this talk, Michael Elder describes how we practice DevOps internally with a mixture of IBM-built and open source tools. He'll discuss the areas that we do well and the challenges that we have with changing our culture around areas like test automation. On top of that, he'll describe how you can leverage these approaches in your own development process!
A paradigm shift for testing - how to increase productivity 10x!Vasco Duarte
European IT industry need to deal with a huge salary gap with developing countries.
How can we increase our productivity and quality to compensate for the salary differences? This is a systems-thinking / Lean based approach to that problem
Test Automation on Large Agile Projects: It's Not a CakewalkTechWell
1) The document discusses test automation on large agile projects. It describes how test automation grew and responsibilities were divided across multiple teams over 2.5 years on one project.
2) Key reasons for test automation included keeping development on track, capturing knowledge, and automating repetitive work. Issues that arose included accumulating test debt and tools contributing to segmented responsibilities.
3) The presentation provides lessons learned around defining "Done", managing test debt, and organizing testing responsibilities across teams as projects increase in size and complexity. Setting expectations for test code quality and having integrated discussions on story size were emphasized.
The document discusses continuous deployment and integration. It describes why these practices are important for building robust applications with a solid architecture. Continuous deployment allows for very fast iteration and quick feedback cycles through continuous testing and automated deployment and rollback. The cloud is well-suited for continuous deployment with its standardized and automated features. It outlines how many startups and companies like Codeship and Github are implementing these practices and what the future may hold with more automation and usage of staging environments. It provides tips for getting started with continuous deployment and integration testing.
Model-based testing offers several advantages over traditional documentation-based approaches to quality assurance. It allows testers to create executable models that can automatically generate test cases and scripts, focusing testing on high-risk areas. When the software changes, the model can automatically update dependent tests. Using the same models across teams provides a central point of reference that brings business and development groups into alignment. Modeling catches design flaws earlier in the development process compared to traditional testing approaches.
The Survey Says: Testers Spend Their Time Doing...TechWell
How can testers contribute more to the success of their project and their company? How can they focus on asking the right questions, improving test planning and design, and finding defects so the business releases a quality product―even though there’s always one more fire to extinguish or one more request to fulfill? There aren’t enough hours in the day to do it all. Join Al Wagner as he reveals recent survey results showing where testers actually spend their time and where testers think their time would be better spent. Compare your own experience with what 250 test professionals from around the world reported. You may be surprised how prevalent testing challenges really are. Learn what techniques and technologies are available to help today’s test professionals execute what they were actually hired to do—test software. Return to your organization with an increased understanding of how other testers are dealing with their testing bottlenecks and what activities your peers view as the best use of their valuable time.
Eric Ries sllconf keynote: state of the lean startup movementEric Ries
Presentation by Eric Ries to kick off the 2011 Startup Lessons Learned conference #sllconf. Livestream here: http://www.justin.tv/startuplessonslearned
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.
The Essential Ingredients of a Leadership Development CurriculumCMOE
The document discusses elements that should be included in leadership development programs and workshops. It recommends 10 essential elements: breaking the ice, holding up a mirror, sharing a practical framework, facilitating "a-ha" moments, taking a test drive, providing quantitative feedback, more practice, tools and tips, knowledge transfer planning, and closing thoughts. It then provides more details about each element and CMOE's approach to customizing leadership development solutions for clients.
Current Trends in Agile - opening keynote for Agile Israel 2014Yuval Yeret
Yuval Yeret, AgileSparks’s CTO will give trends overview session – What is hot, what is not, in the lean agile industry/community – with the aim of exposing people and giving a big picture view that places the different trends as well as sessions in the conference into the right context. We will discuss trends like Scaling Agile (SAFe, Less, DAD), DevOps / Continuous Delivery, Modern Management aspects, Modern Change Management approaches such as Open-Agile-Adoption, What is going on in the world of Kanban, Agile Fluency, Technical Safety / Anzeneering, and maybe more.
http://agileisrael2014.com/current-trends-in-agile/
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdfTechgropse Pvt.Ltd.
In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
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.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
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
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
1. Continuous Deployment
Kane Mar
President, Scrumology Pty Ltd
http://Scrumology.com
Kane@Scrumology.com
Agile Australia 2010
2. In the beginning there was
Continuous Integration.
“Continuous Integration is a software
development practice where members of a team
integrate their work frequently, usually each
person integrates at least daily - leading to
multiple integrations per day ... Many teams find
that this approach leads to significantly reduced
integration problems and allows a team to
develop cohesive software more rapidly.”
- Martin Fowler
2
8. An interesting quote ...
“We need to get serious about breaking down the
silos within our organisations, getting customer
focused and driving some real change in the
industry. The biggest danger Youi represents is
that they will change the expectation and our
organisations will not be ready for it.”
- Isabel Frederick, Medibank Private
8
9. Some things to consider ...
» Some environments are easier than others
» Continuous Deployment for desktop
applications is difficult ... but still do-able
» Continuous Deployment requires extensive
automated testing and monitoring
9
10. Adopting Continuous Deployment
1. Try ... Adopt Continuous Integration
2. Try ... Stop the (Commit) line
3. Try ... Simple deployment
4. Try ... Realtime alerting
5. Test, test and test some more.
10