Scaling agile using SOS
•Download as PPTX, PDF•
1 like•319 views
During one of the "Discuss Agile" meetup's I had the opportunity of presenting the approach I had taken to implement Scrum of Scrums (A.K.A SOS)
Report
Share
Report
Share
Recommended
Don’t Make These Scrum Mistakes
Sumedha Ganjoo presented on common mistakes made when adopting Scrum. She discussed how having one person act as both the product owner and Scrum master leads to conflicts of interest and less accountability. Other mistakes include not properly estimating work, allowing technical debt to accumulate, focusing on documentation over working software, and customizing Scrum practices without understanding the reasons behind them. The presentation emphasized separating roles, setting clear expectations, prioritizing working software over documentation, and making incremental improvements based on team feedback and retrospectives.
Continuous Integration: Getting your department to drink the Kool-Aid
Everyone wants automated regression, automated builds, and single click deployments. Who wouldn’t want day to day development blockers eliminated. However, getting these things happening in your office might often face fierce resistance. Here is how one small department banded together for success.
Presented by Jen Knight, Michael Benning
Continuous Integration - Getting Your Department To Drink The Kool Aid
This document discusses strategies for getting a department to adopt continuous integration practices. It recommends starting with a proof of concept project, gaining support from management and technical leaders, and evangelizing successful examples. Specific tactics include automating tests, deployments, and reducing time between changes and production to demonstrate value. The goal is to standardize continuous integration processes across teams through education, collaboration, and leading by example.
Software Engineering Agile methodology SCRUM
This document provides an introduction to Agile development and Scrum methodology. It discusses that Agile focuses on iterative development with collaboration between cross-functional teams. Scrum is an Agile methodology that uses sprints, daily stand-ups, backlogs and emphasizes self-organizing teams. A Scrum team works in sprints to develop working software increments based on prioritized backlog items.
Certified Scrum Master Training - IAL Global
CSM helps project team to use scrum effectively. Anybody with complex project can use scrum in their projects.IAL Global is prominent in providing CSM training in Australia.
The Scrum Master Role
The document outlines the key responsibilities of a Scrum Master which include facilitating transparent communication and self-organization within the team. The Scrum Master aims to help the team adapt quickly to changes, solve problems independently, and create visual reporting tools. Some of the Scrum Master's other responsibilities are to reflect on meetings and ceremonies, ensure definition of done is agreed upon, protect the team from obstacles, and celebrate the team's successes.
Jira (Being Agile with Your Jira Board)
Jira is an issue tracking tool from Atlassian that can help organizations manage products and work. It uses workflows like Scrum and Kanban to plan work in cycles or track long lists of tasks. The document introduces Jira and compares it to similar tools, then discusses common workflows like tracking issues, maintaining a backlog, prioritizing tasks, and assigning work. It emphasizes finding the workflow that works best for each individual company or product.
Scrum by picture
This document provides a pictorial overview of the Scrum framework, which is an agile process for managing work. It outlines the core values of Scrum which include commitment, courage, focus, openness, and respect. The Scrum team consists of a Product Owner, Development Team, and Scrum Master. Key Scrum events include the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Artifacts in Scrum include the Product Backlog, Sprint Backlog, and Increment. This derivative work is based on the Scrum Guide and is offered under a Creative Commons license.
Recommended
Don’t Make These Scrum Mistakes
Sumedha Ganjoo presented on common mistakes made when adopting Scrum. She discussed how having one person act as both the product owner and Scrum master leads to conflicts of interest and less accountability. Other mistakes include not properly estimating work, allowing technical debt to accumulate, focusing on documentation over working software, and customizing Scrum practices without understanding the reasons behind them. The presentation emphasized separating roles, setting clear expectations, prioritizing working software over documentation, and making incremental improvements based on team feedback and retrospectives.
Continuous Integration: Getting your department to drink the Kool-Aid
Everyone wants automated regression, automated builds, and single click deployments. Who wouldn’t want day to day development blockers eliminated. However, getting these things happening in your office might often face fierce resistance. Here is how one small department banded together for success.
Presented by Jen Knight, Michael Benning
Continuous Integration - Getting Your Department To Drink The Kool Aid
This document discusses strategies for getting a department to adopt continuous integration practices. It recommends starting with a proof of concept project, gaining support from management and technical leaders, and evangelizing successful examples. Specific tactics include automating tests, deployments, and reducing time between changes and production to demonstrate value. The goal is to standardize continuous integration processes across teams through education, collaboration, and leading by example.
Software Engineering Agile methodology SCRUM
This document provides an introduction to Agile development and Scrum methodology. It discusses that Agile focuses on iterative development with collaboration between cross-functional teams. Scrum is an Agile methodology that uses sprints, daily stand-ups, backlogs and emphasizes self-organizing teams. A Scrum team works in sprints to develop working software increments based on prioritized backlog items.
Certified Scrum Master Training - IAL Global
CSM helps project team to use scrum effectively. Anybody with complex project can use scrum in their projects.IAL Global is prominent in providing CSM training in Australia.
The Scrum Master Role
The document outlines the key responsibilities of a Scrum Master which include facilitating transparent communication and self-organization within the team. The Scrum Master aims to help the team adapt quickly to changes, solve problems independently, and create visual reporting tools. Some of the Scrum Master's other responsibilities are to reflect on meetings and ceremonies, ensure definition of done is agreed upon, protect the team from obstacles, and celebrate the team's successes.
Jira (Being Agile with Your Jira Board)
Jira is an issue tracking tool from Atlassian that can help organizations manage products and work. It uses workflows like Scrum and Kanban to plan work in cycles or track long lists of tasks. The document introduces Jira and compares it to similar tools, then discusses common workflows like tracking issues, maintaining a backlog, prioritizing tasks, and assigning work. It emphasizes finding the workflow that works best for each individual company or product.
Scrum by picture
This document provides a pictorial overview of the Scrum framework, which is an agile process for managing work. It outlines the core values of Scrum which include commitment, courage, focus, openness, and respect. The Scrum team consists of a Product Owner, Development Team, and Scrum Master. Key Scrum events include the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Artifacts in Scrum include the Product Backlog, Sprint Backlog, and Increment. This derivative work is based on the Scrum Guide and is offered under a Creative Commons license.
2017 scrum-guide-us
The document is the Scrum Guide, which provides the definition and framework of Scrum. It describes Scrum as an agile framework for managing complex work, with roles of Product Owner, Development Team and Scrum Master. It outlines Scrum events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective. It also describes Scrum artifacts like the Product Backlog, Sprint Backlog and Increment. The guide was created by Ken Schwaber and Jeff Sutherland, who developed the Scrum framework.
AdvanScrum: To Scrum and Beyond
This document introduces AdvanScrum, which suggests practical tools and techniques based on Scrum but with a new mindset. It describes 3 roles, 5 meetings, and 3 artifacts. It notes some alternative terminology used such as "Mission Manager" instead of "Product Owner" and "Iteration" instead of "Sprint." It emphasizes flexibility in using any tools or techniques and not making anything mandatory. The goal is to deliver improved increments every iteration while also improving self, team, and company.
Introducing Scrum to an Organization
This document introduces Scrum and provides guidance on introducing Agile and Scrum to an organization. It defines Scrum roles and meetings. It notes that adopting Scrum requires systemic change that is difficult but can make an organization more productive and innovative. It recommends adopting Scrum both top-down with executive support and bottom-up driven by teams, starting small with at-risk projects to minimize risk while gaining support.
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.
Workshop debrief
The workshop aimed to teach new procedures and skills, but anticipated obstacles in implementing them and support needed for effective application, with follow up activities suggested to reinforce learning.
CSPO training & Certification
Certified scrum product owner certification is provided by ScrumAlliance after successfully completing the training from us.Visit us and get trained from expertise Agile trainers.
Scrum Master Roles and Responsibilities | Scrum Master Tutorial | Edureka
YouTube Link: https://youtu.be/X95kqqaI9Fg
** Certified Scrum Master Training: https://www.edureka.co/certified-scrum-master-certification-training **
This Edureka PPT on "Scrum Master Roles and Responsibilities" will help you understand who scrum master exactly is and what role does he play in scrum product development.
Introduction to Scrum
Who is a Scrum Master?
Role of a Scrum Master
Responsibilities of a Scrum Master
Qualities of a Good Scrum Master
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Scrum Master
Scrum is certainly not a foolproof framework as it does have its own set
of limitations; which is the reason why it may not be the best fit for
every team or product. There are other Agile and Lean approaches too,
like Kanban or XP.
Therefore, what is crucial is for us to comprehend that these current
shifts call for a dynamic and progressive outlook from developers and managers. The need of the hour is to utilize the benefits that a Scrum Master brings to the table, in terms of opening up team communication and problem solving techniques.
Scrum (406,439)
This document discusses the Scrum framework. Scrum is an agile process for managing complex product development. It uses self-organizing cross-functional teams, sprints, daily stand-ups, and artifacts like a product backlog and sprint backlog. The key components of Scrum include roles like the Scrum Master, Product Owner, and Scrum Team. The Scrum process involves sprint planning, daily stand-ups, and producing an increment of work each sprint.
Scrum and Teamwork
Scrum is a simple framework for iterative software development that can be implemented quickly. It focuses on self-organizing teams, short development cycles called sprints, regular inspection and adaptation, and transparency. Key roles include the product owner, scrum master, and development team. The team works through a backlog of tasks prioritized by the product owner and tracks progress through meetings and artifacts like burn-down charts. While good for focusing a co-located team, scrum may need tailoring for larger or distributed teams.
full-stack agile - Scrum Basics
A small presentation by Ashley-Christian Hardy on the basics of Scrum methodology, covering the basics of roles & responsibilities, events & ceremonies and scrum artefacts.
What is a SCRUM Master
The document describes the role and responsibilities of a Scrum Master. It states that a Scrum Master facilitates the team, ensures Scrum is used correctly, resolves impediments, protects the team, and coaches them. Key responsibilities include planning meetings, enforcing Scrum practices, removing blockers to progress, and helping the team and product owner improve. A Scrum Master has authority over processes but not individuals. Personal characteristics like being a servant leader and having an open, enthusiastic mindset are important for the role.
T3CON 19 Scrum for web agencies, does it really work?
Scrum frameworks can work for web agencies but may need adaptation. Typical challenges for web agencies include small projects, budgets, teams, and stakeholders not being fully involved in Scrum. Scrum works best for long-term, complex products with dedicated teams and POs. Some adaptations include using smaller Scrum teams, hybrid Scrumban approaches, no estimates, integrating designers into teams, and focusing on deploying MVPS and learning from feedback. Open discussion of how others have implemented Scrum in web agencies is encouraged.
Role of scrum master
It is the team who does all the work. Team is self-organising. Team decides and plans. So what is the role of scrum master? Is it a full time role? How is it different from a project manager? Can a project lead or manager be a scrum master? It is probably the least understood and the most abused role in scrum. Let's explore these points in details further on April 10, 3:00 PM.
3 Roles in Scrum
Role of scrum master
Challenges of a scrum master
Skills, Knowledge & mindset required
Full time or part time?
Future career path of scrum master
Benefits:
Uncover the true role of a scrum master which is that of a facilitator, protector, negotiator and a coach.
Understand the true meaning of coaching.
Learn how scrum master can coach the team.
Understand the skills, knowledge and mindset required as a scrum master.
Perform better as a scrum master by getting introduced to some magical techniques and fad words like gamestorming, innovation games and visual thinking to facilitate collaborative decision making.
Learn points which you can use to make people understand the vital role a scrum master plays.
Appreciate the difference between project manager and a scrum master.
Learn who can be a good scrum master.
Attend the webinar and separate yourself from the crazy herd of people blindly accepting or discarding the role of scrum master!!
The Scrum Roles presented by the Scrumlies 2009
The document outlines the 6 core roles in Scrum: ScrumMaster, Product Owner, Team, Customer, Manager, and End User. It describes each role and how they work together. The ScrumMaster protects the team and removes impediments. The Product Owner defines the product vision and backlog. The Team delivers working software each sprint. The Customer requests the product and provides feedback. The Manager establishes organizational structure. The End User provides requirements and feedback.
Scrum role introduction – the scrum master
This document discusses the role of the Scrum Master. It provides an overview of the Scrum Master's responsibilities which include removing impediments, facilitating meetings like the daily scrum, and ensuring the team follows the Scrum process. It also gives examples of scenarios a Scrum Master may face and how they could address them, such as a team member being late or a team not being on track to finish a sprint. The document recommends tools a Scrum Master can use to help guide their work, like a checklist to review how the team and product owner are adhering to Scrum practices.
Scrum is not for everyone: How Scrum does not look like
The document discusses how Scrum is commonly misunderstood and misapplied. It is not simply about daily standups and retrospectives, but is a framework that prescribes specific events and roles. Scrum requires cross-functional self-organizing teams, iterations with working increments, and values of commitment, courage and respect. For a project to truly use Scrum, it must have autonomy for development teams and continuously inspect and adapt the product backlog and sprint goals.
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.
Agile antipatterns webinar august17
This document provides a summary of Raj Kasturi's background and qualifications. It lists that Raj has over 25 years of IT experience including eight years of enterprise Agile experience. It also notes that he has been an adjunct faculty member at Penn State, has 18+ years of teaching experience in areas like Scrum and project management, and has experience in roles like Agile Coach, Scrum Trainer, and Scrum Master. The document provides Raj's contact information and identifies that he is a speaker who volunteers at agile conferences and user groups.
Enterprise andscrum kenschwaber
This document provides an overview and introduction to the book "The Enterprise and Scrum" which discusses best practices for adopting the Scrum framework across an entire enterprise rather than just small teams. The introduction explains that the book aims to help readers navigate how to implement Scrum enterprise-wide to make their entire organization more effective. It notes that Scrum will expose any existing problems or impediments that prevent the enterprise from developing products rapidly and with high quality. The document outlines some of the typical changes that enterprises experience when adopting Scrum such as staff turnover, conflicts as new ways of working are implemented, and shifts in roles and responsibilities for management, product management, and engineering teams.
Scrum distribution risk score
Presentation for AgileDays 2011 by Anna Obukhova, describes the problems of distributed development and team composition with recommendations.
Promises To Frame Scrum
This is a tool to help practioners implmenting scrum. It is a short discussion and exercise around a short hand way of framing scrum with promises. It is intended for experienced facilitators. http://advancedtopicsinscrum.com
More Related Content
What's hot
2017 scrum-guide-us
The document is the Scrum Guide, which provides the definition and framework of Scrum. It describes Scrum as an agile framework for managing complex work, with roles of Product Owner, Development Team and Scrum Master. It outlines Scrum events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective. It also describes Scrum artifacts like the Product Backlog, Sprint Backlog and Increment. The guide was created by Ken Schwaber and Jeff Sutherland, who developed the Scrum framework.
AdvanScrum: To Scrum and Beyond
This document introduces AdvanScrum, which suggests practical tools and techniques based on Scrum but with a new mindset. It describes 3 roles, 5 meetings, and 3 artifacts. It notes some alternative terminology used such as "Mission Manager" instead of "Product Owner" and "Iteration" instead of "Sprint." It emphasizes flexibility in using any tools or techniques and not making anything mandatory. The goal is to deliver improved increments every iteration while also improving self, team, and company.
Introducing Scrum to an Organization
This document introduces Scrum and provides guidance on introducing Agile and Scrum to an organization. It defines Scrum roles and meetings. It notes that adopting Scrum requires systemic change that is difficult but can make an organization more productive and innovative. It recommends adopting Scrum both top-down with executive support and bottom-up driven by teams, starting small with at-risk projects to minimize risk while gaining support.
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.
Workshop debrief
The workshop aimed to teach new procedures and skills, but anticipated obstacles in implementing them and support needed for effective application, with follow up activities suggested to reinforce learning.
CSPO training & Certification
Certified scrum product owner certification is provided by ScrumAlliance after successfully completing the training from us.Visit us and get trained from expertise Agile trainers.
Scrum Master Roles and Responsibilities | Scrum Master Tutorial | Edureka
YouTube Link: https://youtu.be/X95kqqaI9Fg
** Certified Scrum Master Training: https://www.edureka.co/certified-scrum-master-certification-training **
This Edureka PPT on "Scrum Master Roles and Responsibilities" will help you understand who scrum master exactly is and what role does he play in scrum product development.
Introduction to Scrum
Who is a Scrum Master?
Role of a Scrum Master
Responsibilities of a Scrum Master
Qualities of a Good Scrum Master
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Scrum Master
Scrum is certainly not a foolproof framework as it does have its own set
of limitations; which is the reason why it may not be the best fit for
every team or product. There are other Agile and Lean approaches too,
like Kanban or XP.
Therefore, what is crucial is for us to comprehend that these current
shifts call for a dynamic and progressive outlook from developers and managers. The need of the hour is to utilize the benefits that a Scrum Master brings to the table, in terms of opening up team communication and problem solving techniques.
Scrum (406,439)
This document discusses the Scrum framework. Scrum is an agile process for managing complex product development. It uses self-organizing cross-functional teams, sprints, daily stand-ups, and artifacts like a product backlog and sprint backlog. The key components of Scrum include roles like the Scrum Master, Product Owner, and Scrum Team. The Scrum process involves sprint planning, daily stand-ups, and producing an increment of work each sprint.
Scrum and Teamwork
Scrum is a simple framework for iterative software development that can be implemented quickly. It focuses on self-organizing teams, short development cycles called sprints, regular inspection and adaptation, and transparency. Key roles include the product owner, scrum master, and development team. The team works through a backlog of tasks prioritized by the product owner and tracks progress through meetings and artifacts like burn-down charts. While good for focusing a co-located team, scrum may need tailoring for larger or distributed teams.
full-stack agile - Scrum Basics
A small presentation by Ashley-Christian Hardy on the basics of Scrum methodology, covering the basics of roles & responsibilities, events & ceremonies and scrum artefacts.
What is a SCRUM Master
The document describes the role and responsibilities of a Scrum Master. It states that a Scrum Master facilitates the team, ensures Scrum is used correctly, resolves impediments, protects the team, and coaches them. Key responsibilities include planning meetings, enforcing Scrum practices, removing blockers to progress, and helping the team and product owner improve. A Scrum Master has authority over processes but not individuals. Personal characteristics like being a servant leader and having an open, enthusiastic mindset are important for the role.
T3CON 19 Scrum for web agencies, does it really work?
Scrum frameworks can work for web agencies but may need adaptation. Typical challenges for web agencies include small projects, budgets, teams, and stakeholders not being fully involved in Scrum. Scrum works best for long-term, complex products with dedicated teams and POs. Some adaptations include using smaller Scrum teams, hybrid Scrumban approaches, no estimates, integrating designers into teams, and focusing on deploying MVPS and learning from feedback. Open discussion of how others have implemented Scrum in web agencies is encouraged.
Role of scrum master
It is the team who does all the work. Team is self-organising. Team decides and plans. So what is the role of scrum master? Is it a full time role? How is it different from a project manager? Can a project lead or manager be a scrum master? It is probably the least understood and the most abused role in scrum. Let's explore these points in details further on April 10, 3:00 PM.
3 Roles in Scrum
Role of scrum master
Challenges of a scrum master
Skills, Knowledge & mindset required
Full time or part time?
Future career path of scrum master
Benefits:
Uncover the true role of a scrum master which is that of a facilitator, protector, negotiator and a coach.
Understand the true meaning of coaching.
Learn how scrum master can coach the team.
Understand the skills, knowledge and mindset required as a scrum master.
Perform better as a scrum master by getting introduced to some magical techniques and fad words like gamestorming, innovation games and visual thinking to facilitate collaborative decision making.
Learn points which you can use to make people understand the vital role a scrum master plays.
Appreciate the difference between project manager and a scrum master.
Learn who can be a good scrum master.
Attend the webinar and separate yourself from the crazy herd of people blindly accepting or discarding the role of scrum master!!
The Scrum Roles presented by the Scrumlies 2009
The document outlines the 6 core roles in Scrum: ScrumMaster, Product Owner, Team, Customer, Manager, and End User. It describes each role and how they work together. The ScrumMaster protects the team and removes impediments. The Product Owner defines the product vision and backlog. The Team delivers working software each sprint. The Customer requests the product and provides feedback. The Manager establishes organizational structure. The End User provides requirements and feedback.
Scrum role introduction – the scrum master
This document discusses the role of the Scrum Master. It provides an overview of the Scrum Master's responsibilities which include removing impediments, facilitating meetings like the daily scrum, and ensuring the team follows the Scrum process. It also gives examples of scenarios a Scrum Master may face and how they could address them, such as a team member being late or a team not being on track to finish a sprint. The document recommends tools a Scrum Master can use to help guide their work, like a checklist to review how the team and product owner are adhering to Scrum practices.
Scrum is not for everyone: How Scrum does not look like
The document discusses how Scrum is commonly misunderstood and misapplied. It is not simply about daily standups and retrospectives, but is a framework that prescribes specific events and roles. Scrum requires cross-functional self-organizing teams, iterations with working increments, and values of commitment, courage and respect. For a project to truly use Scrum, it must have autonomy for development teams and continuously inspect and adapt the product backlog and sprint goals.
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.
Agile antipatterns webinar august17
This document provides a summary of Raj Kasturi's background and qualifications. It lists that Raj has over 25 years of IT experience including eight years of enterprise Agile experience. It also notes that he has been an adjunct faculty member at Penn State, has 18+ years of teaching experience in areas like Scrum and project management, and has experience in roles like Agile Coach, Scrum Trainer, and Scrum Master. The document provides Raj's contact information and identifies that he is a speaker who volunteers at agile conferences and user groups.
Enterprise andscrum kenschwaber
This document provides an overview and introduction to the book "The Enterprise and Scrum" which discusses best practices for adopting the Scrum framework across an entire enterprise rather than just small teams. The introduction explains that the book aims to help readers navigate how to implement Scrum enterprise-wide to make their entire organization more effective. It notes that Scrum will expose any existing problems or impediments that prevent the enterprise from developing products rapidly and with high quality. The document outlines some of the typical changes that enterprises experience when adopting Scrum such as staff turnover, conflicts as new ways of working are implemented, and shifts in roles and responsibilities for management, product management, and engineering teams.
What's hot (20)
Scrum Master Roles and Responsibilities | Scrum Master Tutorial | Edureka
Scrum Master Roles and Responsibilities | Scrum Master Tutorial | Edureka
T3CON 19 Scrum for web agencies, does it really work?
T3CON 19 Scrum for web agencies, does it really work?
Scrum is not for everyone: How Scrum does not look like
Scrum is not for everyone: How Scrum does not look like
Similar to Scaling agile using SOS
Scrum distribution risk score
Presentation for AgileDays 2011 by Anna Obukhova, describes the problems of distributed development and team composition with recommendations.
Promises To Frame Scrum
This is a tool to help practioners implmenting scrum. It is a short discussion and exercise around a short hand way of framing scrum with promises. It is intended for experienced facilitators. http://advancedtopicsinscrum.com
Scaling scrum agile2010
Have you successfully implemented Scrum on your team, but are finding the pain of scaling your Scrum deployment to the larger organization too much to handle? Is the Scrum of Scrums concept not working out the way you thought it would? Have you had success with scaling Scrum, and want to share what you’ve learned with others? If you answered yes to any of these questions, join us for this interactive session where Melanie Paquette shares the experiences of different of different types of organizations that have had success in scaling Scrum. The organizations profiled include a large, geographically dispersed team of over 300 embedded software developers as well as a smaller, mostly co-located team of 50 mobile application developers. Learn what these organizations have in common, and take back practical techniques you can use to scale Scrum, including how to leverage a traditional project management organization to help your scaling efforts, how to structure large teams to involve the right people, and how to work with geographical distribution.
Agile presentation
Agile development is both a philosophy and methodology for building products in an iterative and incremental way. It involves short development cycles called sprints where self-organizing cross-functional teams focus on continuously delivering working software. Daily stand-up meetings help ensure transparency and coordination across the team. While agile aims to be flexible and lightweight, some key practices like planning, pair programming, and tracking progress help teams stay aligned and deliver value continuously.
Agile camp2016 agile101
The document provides an overview of Agile principles and the Scrum framework. It describes key Scrum roles like the Product Owner and Scrum Master. It also summarizes Scrum ceremonies such as Sprint Planning, Daily Standup, Sprint Review, and Retrospective. User stories and tracking work using a Kanban or Scrum board in TFS are also covered at a high level.
AgileCamp 2014 Track 1: Enterprise Scaling Patterns and Anti Patterns
AgileCamp 2014 Track 1: Enterprise Scaling Patterns and Anti PatternsHyperdrive Agile Leadership (powered by Bratton & Company)
This document describes several patterns for managing dependencies, planning for new and existing products, dealing with dispersed teams, and the challenges of remote product owners. It provides examples of solutions such as involving dependent teams in planning, dedicating teams to new vs existing products, maximizing co-location of teams, and using proxy product owners to help manage the product backlog for remote product owners. Real world examples of where these patterns have been used are also provided.Waterfall vs agile approach scrum framework and best practices in software d...
The document discusses various topics related to software development approaches, including:
1. The differences between waterfall and agile approaches. Agile focuses on iterative development and responding to change over extensive planning.
2. Common problems with traditional project management like late delivery and budget overruns.
3. An overview of the Scrum framework, including roles, artifacts, ceremonies, and best practices. Scrum uses short iterations called sprints to iteratively deliver working software.
4. Recommendations to customize Scrum by incorporating elements of eXtreme Programming (XP) and lean principles to eliminate waste and continually improve processes.
Scrum in Large Companies public edition
Based on our experience in introducing Scrum in large organizations we developed Scrum Readiness Checklist combining most important success factors, as well as troubleshooting guide for common problems.
How (can) Scrum and DevOps Walk Together to Build a High-Quality Product Deli...
Discussion in fishbowl format to find out how Scrum and DevOps should more power-full if we use it together and properly, then validating with data and convergence of CEO Scrum.org and CEO DevOps Institute.
Approaches to scaling agile
This presentation gives an overview of the 4 approaches to Scaling Agile - Scaled Agile Framework (SAFe), Disciplined Agile Delivery (DAD), Large Scale Scrum (LeSS) and Scaling Agile at Spotify (SA@S).
202004-Scrum-Master-Certification-Training-Manual.pdf
This document provides a summary of key Scrum concepts and roles. It explains that Scrum is a framework, not a methodology, and emphasizes empirical process control and self-organization. The three Scrum roles - Product Owner, Scrum Master, and Development Team - and their responsibilities are defined. Key Scrum events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective are also summarized in terms of their purpose and timebox guidelines.
Scrum And The Enterprise
This document discusses strategies for scaling Scrum practices within large organizations. It addresses organizing teams, integrating work across teams, managing people and skills, prioritizing work in an enterprise backlog, and delivering value through iterative development focused on the highest priority items. Key challenges include integrating work across multiple teams and layers, managing specialized skills, and ensuring continuous delivery of value at the enterprise level.
Scrum and Agile SDLC 101
The document provides an overview of Agile software development using Scrum. It describes Scrum as an Agile framework that focuses on delivering business value through short iterative development cycles called sprints. Key aspects of Scrum include self-organizing cross-functional teams, prioritized product backlogs maintained by a Product Owner, and regular sprint planning, daily standup, review and retrospective meetings facilitated by a Scrum Master.
Agile - Scrum
The document discusses key concepts in Agile development including Scrum framework. It compares traditional waterfall model with Agile approach. Some key Scrum concepts covered are roles, events, artifacts, empirical process control, transparency, self-organizing teams. It provides details on events like daily scrum, sprint planning and retrospective. Artifacts discussed are product backlog, sprint backlog and definition of done. Traditional vs Agile success rates are also shared.
Scrum master & agile master
Next level of Scrum Master, Using other Agile Framework apart from Scrum. Using Lean-Agile Principles
"Scrum master or Agile Master" - by Saikat Das @ Scaling Agile Institute
This next level of Scrum Master, their vision for future, how they can scale up in all agile framework apart from just Scrum
Introduction to Scrum
This document discusses Scrum, an agile framework for managing product development. It begins by providing a brief history of Scrum, noting that it originated from rugby terminology and emphasizes self-organizing teams. The document then outlines key Scrum concepts like the product backlog, sprints, increments, and the roles of the product owner and development team. It discusses when Scrum is and isn't applicable, such as for interrupt-driven work where Kanban may be better. The document also introduces the Cynefin framework for determining what approach fits different domains like simple, complicated, complex, chaotic, and disorder. It concludes by noting that while Scrum empowers teams, its implementation can be difficult and make problems visible
10 differences between SAFe and LeSS
Presentation from SAFE@Space conference on 2018.11.06.
Some differences between SAFe and LeSS framework.
Some difficult questions.
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.
Introduction to Scrum
This document provides an introduction and overview of Scrum, an agile framework for managing product development projects. It discusses the origins and principles of Scrum, key roles like the Product Owner and Scrum Master, ceremonies such as sprint planning and retrospectives, artifacts like the product and sprint backlogs, and how Scrum has been implemented successfully in organizations like Salesforce.com. The document also notes characteristics of Scrum projects and how it compares to traditional sequential development models.
Similar to Scaling agile using SOS (20)
AgileCamp 2014 Track 1: Enterprise Scaling Patterns and Anti Patterns
AgileCamp 2014 Track 1: Enterprise Scaling Patterns and Anti Patterns
Waterfall vs agile approach scrum framework and best practices in software d...
Waterfall vs agile approach scrum framework and best practices in software d...
How (can) Scrum and DevOps Walk Together to Build a High-Quality Product Deli...
How (can) Scrum and DevOps Walk Together to Build a High-Quality Product Deli...
202004-Scrum-Master-Certification-Training-Manual.pdf
202004-Scrum-Master-Certification-Training-Manual.pdf
"Scrum master or Agile Master" - by Saikat Das @ Scaling Agile Institute
"Scrum master or Agile Master" - by Saikat Das @ Scaling Agile Institute
More from Deepak Gururaja
Have we crossed the chasm
In this talk, I try to provide a perspective on weather or not we have crossed the Chasm with Agile transformation. Based on a few surveys, I explore the current state of agile adoption across the industry and try to predict the kind of coaching/transformation needs that might come up in the near future.
5 Simple tools for effective retrospectives
Through this slides, I present 5 basic tools that a scrum master should follow, in order to make retrospectives really effective. These are things that I have discovered based on my experience, and would like to share with people
6 thinkinghats
Edward de Bono came up with the idea of parallel thinking using the 6 thinking hats. These are the slides that I put together, based on my learning of the 6 Thinking hats, in order for people to have a quick reference point, to understand the idea of parallel thinking better
Test first
This document describes a Jenga game activity used to demonstrate the benefits of test-driven development. The activity involves building a 3-story Jenga tower with blocks, some of which contain defects. Participants undergo three iterations with different testing procedures: in the first, defects are found after building; in the second, defects are found every 10 blocks; in the third, defects are known for each individual block. The goal is to understand how rework effort decreases when testing occurs earlier in the development cycle rather than later.
Sprint planninng
The document discusses sprint planning in Scrum methodology. It explains that during sprint planning, the Scrum team decides what work can be completed during the sprint. They set two guideposts: the sprint backlog which is the work committed to and the sprint goal which is a short phrase stating what will be achieved. The newer approach to sprint planning involves two parts - part one where the team commits to the deliverables for the sprint and part two where the development team breaks down the work into tasks.
Scrum roles
Scrum roles include the Product Owner, Scrum Master, and Development Team. The Product Owner is responsible for the product backlog and has a complete understanding of customer and stakeholder needs. The Scrum Master helps the team stay motivated and removes impediments so the team can perform at its peak. The cross-functional Development Team is self-managed and accountable for delivering working software each sprint.
Daily standup
The slides that I used to help team understand the importance and the structure for the daily standup
Agile retrospectives
The document discusses the importance of the retrospective meeting in Scrum. It notes that early versions of Scrum did not include retrospectives and that they are important for teams to inspect and adapt their processes. Retrospectives provide an opportunity for teams to reflect on what went well and what can be improved in the last sprint and develop an action plan to become more effective. They should be time-boxed, focus on constructive feedback rather than blame, and actively engage the whole team, Scrum Master, and Product Owner to drive process improvements.
Agile metrices
Metrics are a measure of where and how we stand.
These decks are the ones I use to make teams realize the worth of metrices in Agile
Agile estimation
Estimation in Agile projects can be tricky sometimes, especially for teams and organizations that are moving into Agile from non-Agile frameworks
I use these slides, along with a small activity to train teams on estimation in Agile
More from Deepak Gururaja (10)
Recently uploaded
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
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.
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 | 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.
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.
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!
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
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.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Recently uploaded (20)
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Scaling agile using SOS
- 1. Scaled Scrum Deepak T Gururaja CSP, CSM
- 2. Agenda Scaling Scrum What, When and How Sharing of Best Practices
- 3. Before we begin What is the recommended team size in Scrum What if there is a need to scale to a larger number If it’s a single large team - administrative issues creep up
- 4. Team of Teams a.k.a SOS Scrum of Scrums More than one team working on delivering the same product Each team have Scrum roles within Each team is responsible for one unit of the product
- 5. When should you use it Typically with 2 or more Scrum teams Teams working on the same backlog Co-located or distributed teams Total size typically less than 50 Fairly complex project/product Companies that cannot afford to use the SAFe framework
- 6. Lets look more closely PSI Integrate
- 7. Sprint Fundamentals Sprint Planning Dependencies Prioritization Estimation Plan with dependencies in sight Standup calls At a Team SOS
- 8. Sprint Fundamentals Reviews Team – Do you see a value add? For the user story/product Retrospectives For the team For the product For the release
- 9. Scrum Fundamentals Sprint backlog For the team Burndown Team Product Task Board Team Product – User story completion Metrics For the team For the product
- 10. Drawing the line Horizontal slicing v/s vertical slicing Separation at module Separation at feature set Separation at plugins Who do you think are the best people to figure out where to draw the line?
- 11. So, how to you collaborate Sync up call – SOS Gives a pulse of the product as a whole Typically conducted once or twice a week for a duration of 15 minutes and treated like a standup call If there is a need for further elaboration/discussion, talk offline Mandate presence from all teams
- 12. The Scrum Of Scrum
- 13. Ok… what do you discuss? What did the team do between the last meeting and now? What will the team do between now and the next meeting? Is there anything that is getting in the way of your team? Are you going to work on anything that will impact other teams?
- 14. Who should attend the SOS Scrum Masters Team members representing the technical area Product management, if the need be Product managers Stakeholders are not typically a part of the SOS
- 15. Best practices Plan together – deliver together Same length iterations Better to have same product owner or someone who can take responsibility of the product release Work off the same product backlog Backlog grooming to identify dependencies Shared product Vision Visual flow at the product level
- 16. What about Our practices? DOD? For the user story Not for the team, but for the product DOR? Dependencies considered? For the user stories, not for the team Workflow Independent to the team
- 17. What about Engineering practices? Donot forget the basics – Clean code, unit testing, code reviews, etc Continuous integration eliminates risk to a large extent Have regular technical checkpoints Always work off the same code base Think about weather or not you want to keep the “master” clean Setting stringent coding standards brings more benefits than you can imagine
- 18. Pros Light weight Easy to implement Does not require sophisticated structure Is not intensive No patents or certifications yet
- 19. Cons Structure not defined Cannot be scalable beyond a certain number of teams No definite methods defined No dedicated roles
- 20. Think about….