"Done" - Are We There Yet?
•
7 likes•994 views
One of the core values expressed in the agile manifesto is “working software over comprehensive documentation” because working software is what delivers value to our customers. Agile development requires a sofware development team have working software ready to deploy at the end of each iteration; but accomplishing this can be harder than it seems, especially when first starting with agile. In this highly interactive session you will understand how a team definition of “Done” is necessary to making agile delivery possible, and what you can do to make it happen while avoiding the pitfalls.
Report
Share
Report
Share
Download to read offline
Recommended
Humans of Agile and Scrum
The success of a project depends on the humans in the team. The personal relationships are of utmost important. Social & emotional intelligence is key to understanding the dynamics in the team. Trust in team goes up as people feel seen, heard and appreciated. This presentation is an attempt to look at the human side of Agile & Scrum and understanding its importance.
The Project Management Comeback
Project Managers often face an identity crisis when companies transition to agile: either become a scrum master, move to another role entirely, or another company! This discussion will demonstrate how project management can not only co-exist with your agile process, but thrive. Plus, you'll learn how Gilt blends agile principles with traditional project management techniques to bring their strategic initiatives to life.
Salesforce Agile Transformation - Agile 2007 Conference
Storytelling at the Agile 2007 Conference by Steve Greene and Chris Fry. Exposes the dramatic success at Salesforce.com in transforming R&D into an Agile development organization in a \"Big Bang\" way.
Lean vs scrum
Agile software development has proven to be more successful than traditional methods. However there are many Agile methodologies (Scrum, Kanban, Lean, XP). It is difficult to make a right choice.
Do you want to know the differences between Scrum and Lean? Perhaps you struggle with your existing Scrum implementation and looking for a better methodology. So did I. I spent many hours looking for continuous improvement beyond Retrospectives and Sprint Reviews. And I found my answer in applying Lean Principles.
This session will help you to increase your understanding of Lean and Scrum. It will also give you some practical examples of implementing Lean in Scrum teams.
Modernizing Development - The Road to Agility and DevOps at Compuware
Transforming a development organization from waterfall to agile is a big undertaking. Even larger when it’s a 40-year-old mainframe development organization. Having the vision for the future and the proper tools to enable that vision is essential. Join David Rizzo, an IT veteran, who led the transformation of Compuware from waterfall to agile and implementation of DevOps. You’ll see how Confluence was used to promote collaboration, in the office and in the field. How JIRA Software was used to track agile tasks and projects and how Bitbucket was utilized for handling source code. A modern DevOps toolchain is key to successful implementation. Using the Atlassian tools, Agile and DevOps were fully implemented across the entire organization.
Pitfalls of an Agile Transformation
The document discusses 10 common pitfalls that can occur during an agile transformation. The first pitfall is thinking agile is just a process change rather than a cultural shift. Other pitfalls include providing no guidance during the transformation, leadership not being properly aligned, transparency being abused, and organizational culture remaining misaligned after the transition to agile. The document stresses the importance of establishing a continuous improvement culture, aligning teams to products and customers, and gaining organizational alignment across the entire company for a successful agile transformation.
Agile Testing - What, why and how.
This document provides an overview of being an agile tester. It begins with introductions and then outlines key topics like what agile is, how it differs from conventional models, concepts to unlearn from traditional testing, the agile testing quadrants framework, taking a methodical approach to agile testing, and takeaways. The document emphasizes that testers in agile work closely with developers throughout the entire process, automate repetitive tasks, and add value beyond simply finding defects.
The Life of a Feature in Agile Development - Eric Dalgliesh
Here at Atlassian, we are all about creating the best tools to help you get the most out of your agile development. In this session, we'll cover the basics of how we use our products to develop a feature. We'll also show you a few ways to use our products that you might not have considered, that could kick your productivity up a notch. This talk highlights JIRA, Bamboo, HipChat, and Stash.
Recommended
Humans of Agile and Scrum
The success of a project depends on the humans in the team. The personal relationships are of utmost important. Social & emotional intelligence is key to understanding the dynamics in the team. Trust in team goes up as people feel seen, heard and appreciated. This presentation is an attempt to look at the human side of Agile & Scrum and understanding its importance.
The Project Management Comeback
Project Managers often face an identity crisis when companies transition to agile: either become a scrum master, move to another role entirely, or another company! This discussion will demonstrate how project management can not only co-exist with your agile process, but thrive. Plus, you'll learn how Gilt blends agile principles with traditional project management techniques to bring their strategic initiatives to life.
Salesforce Agile Transformation - Agile 2007 Conference
Storytelling at the Agile 2007 Conference by Steve Greene and Chris Fry. Exposes the dramatic success at Salesforce.com in transforming R&D into an Agile development organization in a \"Big Bang\" way.
Lean vs scrum
Agile software development has proven to be more successful than traditional methods. However there are many Agile methodologies (Scrum, Kanban, Lean, XP). It is difficult to make a right choice.
Do you want to know the differences between Scrum and Lean? Perhaps you struggle with your existing Scrum implementation and looking for a better methodology. So did I. I spent many hours looking for continuous improvement beyond Retrospectives and Sprint Reviews. And I found my answer in applying Lean Principles.
This session will help you to increase your understanding of Lean and Scrum. It will also give you some practical examples of implementing Lean in Scrum teams.
Modernizing Development - The Road to Agility and DevOps at Compuware
Transforming a development organization from waterfall to agile is a big undertaking. Even larger when it’s a 40-year-old mainframe development organization. Having the vision for the future and the proper tools to enable that vision is essential. Join David Rizzo, an IT veteran, who led the transformation of Compuware from waterfall to agile and implementation of DevOps. You’ll see how Confluence was used to promote collaboration, in the office and in the field. How JIRA Software was used to track agile tasks and projects and how Bitbucket was utilized for handling source code. A modern DevOps toolchain is key to successful implementation. Using the Atlassian tools, Agile and DevOps were fully implemented across the entire organization.
Pitfalls of an Agile Transformation
The document discusses 10 common pitfalls that can occur during an agile transformation. The first pitfall is thinking agile is just a process change rather than a cultural shift. Other pitfalls include providing no guidance during the transformation, leadership not being properly aligned, transparency being abused, and organizational culture remaining misaligned after the transition to agile. The document stresses the importance of establishing a continuous improvement culture, aligning teams to products and customers, and gaining organizational alignment across the entire company for a successful agile transformation.
Agile Testing - What, why and how.
This document provides an overview of being an agile tester. It begins with introductions and then outlines key topics like what agile is, how it differs from conventional models, concepts to unlearn from traditional testing, the agile testing quadrants framework, taking a methodical approach to agile testing, and takeaways. The document emphasizes that testers in agile work closely with developers throughout the entire process, automate repetitive tasks, and add value beyond simply finding defects.
The Life of a Feature in Agile Development - Eric Dalgliesh
Here at Atlassian, we are all about creating the best tools to help you get the most out of your agile development. In this session, we'll cover the basics of how we use our products to develop a feature. We'll also show you a few ways to use our products that you might not have considered, that could kick your productivity up a notch. This talk highlights JIRA, Bamboo, HipChat, and Stash.
Getting to the Heart of Agile
The document discusses issues with traditional development approaches and how adopting Agile practices helped address them. It introduces Agile concepts like Scrum, user stories, and ceremonies. While some have concerns that Agile has become diluted, the document argues the heart of Agile is experimentation - observing, forming hypotheses, running experiments, and analyzing results. This allows teams to solve their own problems through individual interactions over processes, focus on working software through experimentation rather than documentation, collaborate with customers through experiments instead of contracts, and constantly adapt through change by embracing experimentation.
Undercover Scrum Master - Agile2019
After three years as a Scrum Master and Agile coach, I hit a wall coaching a team that did not want to try popular Agile engineering techniques such as TDD and pair programming. I had become a Scrum Master after four years working on the business analysis and account ownership side of things and could not speak from personal experience about engineering practices. In order to get some first-hand experience and to gain a new perspective, I chose to spend a year or two as a software developer on a Scrum team.
The experience has been eye-opening. I experienced a tremendous cognitive load working with a wide array of technologies; this pulled my attention away from many of the collaborative and process-oriented activities I cared about as a Scrum Master. I was surprised to feel strong pressure to complete work quickly, cutting corners, even when the Product Owner and Scrum Master were not asking me to. When this pressure was explicit, it usually came from my fellow developers. On the other hand, there is real joy in writing code and seeing a system do something worthwhile that it wasn't doing before. My outlook has changed tremendously and is something I want to share with anyone who works with development teams, especially Scrum Masters and other coaches. I am still enjoying my time as a developer, but I'm looking forward to returning to coaching and incorporating this experience into my approach.
Slides for my presentation at Agile2019 (https://agile2019.sched.com/event/OD8A/undercover-scrum-master-dane-weber)
Scrummaster Needed Desperately at LAST Conf 2016 in Melbourne, Australia
There is a lot of reluctance within organisations to place ScrumMasters, let alone to spend money to hire them. Surely this role can be done by one of the developers, right? After all, it’s only a minor role, isn’t it? Far from it! The ScrumMaster is a full-time role. Without it, who can take care of the agile process on behalf of a busy Scrum team?
One way to help teams and management understand the value of the ScrumMaster’s role is to show them the volume and importance of tasks a ScrumMaster can fulfil, and the consequences of what happens if nobody takes care of these tasks. This session not only presents the 42 tasks of a ScrumMaster’s role but will clearly show that every Scrum team needs a ScrumMaster.
The Ultimate Agile Mix Tape (Agile 2017)
My session from Agile 2017 on mixing principles and practices from all the relevant Agile approaches to get the best process for your organization.
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...
Webinar by Clarke Ching Agile and ToC expert. Agile: the Good, the Bad and the Ugly. If your Agile is broken then this is how to fix it!
Your Agile teams are busy. Busy delivering. Busy improving. Your quality is amazing. Rework is low. The product looks great. Your users love it. You are a high performing team!
But your internal customers say your teams are slow. This session will teach you how to use the Theory of Constraints to figure out how to speed up, by finding the one thing that’s slowing them down.
This webinar will cover how, in an Agile environment:
- to better control scope creep,
- to reinforce your relationship with the I.T. Development team’s client,
- to be able to make commitments and honour them and
- to decide where your bottleneck should be.
About the speaker
Clarke Ching is a computer scientist with an MBA who discovered Goldratt’s Theory of Constraints (ToC) in 2003 and has been using it ever since to accelerate Agile initiatives. He is fascinated by Agile and obsessed with ToC.
He wrote the amazon best-sellers Rolling Rocks Downhill and The Bottleneck Rules. Rolling Rocks Downhill teaches 3 things: the fundamentals of Agile combined with ToC; how to use those fundamentals to deliver big projects faster and on time; and how to deliver quietly huge transformations. It’s been featured in The Guardian newspaper and The Spectator magazine. It was one of Barbara Oakley’s top 10 books of 2019. It was the #2 best-selling Leadership book on amazon.com, just behind Steven Covey’s 7-habits book.
He has been Agile / Lean / ToC expert in: GE Energy, Dell, Royal London (life insurance & pensions), Gazprom and Standard Life Aberdeen among other organizations. He is the past Chairperson of Agile Scotland. He is a lecturer at Victoria University School Of Management in New Zealand where he now lives.
Today he is the founder and Chief Productivity Officer of Odd Socks Consulting
DevOps: Hype or Hope
DevOps aims to break down silos between development and operations teams to reduce risks and speed up the software development process. It promotes continuous integration, delivery, testing and monitoring to catch issues early. While tools can help, DevOps is primarily a cultural shift where teams collaborate throughout the development lifecycle. Benefits include faster time to market, improved quality, better productivity and visibility into issues. Challenges involve changing mindsets and incentivizing collaboration between different roles.
Day projectcon real-world-scrum
The document discusses how Azure DevOps can be used to support Scrum and real-world software development. It describes how Azure DevOps provides tools for backlog management, sprint planning, sprint management, test case management, automated builds, releases, and more. It emphasizes the importance of having a written Definition of Done and provides an example Definition of Done.
Agile Development Practices - Productivity
Lunch and Learn I did on some general Agile and other practices that can make developers more productive.
Most of the content was in the speech though unfortunately.
Does this FizzGood? Improve velocity, predictability & agility by asking a si...
Frequent small good decoupled (FSGD) is a way of working that focuses on frequent delivery of small, good changes that are decoupled from each other. This allows for flexibility, learning, and value delivery. Examples show how customizing icons and releasing features can be done in a FSGD way through independent, coordinated changes. The benefits of FSGD include increased marketability, sustainability, frequency of feature delivery, and ability to gain repeat customers through a spirit of continuous improvement.
Agile with Waterfall
This document discusses integrating agile development practices into a waterfall methodology. It describes how agile practices like sprints, daily standups, and test-driven development can work with waterfall processes for requirements, testing and compliance. Sprints would deliver working software in short cycles with continuous feedback, while still meeting requirements defined in waterfall planning. Overall it argues that agile values around transparency, collaboration and adapting to change can improve waterfall projects if integrated appropriately for each organization's needs.
KAA How to get your Good agile teams to Great
The document provides tips for getting an agile team from good to great by focusing on outcomes over outputs, allocating time to incremental improvements to reduce technical debt, and limiting work in progress to focus on finishing projects instead of starting new ones in order to deliver value earlier. The presentation also discusses building trust, handling conflicts constructively, establishing team values and policies, and developing team members' breadth and depth of skills.
From Incremental & Iterative to Agile – What's the Right Process For Your Tea...
Every software team has heard the phrase “going agile" and many consider themselves agile, but what does it mean to be truly agile? Implementing agile in a team takes commitment and is anything but “nimble and quick”. In fact, sometimes you need to become good at Incremental and Iterative Development (IID) before you can be Agile. In this talk, you will learn whether IID or Agile is right for your team, how to deploy and maintain a selected process, and how to make JIRA work for your development process.
Mission Impossible: Banking on a SAFe QuickStart
Imagine inheriting the job leading the "business as usual" change program for Westpac's new online banking platform. Your challenge, should you choose to accept it (like you have a choice), is to “turn it Agile”. You are “gifted” a SAFe Program Consultant, not that you know what that is. So you tell them of your predicament and ask if Agile will help.
As one would expect, the Agile consultant can see the path to agility. However, the recommended approach seems somewhat unconventional. A one-week immersion program that will transform the waterfall machine into an Agile Release Train!
Tune into this session to learn how one of Australia’s largest banks adopted Agile on a mission critical application overnight.
Attendees at this session will learn the benefits and pitfalls of using SAFe’s notorious Quick Start approach to implementing Agile, and the facts about what it really takes to “Quick Start” an Agile Release Train.
Continuous Feedback: The New Paradigm by Jared Richardson
In these slides Jared discusses creating intentional feedback in several forms, but then we’ll focus on continuous integration and continuous testing/continuous deployment.
Available on testhuddle.com
Let's Build a Product Development Organization!
A workshop on building agile organizations from small single teams through large numbers of teams including discussions of long term organizational thinking and leadership coaching. Participants will use their current organizations as a starting point and will project them through future growth and challenges.
Scaling Agile with JIRA
This document discusses scaling agile practices in large organizations. It recommends scaling customization of issue types, fields, and workflows in project management software as the organization scales its culture. Specific tips include tracking who is involved in work, following story progress and understanding epic value across projects. Flexible tracking of investment details is also recommended.
10 Questions For Your Scrum Master Interview
This document provides 10 questions to ask during a Scrum Master interview to determine how agile the position and team are. The questions cover topics like iteration length, team size and structure, involvement of product owners, code deployment practices, testing approach, requirements documentation, use of metrics, meeting frequency, executive support for agile, and the Scrum Master's responsibilities. Answers that indicate shorter iterations, small cross-functional teams, frequent product owner availability, continuous integration, test-driven development, user stories, estimating with story points and daily stand-ups would suggest a truly agile approach, while longer responses would be less agile.
The Most Productive Meeting In The World (DevOps Days Ohio 2017)
The document describes how an operations team improved their productivity and work environment through changes to their meetings and processes. They reduced time spent in communication tools like Slack, increased engineering time, and streamlined decision making. Their weekly meetings provided a safe space to discuss issues and make immediate decisions. As a result, the team felt more empowered, productive, and able to focus on engineering work rather than meetings and communication. They also improved career development, team health, and advocacy for automation and infrastructure as code. A few challenges remained around timely discussion of all topics and external dependencies.
"Deadlines" are killing agile
This talk will address the flawed way in which we marry the Agile and traditional ways of doing things when trying to deliver in a timely fashion, particularly to deadlines. It will suggest an alternative approach which puts a greater emphasis on Agile and Lean principles. Ironically, by using genuine time constraints as a factor in the prioritisation of work rather than as a focus for its execution, the odds of meeting those "deadlines" are actually improved. This talk will show you how to do that. And then truly glean the benefits of Agile.
Executives of software product and service companies always want stuff delivered faster, cheaper and better. Agile principles and methods are believed to be a way to achieve this. Unfortunately, the typical approach taken by software organisations is to use Agile as a local optimisation for development teams, creating a paradox where things actually take way longer than they need to, and are of a quality way lower than they should be. The "deadlines" emerging from the customer-facing parts of the business are consistently not met, causing conflict and confusion in why things never get done "on time", and why the quality of the software isn't better.
In short, the continued paradigm of deadline-driven development is killing the benefits that Agile Software Development can bring.
Being vs Doing agile
Most of the times I have seen the teams spending immense amount of time in mastering the mechanics than the intent.
Key to successful agile adoption is to have the agile as a team culture than just doing it
ALE15 The real value of a definition of done
The document discusses the value of having a Definition of Done (DoD) for software development iterations. A DoD lists all the criteria needed to consider a user story complete. This helps improve quality, deliver features faster, and minimize bugs and rework. It also provides transparency into a team's process and capabilities. The DoD should evolve over time as a team's skills improve to balance delivering quickly while maintaining quality.
Definition of Done - Agile Pays Basque - 23/09/2016
Slides de la session "Dodelinant de la tête" à Agile Pays Basque
More Related Content
What's hot
Getting to the Heart of Agile
The document discusses issues with traditional development approaches and how adopting Agile practices helped address them. It introduces Agile concepts like Scrum, user stories, and ceremonies. While some have concerns that Agile has become diluted, the document argues the heart of Agile is experimentation - observing, forming hypotheses, running experiments, and analyzing results. This allows teams to solve their own problems through individual interactions over processes, focus on working software through experimentation rather than documentation, collaborate with customers through experiments instead of contracts, and constantly adapt through change by embracing experimentation.
Undercover Scrum Master - Agile2019
After three years as a Scrum Master and Agile coach, I hit a wall coaching a team that did not want to try popular Agile engineering techniques such as TDD and pair programming. I had become a Scrum Master after four years working on the business analysis and account ownership side of things and could not speak from personal experience about engineering practices. In order to get some first-hand experience and to gain a new perspective, I chose to spend a year or two as a software developer on a Scrum team.
The experience has been eye-opening. I experienced a tremendous cognitive load working with a wide array of technologies; this pulled my attention away from many of the collaborative and process-oriented activities I cared about as a Scrum Master. I was surprised to feel strong pressure to complete work quickly, cutting corners, even when the Product Owner and Scrum Master were not asking me to. When this pressure was explicit, it usually came from my fellow developers. On the other hand, there is real joy in writing code and seeing a system do something worthwhile that it wasn't doing before. My outlook has changed tremendously and is something I want to share with anyone who works with development teams, especially Scrum Masters and other coaches. I am still enjoying my time as a developer, but I'm looking forward to returning to coaching and incorporating this experience into my approach.
Slides for my presentation at Agile2019 (https://agile2019.sched.com/event/OD8A/undercover-scrum-master-dane-weber)
Scrummaster Needed Desperately at LAST Conf 2016 in Melbourne, Australia
There is a lot of reluctance within organisations to place ScrumMasters, let alone to spend money to hire them. Surely this role can be done by one of the developers, right? After all, it’s only a minor role, isn’t it? Far from it! The ScrumMaster is a full-time role. Without it, who can take care of the agile process on behalf of a busy Scrum team?
One way to help teams and management understand the value of the ScrumMaster’s role is to show them the volume and importance of tasks a ScrumMaster can fulfil, and the consequences of what happens if nobody takes care of these tasks. This session not only presents the 42 tasks of a ScrumMaster’s role but will clearly show that every Scrum team needs a ScrumMaster.
The Ultimate Agile Mix Tape (Agile 2017)
My session from Agile 2017 on mixing principles and practices from all the relevant Agile approaches to get the best process for your organization.
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...
Webinar by Clarke Ching Agile and ToC expert. Agile: the Good, the Bad and the Ugly. If your Agile is broken then this is how to fix it!
Your Agile teams are busy. Busy delivering. Busy improving. Your quality is amazing. Rework is low. The product looks great. Your users love it. You are a high performing team!
But your internal customers say your teams are slow. This session will teach you how to use the Theory of Constraints to figure out how to speed up, by finding the one thing that’s slowing them down.
This webinar will cover how, in an Agile environment:
- to better control scope creep,
- to reinforce your relationship with the I.T. Development team’s client,
- to be able to make commitments and honour them and
- to decide where your bottleneck should be.
About the speaker
Clarke Ching is a computer scientist with an MBA who discovered Goldratt’s Theory of Constraints (ToC) in 2003 and has been using it ever since to accelerate Agile initiatives. He is fascinated by Agile and obsessed with ToC.
He wrote the amazon best-sellers Rolling Rocks Downhill and The Bottleneck Rules. Rolling Rocks Downhill teaches 3 things: the fundamentals of Agile combined with ToC; how to use those fundamentals to deliver big projects faster and on time; and how to deliver quietly huge transformations. It’s been featured in The Guardian newspaper and The Spectator magazine. It was one of Barbara Oakley’s top 10 books of 2019. It was the #2 best-selling Leadership book on amazon.com, just behind Steven Covey’s 7-habits book.
He has been Agile / Lean / ToC expert in: GE Energy, Dell, Royal London (life insurance & pensions), Gazprom and Standard Life Aberdeen among other organizations. He is the past Chairperson of Agile Scotland. He is a lecturer at Victoria University School Of Management in New Zealand where he now lives.
Today he is the founder and Chief Productivity Officer of Odd Socks Consulting
DevOps: Hype or Hope
DevOps aims to break down silos between development and operations teams to reduce risks and speed up the software development process. It promotes continuous integration, delivery, testing and monitoring to catch issues early. While tools can help, DevOps is primarily a cultural shift where teams collaborate throughout the development lifecycle. Benefits include faster time to market, improved quality, better productivity and visibility into issues. Challenges involve changing mindsets and incentivizing collaboration between different roles.
Day projectcon real-world-scrum
The document discusses how Azure DevOps can be used to support Scrum and real-world software development. It describes how Azure DevOps provides tools for backlog management, sprint planning, sprint management, test case management, automated builds, releases, and more. It emphasizes the importance of having a written Definition of Done and provides an example Definition of Done.
Agile Development Practices - Productivity
Lunch and Learn I did on some general Agile and other practices that can make developers more productive.
Most of the content was in the speech though unfortunately.
Does this FizzGood? Improve velocity, predictability & agility by asking a si...
Frequent small good decoupled (FSGD) is a way of working that focuses on frequent delivery of small, good changes that are decoupled from each other. This allows for flexibility, learning, and value delivery. Examples show how customizing icons and releasing features can be done in a FSGD way through independent, coordinated changes. The benefits of FSGD include increased marketability, sustainability, frequency of feature delivery, and ability to gain repeat customers through a spirit of continuous improvement.
Agile with Waterfall
This document discusses integrating agile development practices into a waterfall methodology. It describes how agile practices like sprints, daily standups, and test-driven development can work with waterfall processes for requirements, testing and compliance. Sprints would deliver working software in short cycles with continuous feedback, while still meeting requirements defined in waterfall planning. Overall it argues that agile values around transparency, collaboration and adapting to change can improve waterfall projects if integrated appropriately for each organization's needs.
KAA How to get your Good agile teams to Great
The document provides tips for getting an agile team from good to great by focusing on outcomes over outputs, allocating time to incremental improvements to reduce technical debt, and limiting work in progress to focus on finishing projects instead of starting new ones in order to deliver value earlier. The presentation also discusses building trust, handling conflicts constructively, establishing team values and policies, and developing team members' breadth and depth of skills.
From Incremental & Iterative to Agile – What's the Right Process For Your Tea...
Every software team has heard the phrase “going agile" and many consider themselves agile, but what does it mean to be truly agile? Implementing agile in a team takes commitment and is anything but “nimble and quick”. In fact, sometimes you need to become good at Incremental and Iterative Development (IID) before you can be Agile. In this talk, you will learn whether IID or Agile is right for your team, how to deploy and maintain a selected process, and how to make JIRA work for your development process.
Mission Impossible: Banking on a SAFe QuickStart
Imagine inheriting the job leading the "business as usual" change program for Westpac's new online banking platform. Your challenge, should you choose to accept it (like you have a choice), is to “turn it Agile”. You are “gifted” a SAFe Program Consultant, not that you know what that is. So you tell them of your predicament and ask if Agile will help.
As one would expect, the Agile consultant can see the path to agility. However, the recommended approach seems somewhat unconventional. A one-week immersion program that will transform the waterfall machine into an Agile Release Train!
Tune into this session to learn how one of Australia’s largest banks adopted Agile on a mission critical application overnight.
Attendees at this session will learn the benefits and pitfalls of using SAFe’s notorious Quick Start approach to implementing Agile, and the facts about what it really takes to “Quick Start” an Agile Release Train.
Continuous Feedback: The New Paradigm by Jared Richardson
In these slides Jared discusses creating intentional feedback in several forms, but then we’ll focus on continuous integration and continuous testing/continuous deployment.
Available on testhuddle.com
Let's Build a Product Development Organization!
A workshop on building agile organizations from small single teams through large numbers of teams including discussions of long term organizational thinking and leadership coaching. Participants will use their current organizations as a starting point and will project them through future growth and challenges.
Scaling Agile with JIRA
This document discusses scaling agile practices in large organizations. It recommends scaling customization of issue types, fields, and workflows in project management software as the organization scales its culture. Specific tips include tracking who is involved in work, following story progress and understanding epic value across projects. Flexible tracking of investment details is also recommended.
10 Questions For Your Scrum Master Interview
This document provides 10 questions to ask during a Scrum Master interview to determine how agile the position and team are. The questions cover topics like iteration length, team size and structure, involvement of product owners, code deployment practices, testing approach, requirements documentation, use of metrics, meeting frequency, executive support for agile, and the Scrum Master's responsibilities. Answers that indicate shorter iterations, small cross-functional teams, frequent product owner availability, continuous integration, test-driven development, user stories, estimating with story points and daily stand-ups would suggest a truly agile approach, while longer responses would be less agile.
The Most Productive Meeting In The World (DevOps Days Ohio 2017)
The document describes how an operations team improved their productivity and work environment through changes to their meetings and processes. They reduced time spent in communication tools like Slack, increased engineering time, and streamlined decision making. Their weekly meetings provided a safe space to discuss issues and make immediate decisions. As a result, the team felt more empowered, productive, and able to focus on engineering work rather than meetings and communication. They also improved career development, team health, and advocacy for automation and infrastructure as code. A few challenges remained around timely discussion of all topics and external dependencies.
"Deadlines" are killing agile
This talk will address the flawed way in which we marry the Agile and traditional ways of doing things when trying to deliver in a timely fashion, particularly to deadlines. It will suggest an alternative approach which puts a greater emphasis on Agile and Lean principles. Ironically, by using genuine time constraints as a factor in the prioritisation of work rather than as a focus for its execution, the odds of meeting those "deadlines" are actually improved. This talk will show you how to do that. And then truly glean the benefits of Agile.
Executives of software product and service companies always want stuff delivered faster, cheaper and better. Agile principles and methods are believed to be a way to achieve this. Unfortunately, the typical approach taken by software organisations is to use Agile as a local optimisation for development teams, creating a paradox where things actually take way longer than they need to, and are of a quality way lower than they should be. The "deadlines" emerging from the customer-facing parts of the business are consistently not met, causing conflict and confusion in why things never get done "on time", and why the quality of the software isn't better.
In short, the continued paradigm of deadline-driven development is killing the benefits that Agile Software Development can bring.
Being vs Doing agile
Most of the times I have seen the teams spending immense amount of time in mastering the mechanics than the intent.
Key to successful agile adoption is to have the agile as a team culture than just doing it
What's hot (20)
Scrummaster Needed Desperately at LAST Conf 2016 in Melbourne, Australia
Scrummaster Needed Desperately at LAST Conf 2016 in Melbourne, Australia
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...
Does this FizzGood? Improve velocity, predictability & agility by asking a si...
Does this FizzGood? Improve velocity, predictability & agility by asking a si...
From Incremental & Iterative to Agile – What's the Right Process For Your Tea...
From Incremental & Iterative to Agile – What's the Right Process For Your Tea...
Continuous Feedback: The New Paradigm by Jared Richardson
Continuous Feedback: The New Paradigm by Jared Richardson
The Most Productive Meeting In The World (DevOps Days Ohio 2017)
The Most Productive Meeting In The World (DevOps Days Ohio 2017)
Viewers also liked
ALE15 The real value of a definition of done
The document discusses the value of having a Definition of Done (DoD) for software development iterations. A DoD lists all the criteria needed to consider a user story complete. This helps improve quality, deliver features faster, and minimize bugs and rework. It also provides transparency into a team's process and capabilities. The DoD should evolve over time as a team's skills improve to balance delivering quickly while maintaining quality.
Definition of Done - Agile Pays Basque - 23/09/2016
Slides de la session "Dodelinant de la tête" à Agile Pays Basque
Definition of Done and Acceptance Criteria
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Lightening Talk: definition of ready
This document discusses the concept of "READY" in agile development. It defines READY as having clear goals and criteria, understanding how to complete the work, having the ability to complete it in the sprint, and managing risks and dependencies. Work that is not READY causes problems like missed deadlines and unclear acceptance criteria. The document recommends using READY as a quality gate to prevent unprepared work from being committed to sprints. It provides examples of how to structure product backlogs and incrementally prepare stories to become READY. The results section notes low adoption rates for READY compared to definitions of done.
Definition of Done and Product Backlog refinement
The document discusses product backlog refinement and the definition of done in agile software development. It emphasizes that product backlog refinement is an important meeting to clarify and estimate user stories and work items to have a ready backlog for iteration planning. It also stresses that having a clear definition of done helps improve team quality, transparency for stakeholders, better release planning, and minimizing risks. Regular product backlog refinement coupled with a well-defined definition of done are key practices for achieving agility.
Dod is not done
The document discusses the Definition of Done (DoD) in the context of Scrum. It states that the DoD is a checklist of activities that must be completed to produce software, such as writing code, testing, and creating documentation. The DoD adds verifiable value and serves as the primary reporting mechanism for team members. Additionally, the DoD helps ensure transparency in the work being done. The document emphasizes that software is not considered "done" until it is deployed to production and being monitored.
Definition Of Done
The document discusses defining the "Definition of Done" (DoD) which establishes the quality standards and activities required to consider a user story or increment of work complete. It notes problems that can occur without a DoD such as technical debt, unpredictable delivery dates, and overcommitting work. The document recommends that the team, including the product owner, define the DoD during backlog estimation and that the definition evolves over sprints based on the team's experience. It provides some examples of DoD criteria for user stories and sprints.
Definition of Ready (XP2011)
The document discusses the definition of ready as it relates to user stories and sprints in agile software development. It provides details on what constitutes a user story being ready, including it being defined, having acceptance criteria, identified dependencies, sized by the team, and more. It also lists criteria for a sprint to be ready, such as the sprint backlog being prioritized and containing all committed work with no hidden work, and all team members having calculated their capacity for the sprint.
Definition of Done
The document discusses the definition of "done" and why it is important for software development projects. It provides multiple definitions that increase in level of completeness, from just having the code checked in to having the code fully tested, documented, packaged, and reviewed with all bugs closed. The definitions help ensure software meets quality standards before being considered finished.
Viewers also liked (9)
Definition of Done - Agile Pays Basque - 23/09/2016
Definition of Done - Agile Pays Basque - 23/09/2016
Similar to "Done" - Are We There Yet?
U Xmagic Agile Presentation
SketchFlow allows users to quickly prototype and iterate on user interface designs without extensive time or resource investments. It provides an informal way to explore ideas and evolve rough concepts into living prototypes. This rapid and cost-effective approach focuses on being creative and building the best solution.
Effective prototyping with SketchFlow allows experimenting with application flow, screen layouts, and state transitions. The interactive player engages clients by displaying working prototypes and collecting feedback directly in Expression Blend.
Agile practices like iterative development and user-centered design help teams collaborate effectively and respond quickly to change.
Information Development in an Agile Environment
The document discusses Information Development (InfoDev) considerations for transitioning to an Agile development environment. Some key points:
1. InfoDev tasks need to be reduced and linked to development iterations to minimize lag and rework. Documentation must be completed within each iteration.
2. An Agile documentation process includes authoring content in iterations and conducting end-to-end reviews in hardening iterations before finalizing.
3. Transitioning required changes like more standalone documentation chunks for review versus large documents, and shifting accountability for documentation from InfoDev to development teams.
Agile intro resources
The document provides an overview of Agile development methods. It discusses what Agile is, why it is important, and how difficult it can be to implement. Specifically, it defines Agile as an iterative approach that emphasizes adaptation, incremental delivery, and collaboration. It then summarizes the Scrum framework, noting its core roles, meetings, and iterative process for completing work in short cycles.
Introduction to Agile Software Development Process
The document provides an introduction to agile software development processes. It discusses the waterfall model and iterative and incremental model. It then defines agile as a collection of iterative development methodologies that are lightweight and value individuals, interactions, working software, and responding to change. The document outlines agile principles and practices like user stories, story points, test-driven development, pair programming, daily stand-up meetings, story boards, burn down charts, continuous integration, and retrospectives. It concludes with feedback from an agile team noting benefits like earlier defect detection but also challenges in applying new techniques and lack of product management involvement.
Markus Clermont - Surviving in an Agile Environment - Google - SoftTest Ireland
Visit www.softtest.ie and join our mailing list to hear about upcoming Irish Software Testing Events.
HP DevOps Summit 2021
This document summarizes a presentation about HP's journey with inner sourcing. It describes initial challenges like code ownership by individuals leading to long wait times. A senior leader paper defined a new engineering culture and strategic direction. Their solution was an inner source program with unified guidelines, establishing trusted committers, and prioritizing foundational capabilities. They share lessons like underestimating trust-building and the importance of early wins. The benefits of inner sourcing included empowered engineers, decreased wait times, new skills, and faster delivery of high-quality products.
HP's Dev Ops Summit 2021, Better Together: An Inner Source Journey
This presentation was given at HP's DevOps Summit 2021. Aliza Carpio and Rocio Montes shared strategy, tactics and lessons learned from their past inner source work.
Girl Geek X Indeed Talks (January 18, 2018)
Girl Geek X Indeed lightning talks from -
- Ashley Graves, Indeed Security Engineer
- Jessi Roesner, Indeed Site Reliability Engineer
- Samikshya Patra, Indeed Engineering Manager
- Janie Clarke, Indeed Product Manager
- Kim Williams, Indeed Director of Experience Design
More at www.girlgeek.io
Agile20070912
The document discusses an introduction to agile principles and practices. It begins with introductions from Yves Hanoulle and Vera Peeters. It then discusses agile manifesto values and principles. It covers topics like agile project management, scaling agile, and introduces an XP game exercise. The goal is to provide an overview of agile concepts and how they can help the situation at Porthus.
The complexity in the simplicity of Agile? by Arie van Bennekum
Looking at Agile, it is so simple. In fact Agile is just structured common sense. Still so many people struggle to get their success in Agile. What is going on? The point is Agile, with all its simplicity, is based on different paradigms and the old paradigms hinder. The question is, can you identify thew old paradigms and furthermore, how do you change them. Arie van Bennekum will take you in his talk on his 22 years Agile journey and share his experience, successes, his delta’s and IATM, the Integrated Agile Transformation Model he developed for Agile transformations. IATM is a successful Agile change process to (the next level of) Agile he and his teams use doing international Agile transformations.
DevOps for Managers
Mark Mzyk
Engineering Manager with Chef
Find more by Mark Mzyk: https://speakerdeck.com/mmzyk
All Things Open
October 26-27, 2016
Raleigh, North Carolina
Agile in Action - Agile Overview for Developers
Excerpt from a presentation I gave to the University of Alabama Association for Computing Machinery in November 2010. I wanted to give the students a practical overview of Agile and Scrum and give them some perspective on what Agile means for developers.
Why Isn't Clean Coding Working For My Team
Teams fail to achieve the full benefit of the "clean code" approach when they focus on the code and neglect the Agile process. The full title of Uncle Bob's "Clean Code" book is "Clean Code: A Handbook of Agile Software Craftsmanship". This talk presents an depth look at necessary relationship between Clean Code software craftsmanship and the Agile methodology, identifies common scenarios and situations where teams may fall short of recognizing and respecting that relationship, and provides practical recommendations for achieving a fully integrated process of Agile Software Craftsmanship.
Robert Martin's book "Clean Code: A Handbook of Agile Software Craftsmanship" had a huge positive impact on software development teams that adopted his approach to "Agile Software Craftsmanship". But teams sometimes fail to achieve the full benefit of the "clean code" approach because they focus on the code and neglect the Agile process.
It's easy to do: the book provides such clear, practical advice on how to write code that is easier to maintain, more reliable, and less error prone that developers adopt those techniques to great effect and fail to pursue and adopt the harder, agile process recommendations from the book. This is further complicated by the fact that there is now a Software Craftsmanship Manifesto that is separate from the Agile Manifesto.
So, how does using selected clean code techniques break the Agile process defined in the the book? What is the relationship between the two that Uncle Bob wanted us to understand and adopt in toto? Where do we go wrong? Are there some work environment or business driven scenarios that are more likely to break the relationship?
This presentation addresses those questions and more by an taking an in depth look at necessary relationship between Clean Code software craftsmanship and the Agile methodology, identifies common scenarios and situations where teams may fall short of recognizing and respecting that relationship, and provides practical recommendations for achieving a fully integrated process of Agile Software Craftsmanship.
You keep using the word agile, i do not think it means what you think it means
Slides for the talk about what people think agile is, what agile is about and how you can get back to the idea of agile.
A recording of the talk from NDC London 2016 should be available here https://vimeo.com/158164783
Scaling Agile - Agility Defined
The document discusses key aspects of agile methodology including the Agile Manifesto, Scrum roles and ceremonies, product backlogs, user stories, and an individual's role on an agile team. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change over processes, tools, documentation, contracts, and following a plan. Scrum uses roles of Product Owner, Scrum Master, and self-organizing teams. Product backlogs contain prioritized user stories which are small pieces of functionality with acceptance criteria. Metascrums involve key stakeholders to resolve impediments. An individual's role is to focus on testing, active listening, and delivering value frequently through working software.
Agile Software Development
Learn the lifecycle of a software startup company, the realities of software development and the key decision points in Hemant Elhence's presentation.
Synerzip Agile Software Development
Learn the lifecycle of a software startup company, the realities of software development and the key decision points in Hemant Elhence's presentation.
Lean Business Analysis and UX Runway - Natalie Warnert
How to integrate BAs and UX in a Agile/Lean environment to create an MVP to learn while reducing potential waste. Presented at Lviv IT Arena, 2015 in Lviv, Ukraine by Natalie Warnert, October 3, 2015
www.nataliewarnert.com
Lean Business Analysis and UX Runway: Managing Value by Reducing Waste (Natal...
The document discusses how business analysts and UX professionals can collaborate effectively in an Agile environment through a process called the "Analyst and UX Runway". This process involves business analysts and UX professionals working together throughout the product development lifecycle from initial planning through execution and review, with the goal of continuously delivering value to customers through short iterations of planning, development and feedback. The Analyst and UX Runway approach aims to balance upfront planning with flexibility to incorporate frequent customer feedback.
Fundamentals of Agile
The document discusses fundamentals of agile development including the agile manifesto and its 12 principles. It emphasizes values such as individuals and interactions, working software, customer collaboration, and responding to change. It also discusses agile processes like Scrum and Kanban, continuous improvement through inspection and adaptation, and techniques like test-driven development, pair programming, and continuous integration to enable regular rapid feedback. Finally, it notes that while agile is popular, the real question is whether it will make teams more successful in delivering value to customers on time and under budget.
Similar to "Done" - Are We There Yet? (20)
Introduction to Agile Software Development Process
Introduction to Agile Software Development Process
Markus Clermont - Surviving in an Agile Environment - Google - SoftTest Ireland
Markus Clermont - Surviving in an Agile Environment - Google - SoftTest Ireland
HP's Dev Ops Summit 2021, Better Together: An Inner Source Journey
HP's Dev Ops Summit 2021, Better Together: An Inner Source Journey
The complexity in the simplicity of Agile? by Arie van Bennekum
The complexity in the simplicity of Agile? by Arie van Bennekum
You keep using the word agile, i do not think it means what you think it means
You keep using the word agile, i do not think it means what you think it means
Lean Business Analysis and UX Runway - Natalie Warnert
Lean Business Analysis and UX Runway - Natalie Warnert
Lean Business Analysis and UX Runway: Managing Value by Reducing Waste (Natal...
Lean Business Analysis and UX Runway: Managing Value by Reducing Waste (Natal...
More from Paul Rayner
Fighting the Invisible Enemy - Paul Rayner (NewCrafts 2018)
Queues are inevitable in product development processes but can be managed and constrained to reduce economic waste. The goal should be to reduce congestion like managing traffic flow on a freeway rather than maximizing utilization like a parking lot. Measuring and modeling queues can help highlight where handoffs and wait states undermine performance. When queues start to grow, quick interventions may include limiting new commitments, adjusting staffing levels, changing the work mix, or applying efforts to reduce the queue. Everything flows, so adaptive management of queues is important to maintain flow in business processes.
Strategic design using ddd
The document discusses strategic design using Domain-Driven Design (DDD). It notes that DDD focuses design efforts where it matters most by prioritizing the core domain and using different strategies for generic, supporting, and core subdomains. Tactical DDD patterns can be applied to the core domain. The document provides examples and poses questions to illustrate DDD concepts.
Keeping Architectures Relevant - 4 Feb 2010
Too many systems seem to become legacy upon release, while some never even have a chance to move into production before they are undermined by the calcification of unmet expectations and mismatched domain needs. Regardless of the design effort early in the lifecycle, neglect of the domain model and inflexible design results in the increasing irrelevance of the initial architecture of a system.
Sustainable and successful software development is all about managing complexity and enabling change, and successful architects create designs that clearly address both. As an architecture is allowed to emerge, evolve, and mature, it becomes a true reflection of the deep understanding of both domain experts and developers. Architects who expect their initial design to evolve, and who design with evolution in mind, create architectures that deliver a strong competitive advantage to the business.
.NET, Open Source and Mono (presented at Colorado Springs OS Group (9/24/2009)
Open source projects in .NET are flourishing. Can mainstream open source developers continue to ignore the platform that exerts such a large influence on IT development globally? Come prepared to challenge your assumptions about OSS development in .NET, and to learn about the state of OSS in .NET and how the Mono Project fits into this picture. Mono is an open development initiative sponsored by Novell to develop an open source, UNIX version of the Microsoft .NET development platform. Its objective is to enable UNIX developers to build and deploy cross-platform .NET applications on Linux, BSD, UNIX, Mac OS X, Solaris, iPhone and Windows.This presentation will provide an introduction to OSS in .NET, with a particular focus on how Mono 2.4 brings the benefits of the .NET framework to platforms beyond Windows.
Introduction To Domain Driven Design
Domain-Driven Design applies whenever we are operating in a complex, intricate domain. Make the software a reflection of the domain. The software needs to incorporate and express the core concepts and elements of the domain, and precisely realize the relationships between them.
.NET, OSS & Mono
The Mono Project is an open development initiative sponsored by Novell to develop an open source, UNIX version of the Microsoft .NET development platform. Its objective is to enable UNIX developers to build and deploy cross-platform .NET applications, and can run on Linux, BSD, UNIX, Mac OS X, Solaris and Windows operating systems.This presentation will provide an introduction to Mono 2.0 and show how it brings the benefits of the .NET framework to platforms beyond Windows. Part of the presentation will also cover the state of open source development in the .NET space and what Microsoft needs to ensure that .NET-based open source initiatives flourish.
More from Paul Rayner (6)
Fighting the Invisible Enemy - Paul Rayner (NewCrafts 2018)
Fighting the Invisible Enemy - Paul Rayner (NewCrafts 2018)
.NET, Open Source and Mono (presented at Colorado Springs OS Group (9/24/2009)
.NET, Open Source and Mono (presented at Colorado Springs OS Group (9/24/2009)
Recently uploaded
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
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).
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Recently uploaded (20)
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
"Done" - Are We There Yet?
- 1. “Done” Are We There Yet? Paul Rayner
- 2. Questions? Write them down on a sticky note…
- 3. Agile Manifesto • Individuals and interactions – over processes and tools • Working software – over comprehensive documentation • Customer collaboration – over contract negotiation • Responding to change – over following a plan
- 4. Agile Manifesto • Individuals and interactions – over processes and tools • Working software – over comprehensive documentation • Customer collaboration – over contract negotiation • Responding to change – over following a plan
- 5. Agile Principles • Highest priority: satisfy the customer through early and continuous delivery of valuable software. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Working software is the primary measure of progress.
- 6. Definition of “Done” Roleplay!
- 7. Definition of “Done” Why?
- 8. An Agile Framework: Scrum
- 15. Definition of “Done” Group Exercise
- 16. Brainstorming: What do we need to do, as a team, to ship software to our customers/stakeholders?
- 18. Categorization: How should we group these activities/artifacts?
- 19. Categorization: How should we group these activities/artifacts? Focus on customer value
- 20. Sorting & Consolidation: Where are the duplicates?
- 21. Sorting & Consolidation: Where are the duplicates? What % is writing code?
- 22. Non-Iteration Artifacts: Which of these things can not be done every iteration? Why?
- 23. Agree => Iterate Gain consensus, review regularly…and refine
- 25. Review
- 26. Resources Note: Much of the materials for the exercises in this session can be found in the “Done List Creation Exercise” by Mitch Lacey and “Building a Definition of Done” by Chris Sterling http://delicious.com/virtualgenius/Done
- 27. Agility. Craft. Architecture. Paul Rayner paul@virtual-genius.com 303.374.4370 @virtualgenius (Twitter) http://virtualgenius.spaces.live.com