For the reboot of the Agile Orlando use group, we did lightning talks on various topics. I shared some perspectives on scaling agile. More at http://agileorlando.com
Building QA Team that matters for an Agile WorldMaurizio Mancini
Presentation from Quest 2015 - Covers building a new QA Team that matters, how to approach Agile Testing, and how to present the message to renovate your existing QA team for Agile.
Transforming Managers for an Agile Deployment - Agile Tour Montreal 2017Maurizio Mancini
Presentation at Agile Tour Montreal 2017 by Maurizio Mancini of Exempio. This presentation is an overview of what role software managers could play in an Agile world.
The document discusses how to reboot an agile team. It outlines six essential ingredients needed which include leadership, management style, vision, engagement, quality, and an agile coach. It then describes a five sprint process to reboot the team, with each sprint focusing on a different aspect of rebuilding the team such as understanding the current problems, breaking old habits, delivering working software, and becoming a self-organizing team. The document emphasizes that change is difficult and will involve managing emotions, and recommends using a modern management style and clear plan to guide the reboot of the agile team.
From Incremental & Iterative to Agile – What's the Right Process For Your Tea...Atlassian
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.
This document outlines a method for rebooting an agile team in 5 sprints. It discusses assessing the current state using a survey across 5 dimensions. Sprint 1 focuses on understanding the current problems. Sprint 2 aims to break the status quo and motivate change. Sprint 3 has the team experience pain while implementing changes. Sprint 4 has the team cross the edge and collaborate better. Sprint 5 removes training wheels to create a high performing, self-organized agile team. The method emphasizes the importance of leadership, vision, engagement and quality from the start. It also notes that emotions are part of any change process and should be managed well.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
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.
Building QA Team that matters for an Agile WorldMaurizio Mancini
Presentation from Quest 2015 - Covers building a new QA Team that matters, how to approach Agile Testing, and how to present the message to renovate your existing QA team for Agile.
Transforming Managers for an Agile Deployment - Agile Tour Montreal 2017Maurizio Mancini
Presentation at Agile Tour Montreal 2017 by Maurizio Mancini of Exempio. This presentation is an overview of what role software managers could play in an Agile world.
The document discusses how to reboot an agile team. It outlines six essential ingredients needed which include leadership, management style, vision, engagement, quality, and an agile coach. It then describes a five sprint process to reboot the team, with each sprint focusing on a different aspect of rebuilding the team such as understanding the current problems, breaking old habits, delivering working software, and becoming a self-organizing team. The document emphasizes that change is difficult and will involve managing emotions, and recommends using a modern management style and clear plan to guide the reboot of the agile team.
From Incremental & Iterative to Agile – What's the Right Process For Your Tea...Atlassian
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.
This document outlines a method for rebooting an agile team in 5 sprints. It discusses assessing the current state using a survey across 5 dimensions. Sprint 1 focuses on understanding the current problems. Sprint 2 aims to break the status quo and motivate change. Sprint 3 has the team experience pain while implementing changes. Sprint 4 has the team cross the edge and collaborate better. Sprint 5 removes training wheels to create a high performing, self-organized agile team. The method emphasizes the importance of leadership, vision, engagement and quality from the start. It also notes that emotions are part of any change process and should be managed well.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
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.
This document discusses how to address scaling agile needs on JIRA using SAFe (Scaled Agile Framework). It introduces cPrime as a SAFe and Agile training partner. It provides an overview of SAFe concepts like portfolio, program and team levels. It describes how business and architectural epics flow through the system from identification to implementation. It shows how epics can be allocated to Agile release trains and decomposed into features. Finally, it discusses investment themes and some JIRA addons for supporting SAFe.
The document discusses the Scaled Agile Framework (SAFe) for implementing agile practices in complex enterprise projects. It presents SAFe as an option for organizations that have multiple Scrum teams or one team with independent threads. The core values and principles of SAFe are described, including the release train, program increment planning, and that it focuses on Lean-Agile leadership. Some limitations are that SAFe requires Scrum practices within teams and training for both teams and management to understand and apply the framework effectively.
This document discusses why the author's organization transitioned from Scrum to ScrumBan. Some key problems with Scrum included specialized skill sets across distributed teams leading to handoffs between roles. ScrumBan combined elements of Scrum, like time boxing, with Kanban's focus on workflow and limiting work in progress. After transitioning, benefits included improved team morale and velocity while challenges included more complex release planning and measuring velocity.
Agile testing focuses on repeatable quality and efficiency through iterative and incremental development. Testers test each small increment of coding as soon as it is finished, ensuring programmers never get ahead of testers. True agile teams deliver working software frequently in short iterations rather than long delays, with testing done continuously throughout development rather than in separate phases at the end.
This document is an introduction to the Cynefin framework presented by Hosny Ashry. The presentation agenda includes a history of agile, why agile is useful, an explanation of the Cynefin framework, and a question and answer section. The history of agile stretches from 1986 to the Agile Manifesto in 2001. The Cynefin framework categorizes problems as obvious, complicated, complex, or chaotic and prescribes different approaches to problem-solving in each domain.
The Scaled Agile Framework (SAFe) has a special event that is held for every Program Increment (5 sprints-ish). This is a large scale, collaborative event including everyone from the Agile Release Train (50 people plus). This workshop will be a highly interactive event where all participants will be involved in one of many teams collaborating together to plan a single Program Increment for a single product.
The schedule will roughly contain:
Overview of SAFe Program Increment Planning
(Fictional) Business Context
Product / Solution Vision
Architecture Vision And Development Practices
Planning Session 1
Draft Plan Review
Planning Session 2
Final Plan Review
Risk ROAMing
Confidence Vote
Retrospective
This webinar discussed how a company called AcademicText.com transitioned from early Scrum adoption at the team level to implementing the Scaled Agile Framework (SAFe) across multiple teams. It began with Scrum training and using Jira for individual teams. Issues with coordination and dependencies between teams led to adopting SAFe. Key aspects discussed included:
- Aligning teams into Agile Release Trains (ARTs) organized by value streams
- Planning at the program level using a portfolio backlog, epics, and features
- Conducting SAFe release planning meetings over two days to develop the program increment plan
- Tracking progress through metrics like feature completeness and release burndowns
- Managing the
This document provides contact information for Richard Cheng, an agile trainer and coach who has experience leading agile transformations in government and commercial organizations, and lists his credentials including certifications in Scrum, SAFe, LeSS, and project management from organizations like PMI, Scrum Alliance, and Agile Alliance. It also includes his email, phone number, LinkedIn profile, and Twitter handle to facilitate contacting him.
Group hug - Implementing Agile Across Multiple TeamsRichard Cheng
Richard Cheng is an Agile trainer and coach who works for Excella Consulting. He provides training on Agile frameworks like Scrum, Kanban, and LeSS. Excella Consulting offers various Agile training courses and helps organizations implement Agile solutions through coaching, training, assessments, and adoption support. The presentation discusses organizing teams around products versus projects, managing dependencies between teams, and scaling Agile through frameworks like SAFe, LeSS, and DAD.
10 Questions For Your Scrum Master InterviewDavid Bland
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.
Introduction to Scaled Agile Framework SAFeJosef Scherer
1. The document discusses the Scaled Agile Framework (SAFe), a framework for implementing agile practices in large organizations. It describes SAFe's roots in lean thinking and systems management.
2. SAFe is based on the concept of an "Agile Release Train" which coordinates multiple agile teams to deliver value through regular inspection and adaptation cycles. It aims to achieve speed, value and quality at scale through flow, cadence and synchronization.
3. The document outlines key SAFe roles like the Product Manager, Release Train Engineer, System Architect, and System Team which work together using SAFe principles and practices to continuously deliver working solutions.
Introduction to SAFe, the Scaled Agile Frameworksrondal
Sans doute vous identifiez vous dans une ou plusieurs des situations suivantes:
- plusieurs équipes Scrum travaillent dans votre entreprise, parfois sur un même projet ou des projets connexes
- la coordination entre équipes Scrum n'est pas optimale
- vous-même, ou certains stakeholders, ont besoin d'une vue plus long terme sur vos projets Agile, plus que "juste le prochain sprint"
- sur base du succès de Scrum dans votre entreprise, vous voulez allez plus loin et vous voulez rendre plus agile l'entièreté de votre entreprise
Si c'est le cas, venez découvrir le framework SAFe.
Après une présentation du framework et de ses fondements, vous serez en mesure de mieux le comprendre, et de voir ce qu'il peut apporter ou non à votre entreprise.
A common practice among teams in IT companies adopting the latest trends, Agile can be scaled to enterprise level once applied properly. In this Innovation Session, Maduri Senadheera from the Project Management team talks about the Agile mindset, the need for scaling and the benefits of a Scaled Agile Framework for better aligning business processes.
#IBMInterConnect - DCB-3094 Scaling Agile - Launching an Agile Release Train ...Reedy Feggins Jr
In this talk we discuss some of the best practices we have learned for successfully Launching an ART. We discuss how Rational Team Concert (#RTC) can be used to help coordinate the various team activities such as use story analysis, portfolio program and sprint planning, and communicating with the PPM, Agile program and team.
The presentation is from the 2015 #ibminterconnect Conference #feggreed2021
DCB-3094 Scaling Agile Launching a SAFe Agile Release Train using Rational Team Concert – Lesson Learned
This document discusses various aspects of agile practices from the perspective of an agile expert. It touches on topics like commitment to the team's success, iterative development, documentation, retrospectives, testing practices like defining test scenarios and metrics, and emphasizes having fun and working together to succeed as a team rather than as individuals.
Gumtree underwent a transformation from late 2015 to early 2018 to create a "one team" culture without separate dev and QA roles. They initially prepared by shifting mindsets to see quality as everyone's responsibility. They implemented a Gumtree Code Quality Academy to teach developers testing skills. By late 2017, there was no longer a separate "in testing" phase and engineers did both development and testing. As of early 2018, some teams no longer had dedicated QEs and quality engineers took on some development tasks, moving toward true one team collaboration.
The product owner and the scrum team. Can one person do this at scale?Derek Huether
Presented at IIBA Baltimore on March 11, 2014. The last 10 years of Agile have focused on the team. The next 10 years of Agile will focus on the enterprise. That said, should the Product Owner continue to be a single person or does it need to evolve as well? Let's cover the basics and then see how LeadingAgile has been successful at leveraging the Product Owner role at scale.
May 22 2014 how to scale agility in your enterpriseIsaac Hogue
The document outlines a process for successfully scaling agile in an enterprise. It discusses establishing an agile delivery structure based around product teams and establishing different teams for different roles. It then describes mapping out the journey through defining the roadmap, operational framework, and transforming incrementally through phases like establishing trust and predictability before reducing batch size. Finally, it discusses running an agile pilot with independent, entrepreneurial teams to introduce changes incrementally and measure improvements.
This document discusses how to address scaling agile needs on JIRA using SAFe (Scaled Agile Framework). It introduces cPrime as a SAFe and Agile training partner. It provides an overview of SAFe concepts like portfolio, program and team levels. It describes how business and architectural epics flow through the system from identification to implementation. It shows how epics can be allocated to Agile release trains and decomposed into features. Finally, it discusses investment themes and some JIRA addons for supporting SAFe.
The document discusses the Scaled Agile Framework (SAFe) for implementing agile practices in complex enterprise projects. It presents SAFe as an option for organizations that have multiple Scrum teams or one team with independent threads. The core values and principles of SAFe are described, including the release train, program increment planning, and that it focuses on Lean-Agile leadership. Some limitations are that SAFe requires Scrum practices within teams and training for both teams and management to understand and apply the framework effectively.
This document discusses why the author's organization transitioned from Scrum to ScrumBan. Some key problems with Scrum included specialized skill sets across distributed teams leading to handoffs between roles. ScrumBan combined elements of Scrum, like time boxing, with Kanban's focus on workflow and limiting work in progress. After transitioning, benefits included improved team morale and velocity while challenges included more complex release planning and measuring velocity.
Agile testing focuses on repeatable quality and efficiency through iterative and incremental development. Testers test each small increment of coding as soon as it is finished, ensuring programmers never get ahead of testers. True agile teams deliver working software frequently in short iterations rather than long delays, with testing done continuously throughout development rather than in separate phases at the end.
This document is an introduction to the Cynefin framework presented by Hosny Ashry. The presentation agenda includes a history of agile, why agile is useful, an explanation of the Cynefin framework, and a question and answer section. The history of agile stretches from 1986 to the Agile Manifesto in 2001. The Cynefin framework categorizes problems as obvious, complicated, complex, or chaotic and prescribes different approaches to problem-solving in each domain.
The Scaled Agile Framework (SAFe) has a special event that is held for every Program Increment (5 sprints-ish). This is a large scale, collaborative event including everyone from the Agile Release Train (50 people plus). This workshop will be a highly interactive event where all participants will be involved in one of many teams collaborating together to plan a single Program Increment for a single product.
The schedule will roughly contain:
Overview of SAFe Program Increment Planning
(Fictional) Business Context
Product / Solution Vision
Architecture Vision And Development Practices
Planning Session 1
Draft Plan Review
Planning Session 2
Final Plan Review
Risk ROAMing
Confidence Vote
Retrospective
This webinar discussed how a company called AcademicText.com transitioned from early Scrum adoption at the team level to implementing the Scaled Agile Framework (SAFe) across multiple teams. It began with Scrum training and using Jira for individual teams. Issues with coordination and dependencies between teams led to adopting SAFe. Key aspects discussed included:
- Aligning teams into Agile Release Trains (ARTs) organized by value streams
- Planning at the program level using a portfolio backlog, epics, and features
- Conducting SAFe release planning meetings over two days to develop the program increment plan
- Tracking progress through metrics like feature completeness and release burndowns
- Managing the
This document provides contact information for Richard Cheng, an agile trainer and coach who has experience leading agile transformations in government and commercial organizations, and lists his credentials including certifications in Scrum, SAFe, LeSS, and project management from organizations like PMI, Scrum Alliance, and Agile Alliance. It also includes his email, phone number, LinkedIn profile, and Twitter handle to facilitate contacting him.
Group hug - Implementing Agile Across Multiple TeamsRichard Cheng
Richard Cheng is an Agile trainer and coach who works for Excella Consulting. He provides training on Agile frameworks like Scrum, Kanban, and LeSS. Excella Consulting offers various Agile training courses and helps organizations implement Agile solutions through coaching, training, assessments, and adoption support. The presentation discusses organizing teams around products versus projects, managing dependencies between teams, and scaling Agile through frameworks like SAFe, LeSS, and DAD.
10 Questions For Your Scrum Master InterviewDavid Bland
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.
Introduction to Scaled Agile Framework SAFeJosef Scherer
1. The document discusses the Scaled Agile Framework (SAFe), a framework for implementing agile practices in large organizations. It describes SAFe's roots in lean thinking and systems management.
2. SAFe is based on the concept of an "Agile Release Train" which coordinates multiple agile teams to deliver value through regular inspection and adaptation cycles. It aims to achieve speed, value and quality at scale through flow, cadence and synchronization.
3. The document outlines key SAFe roles like the Product Manager, Release Train Engineer, System Architect, and System Team which work together using SAFe principles and practices to continuously deliver working solutions.
Introduction to SAFe, the Scaled Agile Frameworksrondal
Sans doute vous identifiez vous dans une ou plusieurs des situations suivantes:
- plusieurs équipes Scrum travaillent dans votre entreprise, parfois sur un même projet ou des projets connexes
- la coordination entre équipes Scrum n'est pas optimale
- vous-même, ou certains stakeholders, ont besoin d'une vue plus long terme sur vos projets Agile, plus que "juste le prochain sprint"
- sur base du succès de Scrum dans votre entreprise, vous voulez allez plus loin et vous voulez rendre plus agile l'entièreté de votre entreprise
Si c'est le cas, venez découvrir le framework SAFe.
Après une présentation du framework et de ses fondements, vous serez en mesure de mieux le comprendre, et de voir ce qu'il peut apporter ou non à votre entreprise.
A common practice among teams in IT companies adopting the latest trends, Agile can be scaled to enterprise level once applied properly. In this Innovation Session, Maduri Senadheera from the Project Management team talks about the Agile mindset, the need for scaling and the benefits of a Scaled Agile Framework for better aligning business processes.
#IBMInterConnect - DCB-3094 Scaling Agile - Launching an Agile Release Train ...Reedy Feggins Jr
In this talk we discuss some of the best practices we have learned for successfully Launching an ART. We discuss how Rational Team Concert (#RTC) can be used to help coordinate the various team activities such as use story analysis, portfolio program and sprint planning, and communicating with the PPM, Agile program and team.
The presentation is from the 2015 #ibminterconnect Conference #feggreed2021
DCB-3094 Scaling Agile Launching a SAFe Agile Release Train using Rational Team Concert – Lesson Learned
This document discusses various aspects of agile practices from the perspective of an agile expert. It touches on topics like commitment to the team's success, iterative development, documentation, retrospectives, testing practices like defining test scenarios and metrics, and emphasizes having fun and working together to succeed as a team rather than as individuals.
Gumtree underwent a transformation from late 2015 to early 2018 to create a "one team" culture without separate dev and QA roles. They initially prepared by shifting mindsets to see quality as everyone's responsibility. They implemented a Gumtree Code Quality Academy to teach developers testing skills. By late 2017, there was no longer a separate "in testing" phase and engineers did both development and testing. As of early 2018, some teams no longer had dedicated QEs and quality engineers took on some development tasks, moving toward true one team collaboration.
The product owner and the scrum team. Can one person do this at scale?Derek Huether
Presented at IIBA Baltimore on March 11, 2014. The last 10 years of Agile have focused on the team. The next 10 years of Agile will focus on the enterprise. That said, should the Product Owner continue to be a single person or does it need to evolve as well? Let's cover the basics and then see how LeadingAgile has been successful at leveraging the Product Owner role at scale.
May 22 2014 how to scale agility in your enterpriseIsaac Hogue
The document outlines a process for successfully scaling agile in an enterprise. It discusses establishing an agile delivery structure based around product teams and establishing different teams for different roles. It then describes mapping out the journey through defining the roadmap, operational framework, and transforming incrementally through phases like establishing trust and predictability before reducing batch size. Finally, it discusses running an agile pilot with independent, entrepreneurial teams to introduce changes incrementally and measure improvements.
How to Successfully Scale Agile in Your EnterpriseIsaac Hogue
In an enterprise environment that is not structured to adopt out-of-the-box Agile, it’s critical to adopt Agile to your enterprises business drivers, value structure and governance. While Agile methodologies can improve the predictability, quality, and time to market of your software delivery, they are not a silver bullet.
Why Agile Is Failing in Large Enterprises, And What You Can Do About ItMike Cottmeyer
Large companies often struggle to adopt agile practices in a meaningful way. This presentation will help you understand why you are struggling to adopt agile, and more importantly, what you can do about it.
This document provides an overview of Agile frameworks and methodologies. It begins with an introduction to Agile and its history. Key aspects covered include the Agile mindset, comparisons to waterfall methods, the Agile Manifesto and its four values and 12 principles. Specific methodologies like Scrum are then described in detail, including Scrum team roles, events, artifacts and definitions of done. The document concludes with examples of applying Agile through a case study.
How to scale agility in your enterpriseTimothy Wise
Presentation for Southern Fried Agile conference 10/23/2014 that outlines how to scale agility in an enterprise.
The conference is a one day'er in Raleigh NC.
Great Crowd :)
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
It was repeatedly observed that as the number of Scrum teams within an organization grew, two major issues emerged:
* The volume, speed, and quality of their output (working product) per team began to fall, due to issues such as cross-team dependencies, duplication of work, and communication overhead.
* The original management structure was ineffective for achieving business agility. Issues arose like competing priorities and the inability to quickly shift teams around to respond to dynamic market conditions.
In this presentation I will show you how to counteract these issues, using Scrum@Sclae framework for effectively coordinating multiple Scrum teams was clearly needed which would aim for the following:
* Linear scalability: A corresponding percentage increase in delivery of working product with an increase in the number of teams.
* Business agility: The ability to rapidly respond to change by adapting its initial stable configuration.
This document outlines a model for a sustainable agile transformation within an organization. It begins with an overview of agile basics and scaling agile approaches. It then discusses why agile transformations are difficult, focusing on achieving safety from different stakeholder perspectives. The model proposes defining an operational framework structured around teams, products, and services. It recommends introducing change incrementally, starting with independent pilot teams, and measuring improvement through coaching and assessment. The transformation aims to tie back to business drivers like predictability, quality, and early return on investment.
A comparative study of process templates in teamaminmesbahi
This document provides an overview of process templates in Team Foundation Server, including Agile, Scrum, and CMMI templates. It defines key terms related to application lifecycle management. The Scrum template supports tracking product backlog items and bugs, while the Agile template tracks user stories and bugs/tasks separately. The CMMI template supports formal processes and auditing. Risks of using the wrong template, poor team skills, and scope changes are discussed.
The document provides an overview and introduction to Scrum, an agile framework for project management. It discusses the key roles, artifacts, and events in Scrum like sprints, product backlog, daily standups, and retrospectives. It also outlines the benefits of Scrum for different stakeholders such as customers, leadership, and team members.
Scrum is an agile framework for managing projects, commonly used for software development. It utilizes empirical process control through short cycles of work called sprints, daily stand-up meetings, and artifacts like product backlogs and sprint backlogs. The scrum team consists of the product owner, scrum master, and development team. They participate in events like sprint planning, daily scrums, sprint reviews, and retrospectives. The goal is to frequently inspect work, adapt the process as needed, and transparently deliver working software increments within each sprint.
Scrum vs SAFe | Differences Between Scrum and Scaled Agile Framework | EdurekaEdureka!
YouTube Link: https://youtu.be/c2e0BchglOc
** Certified Scrum Master Training: https://www.edureka.co/certified-scrum-master-certification-training **
This Edureka PPT on "Scrum vs SAFe" video will help you understand the key differences between the two most popular frameworks Scrum and Scaled Agile Framework (SAFe). The topics discussed in this course are listed below:
What is Scrum?
What is SAFe?
Major Differences Between Scrum and SAFe
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
Overview on Agile, Scrum, Kanban, Extreme programming (XP) and Scaled Agile F...Hyder Baksh
Unlock the power of Agile methodologies with this concise overview. Delve into the core principles and practices of Agile, Scrum, Kanban, Extreme Programming (XP), and the Scaled Agile Framework (SAFe) in just a few slides.
Discover how Agile methodologies revolutionize project management, emphasizing adaptability, collaboration, and customer-centricity. Learn about Scrum's structured framework, Kanban's visualized workflow, XP's engineering practices, and SAFe's scalable enterprise implementation.
Explore the benefits and challenges each methodology brings, and gain insights into selecting the right approach for your projects. Real-world case studies offer a glimpse into successful Agile transformations. Join us to uncover the essentials of Agile methodologies in today's fast-paced business landscape
Scrum_Blr 11th meet up 13 dec-2014 - Introduction to SAFe - Nagesh_SharmaScrum Bangalore
The document provides an introduction to the Scaled Agile Framework (SAFe) for applying agile practices at an enterprise scale. It discusses challenges organizations face with scaling agile and how SAFe addresses these challenges through its three layers (Portfolio, Program, Team). SAFe draws from Scrum, Extreme Programming, Kanban, lean principles and flows to provide transparency, alignment and program execution capabilities. It emphasizes continuous delivery through Agile Release Trains, empowered self-organizing teams, and roles like the Product Owner and Release Train Engineer. An example case study shows how a financial services company rapidly adopted SAFe to deliver more value faster by aligning their portfolio and programs.
Scaling your agile implementation across multiple teams in large organizations is always a challenge.
In this webinar, Ragia and Asmaa shared their experiences about:
- Why scaling?
- Different scaling frameworks?
- SAFe configurations
- SAFe pros & cons
============== Follow us ==============
Website: http://xpdays.org
Linked In: https://www.linkedin.com/company/xpdays
Facebook: https://www.facebook.com/xpdaysorg
Twitter: https://twitter.com/xpdaysorg
#agile #scaling #xpdays #agilearena
This document provides an introduction to agile frameworks like Scrum, XP, Lean, and Kanban. It discusses agile principles like valuing individuals, collaboration, and responding to change. It describes Scrum roles, events, and tools like user stories, burn-down charts, and daily stand-ups. XP's emphasis on testing is covered. Lean principles like eliminating waste and building quality in are explained. Kanban concepts like pull systems and work-in-progress limits are also summarized. The document concludes with recommendations for certifications and further reading on agile methods.
The document discusses various frameworks for scaling agile development in large organizations. It introduces Disciplined Agile Delivery (DAD), the Scaling Agile Framework (SAFe), Agility Path, Continuous Improvement Framework (CIF), and Large Scale Scrum. DAD is described as a decision-oriented framework, while SAFe is presented as more prescriptive. The document emphasizes that principles are more important than practices and that adopting an agile mindset is key to successful scaling.
This document provides an overview and agenda for an Agile Foundation training session on Scrum, Kanban, and SAFe. The session will cover setting the context for Agile, the Agile Manifesto, Scrum basics, and keywords. It will also discuss Scrum Master certifications and provide a deep dive into Scrum fundamentals and an overview of SAFe. The session aims to be interactive with participation from attendees.
Similar to Agile at Scale - Agile Orlando Lightning Talk (20)
Facilitating distributed agile teams Lean Agile US 2019Mark Kilby
What are the 3 challenges you face facilitating distributed agile teams? This talk discusses those challenges and provide some solutions in 40min. I longer version is being developed to include exercises.
You Have To Say More There: Effective Communication in a Distributed Agile TeamMark Kilby
My Agile2018 experience report with Johanna Rothman on how we pair-write our book. We describe how we used the principles and practices of the book to work as a distributed agile team.
8 Elements of Successful Distributed Agile Teams SFTA ITPallooza Dec20180Mark Kilby
This document summarizes the 8 elements of successful distributed agile teams according to Mark Kilby. The 8 elements are: 1) Acceptable hours of overlap, 2) Transparency at all levels, 3) Culture of continuous improvement, 4) Pervasive communication, 5) Assume good intent, 6) Project rhythm, 7) Resilience, and 8) Default to collaboration. For each element, the document provides examples and questions to help teams implement and evaluate how well they demonstrate that element. The overall message is that focusing on these fundamental principles is more important for distributed team success than any specific practices or tools.
8 elements of successful distributed agile teams agile dc previewMark Kilby
As more and more software teams are distributed by choice or circumstances, is there hope that they can be agile? In this talk for AgileDC 2018, I describe 8 elements that (in the right combination) can lead to successful distributed agile teams.
Agile distributed teams oxymoron or optionMark Kilby
The document summarizes Mark Kilby's presentation on agile distributed teams. It discusses principles for successful distributed agile teams, including having overlapping work hours, pervasive communication, assuming good intent, establishing team rhythms, promoting adaptability and resilience, encouraging pervasive collaboration, focusing on continuous improvement, and transparency at all levels. It provides examples and tips for applying each principle and assessing a team's ability to work distributedly.
This presentation represents some of the early principles that Johanna Rothman and I are uncovering in our work with successful distributed agile software teams.
Do i trust what i can't see (orlando code camp 2017)Mark Kilby
This document discusses building trust among distributed teams. It provides exercises for identifying who team members trust and strategies for deepening trust. Remote team structures like satellites, nebulae, and clusters are described. Techniques for remote teams include back channels, buddy systems, and co-pilots. Building trust requires competence, honesty, and reliability from team members. Organizational characteristics like encouraging appreciation and openness can also foster trust through increased oxytocin levels.
Do i trust what i can't see? Successful distributed teams - LeanAgileUS 2017Mark Kilby
The document discusses building trust in distributed teams. It provides examples of how trust can be developed through competency, honesty, reliability, and building an environment where people feel psychologically safe. Specific techniques for remote teams include assigning "buddies" for remote workers and using chat channels to facilitate constant communication. Trust is presented as the foundation for successful agile collaboration and is an outcome of leaders who foster environments with achievable challenges, self-organization, transparency, and care for employees.
Communicating and collaborating how distributed teams can thrive - kilby-ho...Mark Kilby
This document discusses strategies for effective communication and collaboration in distributed teams. It begins by outlining the principles of agile methodology as they relate to distributed teams. It then describes three types of distributed team structures - satellite, cluster, and nebula. The document proposes several techniques for distributed teams, including assigning "buddies" for remote members, using backchannel communication like chat, and designating team members as "co-pilots" to facilitate coordination. It presents an exercise called the "marshmallow challenge" that guides teams through collaboratively building a structure and includes debrief questions. The document concludes by providing contact information for the authors.
Do i know you? Rapport on distributed teams - OCC 2016Mark Kilby
My talk for Orlando Code Camp 2016 on the importance of Rapport on Distributed teams and why it is more important that "trust building". Thanks to Jim Benson and Tonianne DeMaria Barry for the inspiration.
The document discusses strategies for implementing agile practices in fully distributed teams. It suggests that distributed agile is possible if teams establish overlapping collaboration times, use shared task boards and progress tracking, keep multiple communication channels open at all times, and intentionally build social connections despite working remotely. The key is applying agile principles like collaboration, communication, and community while working in a distributed manner.
This document discusses whether agile practices can be implemented in fully remote teams. It begins with background on Sonatype, an open source software company, and outlines how they have successfully implemented agile practices across distributed teams. The document then discusses benefits of remote work, principles for remote agile such as open communication channels and a shared task board. Practices like daily standups and retrospectives via video conferencing are presented. It concludes by questioning if remote agile works for every team and company.
Is your user group dying? The Agile Florida story (Agile2015)Mark Kilby
This is the story of how 3 agile user groups in Florida all died and then bounced back and eventually became a state-wide learning network! Also see the experience report at http://bit.ly/agileFLstory
July is Distributed Teams month for AgileBill's online agile study group. I was asked to share some of my techniques for facilitating distributed meeetings .. and it's not all about the tools! See what else is happening at http://www.meetup.com/agile3d in distributed online tools, teams and agile or check out my site at http://markkilby.com
Providing an overview of Sonatype's distributed agile approach. This was a 1 hour presentation at South Florida Agile Asociation's Agile Transformation Summit 2015.
Driving Value with Agile Teams (IIBA-AO event)Mark Kilby
The document discusses agile frameworks like Scrum and Kanban. It provides an overview of their key principles and concepts, such as visualizing workflow, limiting work-in-progress, and continuously improving. The document compares Scrum and Kanban, noting that Scrum is generally better for project teams with planned work and high estimation ability, while Kanban works better for sustaining teams with demand-driven work and varied capabilities. It concludes by emphasizing the importance of inspecting and adapting practices over time.
The document discusses working remotely in an agile environment. It provides background on the author and his experience with agile coaching. It examines how remote teams can still adhere to agile principles like frequent collaboration, delivering working software frequently, and reflecting and adjusting regularly. The document considers challenges of remote work like promoting face-to-face conversations and questions how teams can effectively work asynchronously and across distances.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
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.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
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.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
6. What is an Agile Team?
Product Owner
Analyst
Testers
Developers
Scrum
Master
7. Back to Basics - Why Teams Work
• 5-10 people
• Efficient communication
• All skills to deliver work
• Develop a culture and norms
• Know each others strengths
Product Owner
Analyst
Testers
Developers
Scrum
Master
8. Back to Basics - Why Teams Work
• 5-10 people
• Efficient communication
• All skills to deliver work
• Develop a culture and norms
• Know each others strengths
Results in:
• Predictable throughput
• Regular delivery
Product Owner
Analyst
Testers
Developers
Scrum
Master
14. Team
Product Teams – These teams integrate services
and write customer facing features. This is the
proto-typical Scrum team.
15. Team
Team
Product Teams – These teams integrate services
and write customer facing features. This is the
proto-typical Scrum team.
Services Teams – These teams support common
services across product lines. These teams
support the needs of the product teams.
16. Team
Team
Team
Programs Teams – These teams define
requirements, set technical direction, and
provide context and coordination.
Product Teams – These teams integrate services
and write customer facing features. This is the
proto-typical Scrum team.
Services Teams – These teams support common
services across product lines. These teams
support the needs of the product teams.
17. Team
Team
Team
Team
Portfolio Teams – These teams govern the
portfolio and make sure that work is moving
through the system.
Programs Teams – These teams define
requirements, set technical direction, and
provide context and coordination.
Product Teams – These teams integrate services
and write customer facing features. This is the
proto-typical Scrum team.
Services Teams – These teams support common
services across product lines. These teams
support the needs of the product teams.
30. Inspect and Adapt
Change Management
& Communication
Structure
GovernanceMetrics
Assessment
Targeted
Coaching
Measure
Improvement
Form Teams
Teach
Practices
Guide Culture
31. Mark Kilby
Enterprise Agile Coach
Mark@LeadingAgile.com
Mark@markkilby.com
@mkilby– twitter
http://markkilby.com
THANKS!
Questions?
Join us for
Lean Coffee
on Friday
Editor's Notes
Assume 15-30 seconds per slideI can do this talk in 6.5 min –Mark Kilby
Let’s just say, I’ve been doing this for a while …- Guided Agile adoptions at dozens of commercial & government organizations (including Fortune 20)>20 years in software - developer, architect, project manager, ScrumMaster, Product OwnerStarted agile coaching in 2003- co-founder of Agile Orlando and host of Lean Coffee Orlando
This is the question of scale: What do you do when you have more work than one team can execute to delivery timely value?
There are a number of frameworks currently available to answer this question (like SAFe and DAD) and some emerging frameworks.
There are a number of frameworks currently available to answer this question (like SAFe and DAD) and some emerging frameworks.
But to answer the question of scale, we need to go back to basics. Why do agile teams work?Here is a typical Scrum team. Why is this considered a successful structure?
But to answer the question, we need to
But to answer the question, we need to
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
The small team commits to stakeholders and each other to complete a small increment of work
Then demonstrate results
When we scale, we need different cross-functional teams for different jobs
- Guided Agile adoptions at dozens of commercial & government organizations (including Fortune 20)>20 years in software - developer, architect, project manager, ScrumMaster, Product OwnerStarted agile coaching in 2003- co-founder of Agile Orlando and host of Lean Coffee Orlando