More with LeSS - short intro
•
0 likes•831 views
This document provides an overview of Large Scale Scrum (LeSS). It introduces Elad Sofer, a certified LeSS trainer and agile coach with 20 years of software development experience. The document discusses that LeSS is a framework for scaling Scrum to multiple teams working on one product. It provides principles and guides for organizing multiple teams to work together efficiently using an approach like feature teams rather than individual Scrum teams. The document lists upcoming certified LeSS practitioner training courses in various locations.
Report
Share
Report
Share
Download to read offline
Recommended
Less intro workshop
The document discusses the principles of Taylorism and how they are outdated for modern business needs. It argues that only by utilizing the intelligence of all employees, not just executives, can a company survive increasingly complex business environments. Konosuke Matsushita asserts that Japanese companies have moved beyond the Taylor model and will be more successful than Western companies still adhering to outdated Taylorist principles that separate thinking from doing work.
How to make your daily stand-up more engaging
Do we really need the daily stand-up? And if yes, how can we make it more effective, engaging and fun?
Scrummaster Needed Desperately at 2016 Scrum 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.
Scrum Master: Role or Responsibility?
The document discusses the career path for Scrum Masters. It begins by defining the Scrum Master role and qualities of an excellent Scrum Master. It then addresses the debate around whether Scrum Master is a role or a career. The document proposes a 3-level career path for Scrum Masters, including levels for Scrum Master, Senior Scrum Master, and Agile Coach. It outlines the proposed responsibilities, experience, skills, and certifications needed to progress through each level. The goal is to clearly define expectations and provide a path for professional growth to position the Scrum Master job as a true career.
Scrum master basics
Day 1 from our Scrum master week, the material for the one-day training about discovering the basics of the Scrum master role
Berlin-agile-sap-delivery-scrumatscale-meetup
Scrum@Scale is a framework for scaling Scrum to address complex problems across networks of Scrum teams. It consists of Scrum teams operating consistently with the Scrum Guide. Scaling Scrum requires implementing a new operating model where the minimum viable bureaucracy coordinates teams. Key elements include: Executive Action Teams that eliminate impediments; daily Scrums of Scrums between teams; and scaling ceremonies up to thousands of people. Organizations assess where they are currently to identify improvement experiments towards the scaled framework.
How to Become an Indispensable Scrum Master
For those new to Agile there is often an assumption made that the Scrum Master and the Project Manager are the same role.This is absolutely not the case. The two roles are very different and they each fit into approaches to projects that are wildly different as Agile is a Value and Culture driven Project Management Methodology.
I try to address some of the misunderstandings of the Scrum Master Role
You can see some of Scrum Master internal training videos that I did in past.
https://www.youtube.com/my_videos?o=U
How to Become an Indispensable Scrum Master
Scaling Agile - LeSS Framework
Large organizations face challenges scaling agile scrum practices across many teams due to issues like siloed teams losing overall product focus, fixed release dates encouraging a mini-waterfall model, and treating agile adoption as a project with an end rather than continuous improvement. The Large-Scale Scrum (LeSS) framework addresses these problems by organizing teams around customer-centric requirement areas rather than functions, empowering cross-functional feature teams to be self-managed and co-located, and viewing agile adoption as a continuous journey of inspection and adaptation. LeSS scales scrum without adding layers or processes in a non-prescriptive manner focused on continuous learning.
Recommended
Less intro workshop
The document discusses the principles of Taylorism and how they are outdated for modern business needs. It argues that only by utilizing the intelligence of all employees, not just executives, can a company survive increasingly complex business environments. Konosuke Matsushita asserts that Japanese companies have moved beyond the Taylor model and will be more successful than Western companies still adhering to outdated Taylorist principles that separate thinking from doing work.
How to make your daily stand-up more engaging
Do we really need the daily stand-up? And if yes, how can we make it more effective, engaging and fun?
Scrummaster Needed Desperately at 2016 Scrum 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.
Scrum Master: Role or Responsibility?
The document discusses the career path for Scrum Masters. It begins by defining the Scrum Master role and qualities of an excellent Scrum Master. It then addresses the debate around whether Scrum Master is a role or a career. The document proposes a 3-level career path for Scrum Masters, including levels for Scrum Master, Senior Scrum Master, and Agile Coach. It outlines the proposed responsibilities, experience, skills, and certifications needed to progress through each level. The goal is to clearly define expectations and provide a path for professional growth to position the Scrum Master job as a true career.
Scrum master basics
Day 1 from our Scrum master week, the material for the one-day training about discovering the basics of the Scrum master role
Berlin-agile-sap-delivery-scrumatscale-meetup
Scrum@Scale is a framework for scaling Scrum to address complex problems across networks of Scrum teams. It consists of Scrum teams operating consistently with the Scrum Guide. Scaling Scrum requires implementing a new operating model where the minimum viable bureaucracy coordinates teams. Key elements include: Executive Action Teams that eliminate impediments; daily Scrums of Scrums between teams; and scaling ceremonies up to thousands of people. Organizations assess where they are currently to identify improvement experiments towards the scaled framework.
How to Become an Indispensable Scrum Master
For those new to Agile there is often an assumption made that the Scrum Master and the Project Manager are the same role.This is absolutely not the case. The two roles are very different and they each fit into approaches to projects that are wildly different as Agile is a Value and Culture driven Project Management Methodology.
I try to address some of the misunderstandings of the Scrum Master Role
You can see some of Scrum Master internal training videos that I did in past.
https://www.youtube.com/my_videos?o=U
How to Become an Indispensable Scrum Master
Scaling Agile - LeSS Framework
Large organizations face challenges scaling agile scrum practices across many teams due to issues like siloed teams losing overall product focus, fixed release dates encouraging a mini-waterfall model, and treating agile adoption as a project with an end rather than continuous improvement. The Large-Scale Scrum (LeSS) framework addresses these problems by organizing teams around customer-centric requirement areas rather than functions, empowering cross-functional feature teams to be self-managed and co-located, and viewing agile adoption as a continuous journey of inspection and adaptation. LeSS scales scrum without adding layers or processes in a non-prescriptive manner focused on continuous learning.
Practical Scrum course day 1
This document outlines an agenda for a Scrum workshop conducted by Practical Agile. The workshop is led by Ilan Kirschenbaum, an agile coach and co-founder of Practical Agile. The agenda covers introductions, an overview of Scrum and its history, the roles of a Scrum Master and Scrum team, reducing waste, and engineering practices. Scrum is presented as an empirical, iterative framework for self-organizing teams to deliver working software frequently through a sprint cycle of approximately 30 days.
Fire Your Scrum Master
My keynote at AgileNCR2016 at Gurgaon, 9 Dec. In this talk, I explore the very basis of the role of scrum master, what happens when that jobs is done, and what should you do next?
Comments, objections and feedback welcome!
It's More complex than you think
The slides from my Agile Testing Days 2016 conference workshop about complexity and system modeling.
The Agile Hammer
The document summarizes the author's experience with adopting Agile practices within her team. Initially, the team struggled with a partially ad-hoc Agile implementation that resulted in slow, poor quality work and budget overruns. Over time, as the team recomposed their practices to more closely align with Agile principles such as short stand-up meetings, estimating in story points, and continuous flow, they saw improvements in quality, time to market, and flexibility. Business stakeholders also reported benefits like increased visibility into work being done and opportunities to provide feedback. The author concludes by reflecting on further refinements to Agile practices in her current role, supported by a dedicated Agile center of excellence, external coaching, and executive sponsorship.
How to be a great scrum master
The document outlines the responsibilities of a Scrum Master which include removing blocks for the team, acting as an unbreakable buffer, championing Agile practices, being the chief connector to solve issues, providing frequent feedback, and building individual ownership without acting as a team leader. It notes that the Scrum Master role can vary in visibility from almost invisible on small dedicated teams to highly visible and busy on larger teams with more challenges.
Three steps to transform from a waterfall to an Agile org
A long long time ago, in a galaxy far far away... before the LeSS framework existed as a clearly defined framework, a few chosen Agile coaches were trying to restore agility to the galaxy by introducing the organization to the concepts that were later named as the LeSS framework.
This is a story about one Agile coach trying to help a product group in a security company to improve their business success by optimizing the whole rather than parts, by eliminating silos and getting rid of the fore waterfall forces of the dark side
Roadmap to Scrum Master ( CSM )
Scrum is an agile framework for managing product development. It involves short development iterations called sprints (typically 2-4 weeks) where self-organizing cross-functional teams work to deliver a potentially shippable product increment. Key aspects of scrum include product backlogs to define features, sprint planning meetings, daily stand-up meetings, sprint reviews, and retrospectives. Scrum aims to improve transparency, inspection, and adaptation and enables rapid delivery of valuable software through an empirical process that promotes continuous improvement.
Leading agile teams - Advanced Scrum Master
This document provides an overview of an advanced scrum master workshop. It discusses the role and responsibilities of a scrum master, facilitation of scrum ceremonies like the daily scrum and retrospectives, navigating conflict, and growing as a leader. The scrum master is responsible for ensuring the team follows scrum principles and practices, removing impediments, and helping those outside the team understand how to best interact with the scrum process. Effective facilitation of meetings and retrospectives requires setting guidelines, using the right activities, and focusing discussions on problem-solving and continuous improvement.
Short Intro to Agile-Scrum for NCA-CPA
I was invited to give this talk to the NC Association of CPAs.
A short introduction to Scrum from different perspectives that a CPA might have.
Scrum team evolution
What are the characteristics of a good Scrum Team? Are you willing to be a Product Owner or Scrum Master? Are you wondering about the maturity of your development team? This presentation will give you insights about how the evolution of the development team, scrum master, and the product owner.
What does a Scrum Master do, or should do, all day?
A Scrum Master facilitates the Scrum process, creates rhythm and sets expectations for projects and team members. They facilitate daily stand-ups and meetings, enhance communication, and act as an approachable coach through 1:1 meetings and active listening. Scrum Masters also train teams, products, and the organization on Agile practices.
Advanced Scrum master workshop
This document provides information about an advanced scrum master workshop presented by Elad Sofer and Ilan Kirschenbaum of Practical Agile. It includes topics that will be covered such as the responsibilities of a scrum master, facilitating effective meetings and retrospectives, dealing with conflict, and growing as a leader. A video on effective feedback and an exercise on giving and receiving feedback are also outlined. The workshop aims to help participants become more skilled scrum masters.
Full-Time Dedicated ScrumMaster
This document discusses the responsibilities and role of a full-time ScrumMaster. It outlines basic ScrumMaster responsibilities according to the Scrum Guide including promoting Scrum practices, helping others understand Scrum theory, and serving the Product Owner, Development Team, and Organization. The document also lists possible benefits of a full-time ScrumMaster such as focus, dealing with root causes, and happy teams and stakeholders. Challenges include issues with time and money. It emphasizes that a forgotten responsibility is service to the organization, which includes leading Scrum adoption, planning implementations, and causing change that increases productivity.
Kaizen in Action for Regional Scrum Gathering Tokyo 2017
Presentation slides for "Kaizen in Action" session in Regional Scrum Gathering on Jan 12th and 13th, 2017.
#RGST2017
Agile Transformations that Stick
The document provides guidance on making agile transformations stick within organizations. It emphasizes focusing on values, principles and behaviors over mechanics. Key steps include: getting leaders aligned on desired outcomes; training everyone in agile; allowing teams to start without too much tweaking; and watching for danger signs like too much process or role confusion and addressing them. The overall message is that genuine culture change takes time and organizations should fail fast, adapt often, and amplify successes.
Help the Scrum Master IS the Impediment
The change in mindset necessary to become a servant leader is incredibly hard for a scrum master who comes from command and control background. As a newly minted Professional Scrum Master (PSM I), I returned to my team excited and ready to get underway with a scrum adoption. Unfortunately, I had not fully grasped the concept of servant leadership. Instead of being a change agent, I was an impediment.
My own cautionary tale is unfortunately a common one. Well meaning people with 2 day certifications can do a lot of damage to a new scrum team. Attendees will learn about the difficulties of becoming a scrum master, how scrum team members need to embrace the scrum values to promote healthy team practices, and that even certified scrum masters can lose their way.
Scrum Master Lessons from my 4 Year Old Son
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
Introduction to LeSS - Large Scale Scrum
This slide deck was used for a two hour presentation at the Nov 15 session of LeSS-TO Large Scale Scrum Toronto Meetup group
Scrum master checklist
The document discusses the role and responsibilities of a Scrum Master. It describes how the Scrum Master facilitates the Scrum process and ceremonies like daily stand-ups, sprint planning and retrospectives. The Scrum Master also helps resolve impediments, enables self-organization of the team and protects the team from external interference. Key responsibilities include enforcing timeboxes, maintaining artifacts and metrics, and guiding the team on Agile best practices. The document provides checklists and guidelines for Scrum Masters to effectively perform their duties.
Get rid of boring retrospectives
The document provides tips and structures for making retrospectives more engaging and less boring. It suggests using timeboxing, avoiding judgement, and planning activities in advance. Various retrospective game structures are presented, including using starfish, grouping, dot voting, and others to gather data, generate insights, decide on actions, and close the retrospective. The goal is to facilitate learning through fun retrospective activities rather than traditional retrospective formats.
Introduction to Agile & scrum
The document discusses key concepts in Agile and Scrum project management frameworks. It outlines some common misconceptions about Agile, describes Scrum roles and ceremonies like sprint planning and review meetings, and emphasizes that adopting Scrum requires changes to team dynamics, skills, and work habits.
Scrum intro ILTechTalks
The document provides details on Elad Sofer's background and credentials as an Agile Coach, including his email, blog, and Twitter account. It then lists requirements, analysis, design, implementation, testing, acceptance, and delivery as sequential steps in the waterfall development model. The waterfall model is described as originating from manufacturing and construction and being presented by Winston W. Royce in 1970 as a flawed model.
More Related Content
What's hot
Practical Scrum course day 1
This document outlines an agenda for a Scrum workshop conducted by Practical Agile. The workshop is led by Ilan Kirschenbaum, an agile coach and co-founder of Practical Agile. The agenda covers introductions, an overview of Scrum and its history, the roles of a Scrum Master and Scrum team, reducing waste, and engineering practices. Scrum is presented as an empirical, iterative framework for self-organizing teams to deliver working software frequently through a sprint cycle of approximately 30 days.
Fire Your Scrum Master
My keynote at AgileNCR2016 at Gurgaon, 9 Dec. In this talk, I explore the very basis of the role of scrum master, what happens when that jobs is done, and what should you do next?
Comments, objections and feedback welcome!
It's More complex than you think
The slides from my Agile Testing Days 2016 conference workshop about complexity and system modeling.
The Agile Hammer
The document summarizes the author's experience with adopting Agile practices within her team. Initially, the team struggled with a partially ad-hoc Agile implementation that resulted in slow, poor quality work and budget overruns. Over time, as the team recomposed their practices to more closely align with Agile principles such as short stand-up meetings, estimating in story points, and continuous flow, they saw improvements in quality, time to market, and flexibility. Business stakeholders also reported benefits like increased visibility into work being done and opportunities to provide feedback. The author concludes by reflecting on further refinements to Agile practices in her current role, supported by a dedicated Agile center of excellence, external coaching, and executive sponsorship.
How to be a great scrum master
The document outlines the responsibilities of a Scrum Master which include removing blocks for the team, acting as an unbreakable buffer, championing Agile practices, being the chief connector to solve issues, providing frequent feedback, and building individual ownership without acting as a team leader. It notes that the Scrum Master role can vary in visibility from almost invisible on small dedicated teams to highly visible and busy on larger teams with more challenges.
Three steps to transform from a waterfall to an Agile org
A long long time ago, in a galaxy far far away... before the LeSS framework existed as a clearly defined framework, a few chosen Agile coaches were trying to restore agility to the galaxy by introducing the organization to the concepts that were later named as the LeSS framework.
This is a story about one Agile coach trying to help a product group in a security company to improve their business success by optimizing the whole rather than parts, by eliminating silos and getting rid of the fore waterfall forces of the dark side
Roadmap to Scrum Master ( CSM )
Scrum is an agile framework for managing product development. It involves short development iterations called sprints (typically 2-4 weeks) where self-organizing cross-functional teams work to deliver a potentially shippable product increment. Key aspects of scrum include product backlogs to define features, sprint planning meetings, daily stand-up meetings, sprint reviews, and retrospectives. Scrum aims to improve transparency, inspection, and adaptation and enables rapid delivery of valuable software through an empirical process that promotes continuous improvement.
Leading agile teams - Advanced Scrum Master
This document provides an overview of an advanced scrum master workshop. It discusses the role and responsibilities of a scrum master, facilitation of scrum ceremonies like the daily scrum and retrospectives, navigating conflict, and growing as a leader. The scrum master is responsible for ensuring the team follows scrum principles and practices, removing impediments, and helping those outside the team understand how to best interact with the scrum process. Effective facilitation of meetings and retrospectives requires setting guidelines, using the right activities, and focusing discussions on problem-solving and continuous improvement.
Short Intro to Agile-Scrum for NCA-CPA
I was invited to give this talk to the NC Association of CPAs.
A short introduction to Scrum from different perspectives that a CPA might have.
Scrum team evolution
What are the characteristics of a good Scrum Team? Are you willing to be a Product Owner or Scrum Master? Are you wondering about the maturity of your development team? This presentation will give you insights about how the evolution of the development team, scrum master, and the product owner.
What does a Scrum Master do, or should do, all day?
A Scrum Master facilitates the Scrum process, creates rhythm and sets expectations for projects and team members. They facilitate daily stand-ups and meetings, enhance communication, and act as an approachable coach through 1:1 meetings and active listening. Scrum Masters also train teams, products, and the organization on Agile practices.
Advanced Scrum master workshop
This document provides information about an advanced scrum master workshop presented by Elad Sofer and Ilan Kirschenbaum of Practical Agile. It includes topics that will be covered such as the responsibilities of a scrum master, facilitating effective meetings and retrospectives, dealing with conflict, and growing as a leader. A video on effective feedback and an exercise on giving and receiving feedback are also outlined. The workshop aims to help participants become more skilled scrum masters.
Full-Time Dedicated ScrumMaster
This document discusses the responsibilities and role of a full-time ScrumMaster. It outlines basic ScrumMaster responsibilities according to the Scrum Guide including promoting Scrum practices, helping others understand Scrum theory, and serving the Product Owner, Development Team, and Organization. The document also lists possible benefits of a full-time ScrumMaster such as focus, dealing with root causes, and happy teams and stakeholders. Challenges include issues with time and money. It emphasizes that a forgotten responsibility is service to the organization, which includes leading Scrum adoption, planning implementations, and causing change that increases productivity.
Kaizen in Action for Regional Scrum Gathering Tokyo 2017
Presentation slides for "Kaizen in Action" session in Regional Scrum Gathering on Jan 12th and 13th, 2017.
#RGST2017
Agile Transformations that Stick
The document provides guidance on making agile transformations stick within organizations. It emphasizes focusing on values, principles and behaviors over mechanics. Key steps include: getting leaders aligned on desired outcomes; training everyone in agile; allowing teams to start without too much tweaking; and watching for danger signs like too much process or role confusion and addressing them. The overall message is that genuine culture change takes time and organizations should fail fast, adapt often, and amplify successes.
Help the Scrum Master IS the Impediment
The change in mindset necessary to become a servant leader is incredibly hard for a scrum master who comes from command and control background. As a newly minted Professional Scrum Master (PSM I), I returned to my team excited and ready to get underway with a scrum adoption. Unfortunately, I had not fully grasped the concept of servant leadership. Instead of being a change agent, I was an impediment.
My own cautionary tale is unfortunately a common one. Well meaning people with 2 day certifications can do a lot of damage to a new scrum team. Attendees will learn about the difficulties of becoming a scrum master, how scrum team members need to embrace the scrum values to promote healthy team practices, and that even certified scrum masters can lose their way.
Scrum Master Lessons from my 4 Year Old Son
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
Introduction to LeSS - Large Scale Scrum
This slide deck was used for a two hour presentation at the Nov 15 session of LeSS-TO Large Scale Scrum Toronto Meetup group
Scrum master checklist
The document discusses the role and responsibilities of a Scrum Master. It describes how the Scrum Master facilitates the Scrum process and ceremonies like daily stand-ups, sprint planning and retrospectives. The Scrum Master also helps resolve impediments, enables self-organization of the team and protects the team from external interference. Key responsibilities include enforcing timeboxes, maintaining artifacts and metrics, and guiding the team on Agile best practices. The document provides checklists and guidelines for Scrum Masters to effectively perform their duties.
What's hot (19)
Three steps to transform from a waterfall to an Agile org
Three steps to transform from a waterfall to an Agile org
What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day?
Kaizen in Action for Regional Scrum Gathering Tokyo 2017
Kaizen in Action for Regional Scrum Gathering Tokyo 2017
Viewers also liked
Get rid of boring retrospectives
The document provides tips and structures for making retrospectives more engaging and less boring. It suggests using timeboxing, avoiding judgement, and planning activities in advance. Various retrospective game structures are presented, including using starfish, grouping, dot voting, and others to gather data, generate insights, decide on actions, and close the retrospective. The goal is to facilitate learning through fun retrospective activities rather than traditional retrospective formats.
Introduction to Agile & scrum
The document discusses key concepts in Agile and Scrum project management frameworks. It outlines some common misconceptions about Agile, describes Scrum roles and ceremonies like sprint planning and review meetings, and emphasizes that adopting Scrum requires changes to team dynamics, skills, and work habits.
Scrum intro ILTechTalks
The document provides details on Elad Sofer's background and credentials as an Agile Coach, including his email, blog, and Twitter account. It then lists requirements, analysis, design, implementation, testing, acceptance, and delivery as sequential steps in the waterfall development model. The waterfall model is described as originating from manufacturing and construction and being presented by Winston W. Royce in 1970 as a flawed model.
Why move to Scrum ?
This presentation provides reasons for switching from a waterfall development model to Scrum. The waterfall model is not well-suited to handle changing requirements, produces many unused features due to its lack of flexibility, and reduces chances of project success due to its relatively long length. In contrast, Scrum is designed to handle frequent changes, prioritize and build only high-value features through quick feedback cycles, and takes a more iterative approach to development in shorter cycles. Scrum also aims to improve quality, visibility, and reduce costs through its emphasis on these factors. Finally, the document references surveys that show benefits to quality, customer satisfaction, success rates, and productivity realized by organizations after adopting Agile practices like Scrum.
Domain specific languages
Quick introductory to Domain Specific Languages session done at the Software Craftsmanship in Israel meetup
Leading agile teams
This document summarizes a presentation about leading teams in the Age of Agile. The presentation covers several topics:
1. The biggest problems leaders face and how leadership is grown, not born.
2. What responsibilities leaders have to their personal life, projects, teams, communication, and more.
3. Models of leadership, feedback, and dealing with conflicts within teams.
4. Exercises are provided to help participants reflect on their leadership styles and how to have difficult conversations to improve team dynamics.
Feedback - The Secret ingredient of success
The document discusses the differences between home cooks and professional chefs, as well as differences in feedback loops between agile software development processes and traditional processes. It notes that chefs receive constant feedback while cooking that allows them to adjust their dish, unlike home cooks who just follow recipes without tasting. For software development, it describes how agile processes have much shorter and more frequent feedback loops at various levels compared to traditional processes, such as having code reviews that take minutes instead of days and unit testing that provides feedback in minutes rather than weeks. Keeping feedback loops short, frequent, and at multiple levels is key to success with agile methods.
Introduction to Agile & scrum
Introduction to Agile & scrum, but a bit from an HR perspective.
This presentation was given at "JobInfo" as some background material for a better understanding of recruitment in an agile world.
Infrastructure code in Agile software development
Infrastructure code refers to software layers with APIs that are used by multiple users and teams for different purposes. It supports principles like DRY and helps manage shared resources. Traditionally, infrastructure code is never truly complete, becomes too large to manage effectively, and creates bottlenecks. However, taking an agile approach by having multiple feature teams own infrastructure and developing it iteratively reduces bottlenecks and risk while increasing flexibility and business understanding within teams. This requires effort to implement cross-team communication but yields business benefits.
Scrum intro
This document provides an overview of an introductory training session on Scrum. It describes the various activities and sections of the training, including an introduction by the trainer, exercises and games to illustrate Scrum concepts, breakout groups to form teams, and discussions of Scrum roles, ceremonies, and artifacts. The training aims to explain the basics of the Scrum framework in an interactive way using examples, activities, and visuals to engage participants.
Scrum training day 1
This document provides an overview of an introduction to Scrum training session. It includes an agenda with topics like introduction, games and exercises, parking lot for questions, and forming teams. There is also background on the trainer, Elad Sofer, including his experience and roles. Key aspects of Scrum like the roles of Product Owner, Scrum Master and Development Team are defined. Concepts like the product backlog, user stories, story points, planning poker and backlog refinement are introduced and explained. Exercises are included to help illustrate estimating and splitting stories.
Scrum training day 2
This document contains materials from a workshop on scrum mastering and agile coaching. It includes definitions of key roles like scrum master and product owner. It discusses scrum master responsibilities and challenges like removing impediments and helping the team grow. It provides guidance on facilitating meetings, retrospectives, and managing conflicts. Interactive exercises explore giving and receiving feedback, navigating group conflicts, and leadership growth.
Lean sw development il tech-talks
The document summarizes the origins and principles of Lean manufacturing as derived from Toyota's production system. It describes a 1990 study showing Japanese automakers had 50% higher productivity and quality with 40% faster development times using Lean principles. Lean focuses on eliminating waste to optimize value delivery. The core ideas are only producing what is needed when it is needed, stopping work to fix problems, and empowering employees.
Agile estimation and planning
This document discusses agile estimation and planning techniques. It recommends estimating tasks relatively using story points rather than absolute time estimates. Planning poker, where teams privately estimate tasks and then discuss estimates, is presented as an effective technique. Prioritizing a backlog by value, risk, and estimate allows teams to focus on the most important work. Iterative planning within sprints and tracking progress via burn down charts increases transparency.
Practical-Agile Product owner workshop
This is the presentation from the product owner workshop. Feel free to share and use but please link to the original.
Viewers also liked (15)
Similar to More with LeSS - short intro
Large Scale Scrum: More with LeSS
Here are some key points to discuss regarding the change implications of moving from component teams to feature teams:
- Ex-functional managers and component managers may feel a loss of control and identity as their direct reports are redistributed to cross-functional teams. Their role needs to transition from managers to coaches/advisors.
- Specialists may feel anxious about broadening their skills beyond a single specialty. Teams will need to support specialists to gradually expand their capabilities over time.
- Communication patterns will change significantly. Component teams had well-defined interfaces, but feature teams will need to collaborate more openly. New norms around collaboration will need to be established.
- Technical decisions may become more decentralized. Feature teams will need guidance on balancing
Agile lean workshop for managers & exec leadership
This document summarizes an agile workshop for managers and executive leadership at Cisco. The workshop covers several topics:
- Defining the role of an agile functional manager and transitioning existing managers to this role.
- Discussing whether the concept of "servant leadership" is too idealistic and assessing different leadership styles.
- Explaining the value of having a dedicated team room to facilitate transparency, collaboration and trust within agile teams.
The workshop provides guidance to leadership on adopting an inside-out approach to cultural change, emphasizing assessing organizational culture before implementing new processes or structures. Overall, the document outlines an agenda to help management explore how to effectively lead teams using agile and lean
Scaling agility or descaling organization
This document discusses various approaches to scaling agility in large organizations, including Scrum, SAFe, LeSS, and Spotify's model. It describes the challenges of implementing Scrum at both the single team and multi-team levels. SAFe and LeSS propose frameworks for multiple aligned teams delivering value through features and benefits. Spotify uses squads, tribes, chapters and guilds to structure autonomous teams while maintaining alignment. Scaling agility is difficult and requires addressing organizational structure and culture.
Strategic Org Design with Org Topologies™
Org Design is a core skill to be mastered by management for any successful org change.
Org Topologies™ in its essence is a two-dimensional space with 16 distinctive boxes - atomic organizational archetypes. That space helps you to plot your current operating model by positioning individuals, departments, and teams on the map. This will give a profound understanding of the performance of your value-creating organizational ecosystem.
Enterprise agile Framework
Agenda:
Agile Definition
Agile Adoption
How To Scale
Enterprise Agile Frameworks
Scrum@Scale
LeSS
Nexus
KAA 2017 - Comparing Scaling Frameworks: LeSS & SAFe
Scaling Agile is easily misunderstood. Scaling is the term we often hear used to describe using Agile methods with large enterprises. Larger enterprises often deal with bigger and more complex problems than small ones. They have more employees, subcontracting companies, different business units, more processes and a strong culture that defines how things are done. At the same time, they need to be able to deliver results in an ever-changing business environment. They need to be Agile but the bigger the company, the bigger the challenges are for scaling Agile.
Scaling frameworks available in the market today are maturing quickly and provide a variety of choices. Like the Agile Manifesto, these frameworks are based on principles, and they vary widely in the specificity of the recommended approach.
In this session, we will compare how two scaling frameworks, LeSS and SAFe, address the challenges of agility at scale. We will talk about how these two frameworks align, coordinate, and manage dependencies across multiple teams to maintain consistency and agility at scale.
Agile, Lean, and In Between
Many people think of lean, agile, and lean startup as separate processes. In this presentation we'll talk about how they actually evolved from each other, share the same mindset, and can be combined to be more powerful.
Agile Leaders and Agile Managers
The document discusses the role of managers in agile organizations. It suggests that managers focus on empowering self-organizing teams, removing impediments, teaching problem-solving skills, and stimulating continuous improvement and growth across the organization. Effective agile leadership involves roles like servant leadership, host leadership, and defining one's scope of influence at the relationship and organizational levels. Managers should invest in learning through coaching, mentoring, and developing learning organizations with principles like systems thinking and shared vision.
Heitger Consulting ZFU_Value Driver Leadership
The document outlines an approach to strategic leadership development. It discusses the need for a new focus on "orchestration" due to increased complexity and interactions. It proposes an innovative approach that addresses both individual leadership development and organizational leadership development. An example of a corporate leadership development program is provided, highlighting its goals, modules, and key success factors. A framework for leadership development involving various players and experiences is also presented.
Teaching pointy haired bosses to be agile enablers
Are managers hindering your Agile transition? Does it seem like things would be better if the managers all left?
Most managers are intelligent people who have built their careers and fed their families with their current knowledge and experience. During an agile transformation, we need them on-board. Managers know their present situation better than anyone else. They also have inside knowledge about the corporate systems and culture that agile coaches need in order to be successful.
But in some cases the manager does not understand agile. In extreme cases, they can become an impediment to an agile transformation moving forward. How can you get these managers back on your side, supporting the agile transformation?
Agile coaches should start with working to understand what the world looks like through the eyes of these managers. To facilitate this understanding, I discuss re-purposing the concept of product user personas to create manager personas that explore the issues, reservations, hold-ups and concerns that are keeping the manager from supporting an agile transformation.
With this new understanding, agile coaches can develop ways to demonstrate to managers why the agile approach is better, where management fit in the larger picture, and how management also benefits from the changes in the way the team delivers value back to the organization. These insights show managers where they can improve agile projects, how they can add value in a newly transformed organization, and how agile coaches can guide management without alienating them during an agile transformation.
Organization structure @ flat army symposium nov2014
The document discusses organizational structure and principles for designing an effective structure. It provides examples of structures that focus on continuous improvement, breaking down barriers, and closer relationships with customers. The key factors to consider in structure design are strategies, services, processes, roles, skills, and rewards. Changing an organization's structure is a complex process that requires clear communication and training to help staff understand and transition to the new structure.
Organization structure @ Building an Engaged Flat Army in the Library Symposi...
The document discusses organizational structure and principles for designing an effective structure. It provides examples of structures that focus on continuous improvement, breaking down barriers, and closer relationships with customers. The key factors to consider in structure design are strategies, services, processes, roles, skills, and rewards. Changing an organization's structure is a complex process that requires clear communication and training to help staff understand and transition to the new structure.
9 dev ops mark smalley & lex scholten - when and how to devops
The document discusses DevOps, including what it is, its benefits, and how to implement it. DevOps is a multidisciplinary movement that speeds up IT-related business change and reduces costs and risks by improving deployment. Implementing DevOps requires fundamental cultural changes, including looser leadership, self-organizing teams, and a shift towards experimentation, learning, continuous improvement, and teamwork.
Introduction to Kanban
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide an overview of the Kanban method, including the history and motivation, the core principles and practices, and how these apply to efficiency and process improvement in software development.
Come join us for this free Webinar!
More with Less - Agile Meetup 2014/9/18
This document discusses strategies for scaling agile development practices to larger teams and projects. It recommends organizing teams around product features rather than components to avoid coordination issues. Continuous integration and emergent design principles are also emphasized to help maintain quality and deliver work incrementally. Customer validation of requirements through experiments is advised to avoid creating unnecessary features.
Introduction to Kanban
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide an overview of the Kanban method, including the history and motivation, the core principles and practices, and how these apply to efficiency and process improvement in software development.
Come join us for this free Webinar!
Destroying DevOps Culture Anti-Patterns
A talk on the behaviors a team should display when undergoing a successful DevOps journey and transformation.
Large scale agile_svante_lidman
This presentation discusses patterns and anti-patterns for transforming a large legacy organization to being lean and agile. It describes a case study of a large product development unit that successfully piloted an agile transformation. Key lessons included focusing on flow over tasks, implementing cross-functional feature teams, learning from an organization that had already transformed, and having top management support to help overcome organizational impediments. The presentation advises line managers to educate themselves on agile principles, manage by supporting product flow rather than delegating, and question old assumptions about development processes.
LeSS in the big bank a five-year journey
We will trace the history of LeSS in a large bank from underground to the preferred framework from the perspective of 16 LeSS-like cases.
I will tell how I grew LeSS and got a profit in the hostile organizational structure.
I will share how I sold the LeSS framework to business people who hadn’t heard anything about Agile before and wanted to save their subordinate managers.
How I helped middle managers understand their roles in the new LeSS context and how many of them were fired.
In the end, I will explain 5 years of struggle between the corporate bonus system and the LeSS principle of a single goal for all teams of one product.
Principles of ManagementPrinciples of ManagementPrinciples of Manageme.docx
Principles of ManagementPrinciples of Management
Principles of ManagementPrinciples of Management
[AUTHORS REMOVED AT REQUEST OF ORIGINAL
PUBLISHER]
UNIVERSITY OF MINNESOTA LIBRARIES PUBLISHING EDITION, 2015. THIS EDITION ADAPTED FROM A WORK ORIGINALLY PRODUCED IN 2010 BY A PUBLISHER WHO HAS REQUESTED THAT IT NOT RECEIVE
ATTRIBUTION. MINNEAPOLIS, MN
Principles of Management by University of Minnesota is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License, except where otherwise noted.
Contents
Publisher Information x
Chapter 1: Introduction to Principles of Management
1.1 Introduction to Principles of Management 2 1.2 Case in Point: Doing Good as a Core Business Strategy 5 1.3 Who Are Managers? 8 1.4 Leadership, Entrepreneurship, and Strategy 13 1.5 Planning, Organizing, Leading, and Controlling 20 1.6 Economic, Social, and Environmental Performance 25 1.7 Performance of Individuals and Groups 31 1.8 Your Principles of Management Survivor’s Guide 36
Chapter 2: Personality, Attitudes, and Work Behaviors
2.1 Chapter Introduction 48 2.2 Case in Point: SAS Institute Invests in Employees 50 2.3 Personality and Values 52 2.4 Perception 70 2.5 Work Attitudes 78 2.6 The Interactionist Perspective: The Role of Fit 84 2.7 Work Behaviors 87 2.8 Developing Your Positive Attitude Skills 100
Chapter 3: History, Globalization, and Values-Based Leadership
3.1 History, Globalization, and Values-Based Leadership 104 3.2 Case in Point: Hanna Andersson Corporation Changes for Good 106 3.3 Ancient History: Management Through the 1990s 109 3.4 Contemporary Principles of Management 116 3.5 Global Trends 122
3.6 Globalization and Principles of Management 130 3.7 Developing Your Values-Based Leadership Skills 136
Chapter 4: Developing Mission, Vision, and Values
4.1 Developing Mission, Vision, and Values 143 4.2 Case in Point: Xerox Motivates Employees for Success 145 4.3 The Roles of Mission, Vision, and Values 148 4.4 Mission and Vision in the P-O-L-C Framework 153 4.5 Creativity and Passion 160 4.6 Stakeholders 169 4.7 Crafting Mission and Vision Statements 175 4.8 Developing Your Personal Mission and Vision 182
Chapter 5: Strategizing
5.1 Strategizing 191 5.2 Case in Point: Unnamed Publisher Transforms Textbook Industry 193 5.3 Strategic Management in the P-O-L-C Framework 196 5.4 How Do Strategies Emerge? 204 5.5 Strategy as Trade-Offs, Discipline, and Focus 209 5.6 Developing Strategy Through Internal Analysis 219 5.7 Developing Strategy Through External Analysis 231 5.8 Formulating Organizational and Personal Strategy With the Strategy Diamond 242
Chapter 6: Goals and Objectives
6.1 Goals and Objectives 251 6.2 Case in Point: Nucor Aligns Company Goals With Employee Goals 253 6.3 The Nature of Goals and Objectives 255 6.4 From Management by Objectives to the Balanced Scorecard 260 6.5 Characteristics of Effective Goals and Objectives 269 6.6 Using Goals and Objectives in Employee Performance Evaluation 275 6.7 Int.
Similar to More with LeSS - short intro (20)
Agile lean workshop for managers & exec leadership
Agile lean workshop for managers & exec leadership
KAA 2017 - Comparing Scaling Frameworks: LeSS & SAFe
KAA 2017 - Comparing Scaling Frameworks: LeSS & SAFe
Teaching pointy haired bosses to be agile enablers
Teaching pointy haired bosses to be agile enablers
Organization structure @ flat army symposium nov2014
Organization structure @ flat army symposium nov2014
Organization structure @ Building an Engaged Flat Army in the Library Symposi...
Organization structure @ Building an Engaged Flat Army in the Library Symposi...
9 dev ops mark smalley & lex scholten - when and how to devops
9 dev ops mark smalley & lex scholten - when and how to devops
Principles of ManagementPrinciples of ManagementPrinciples of Manageme.docx
Principles of ManagementPrinciples of ManagementPrinciples of Manageme.docx
Recently uploaded
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance Osaka Seminar
By Design, not by Accident - Agile Venture Bolzano 2024
As presented at the Agile Venture Bolzano, 4.06.2024
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
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.
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
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GridMate - End to end testing is a critical piece to ensure quality and avoid...
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
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.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Recently uploaded (20)
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf
By Design, not by Accident - Agile Venture Bolzano 2024
By Design, not by Accident - Agile Venture Bolzano 2024
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
GridMate - End to end testing is a critical piece to ensure quality and avoid...
GridMate - End to end testing is a critical piece to ensure quality and avoid...
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
Monitoring Java Application Security with JDK Tools and JFR Events
Monitoring Java Application Security with JDK Tools and JFR Events
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
More with LeSS - short intro
- 1. Elad Sofer - Certified LeSS trainer follow me on twitter - @eladsof Large Scale Scrum
- 2. About me - Elad Sofer • Father and husband • Live in Israel. • 20 years in Software development • Agile coach • LeSS certified trainer
- 5. The sad truth • Succeeding with one-team-Scrum is difficult enough. • You organization is probably bigger than it needs to be. • LeSS is not going to help you with scaling your organization.
- 6. The “LeSS” question is:
- 8. and… There are no best practices. Only good practices within a specific context The basic assumptions Over complexity hurts agility
- 9. Larman's Laws of Organizational Behavior 1. Organizations are implicitly optimized to avoid changing the status quo of middle- and first-level manager and “specialist” positions & power structures. 2. As a corollary to (1), any change initiative will be reduced to redefining or overloading the new terminology to mean basically the same as status quo. 3. As a corollary to (1), any change initiative will be derided as “purist”, “theoretical”, “revolutionary”, "religion", and “needing pragmatic customization for local concerns” -- which deflects from addressing weaknesses and manager/specialist status quo. 4. Culture follows structure.
- 10. 600 Experiments
- 11. 2008 Table of contents 1.Introduction Thinking tools Organisational tools 2.Systems Thinking 3.Lean Thinking 4.Queueing Theory 5.False Dichotomies 6.Be Agile 7.Feature Teams 8.Teams 9.Requirements Areas 10.Organisation 11.Large-Scale Scrum
- 12. 2010 Table of contents 1.Introduction Action tools 2.Large-Scale Scrum 3.Test 4.Product Management 5.Planning 6.Coordination 7.Requirements 8.Design & Architecture 9.Legacy Code 10.Continuous Integration 11.Inspect & Adapt 12.Multisite 13.Offshore 14.Contracts
- 13. 3 Pages of Rules
- 17. 2016 Table of contents 1.More with LeSS 2.LeSS LeSS Structure 3.Adoption 4.Organise by Customer Value 5.Managers 6.ScrumMasters LeSS Product 7.Product Owner 8.Product Backlog 9.Definition of Done 10.Initial PBR LeSS Sprint 11.Sprint Planning 12.Sprint Coordination and Integration 13.Product Backlog Refinement 14.Sprint Review 15.Sprint RetrospectiveMore or LeSS 16.More or LeSS; Architecture, DevOps
- 19. Two Frameworks: LeSS and LeSS Huge 2-8 teams >8 teams
- 20. LeSS - Up to 8 teams
- 22. Scrum recommends that the backlog is refined for ~2 sprints ahead Items per spint per team: 3-4 For 8 teams: at any given moment ~100 backlog items.
- 23. LeSS Huge
- 25. Upcoming Certified LeSS Practitioner courses • April 19, 2017 - Riga, Latvia • May 10, 2017 - Chicago, United States • June 19, 2017 - Dublin, Ireland • July 12, 2017 - Zurich, Switzerland • August 1, 2017 - Hamburg, Germany • Learn more at http://less.works