Agile 101
•
0 likes•809 views
Myplanet values innovation, humanity, transparency, focus, and excellence. It trusts an agile approach to governance, procedures, guidance, organizational structure, policies, and decision-making. The document discusses how Myplanet uses agile principles and practices like short sprints, frequent progress meetings, prioritizing work based on business value, and continually adapting based on feedback.
Report
Share
Report
Share
Download to read offline
Recommended
Scrum retrospective
The sprint retrospective is a meeting that occurs at the end of each sprint cycle in Scrum. The purpose is for the team to inspect how the last sprint went and identify improvements for the next sprint. Key elements include discussing what went well, what went wrong, and what could be improved. The retrospective is collaborative, involving the whole team, and helps the team improve its processes and build ownership over outcomes.
Agile Roles #3 The Product Owner – What is this Mythical Beast?
What the heck is a Product Owner? Why do you need one? And how can the Product Owner help a team soar – or crash horribly?
In this talk Anthony Marter will share his experience developing the Product Owner role in 2 large NZ software organisations. He’ll cover
· The basics of the role, and how an effective Product Owner contributes to the success of a team
· The challenges of the role, especially at scale
· Why an effective Product Owner is key to establishing and maintaining organisational Agility
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.
Team play - Scrum or Kanban - Choose Your Agile Flavour
A brief overview on Scrum and Kanban, Agile methodology.
Comparison between two, taking notes of different and shared things.
SGIN2013-Keynote-Scrum about people-BobHartman
This document appears to be a presentation about collaborative innovation games. It discusses why Scrum projects fail due to forgetting the human factor. It also talks about Scrum values and an approach to success that involves appreciating, protecting, and inspiring people. The presentation provides an update on Scrum Alliance statistics and their efforts to advocate for Agile through user groups, gatherings, and education.
Mrgn.in scrum:agile - Céline Dedaj/Ableton
Agile Project Management with Scrum. A buzzword breakfast?
I briefly presented the core values of Agile Project Management and the basics of Scrum to get an idea of how to implement Agile with it.
Food for thoughts and discussion.
Nice meetup by the way. Thanks for having me!
Product Ownership - A shared sport!
Speak at Agile ME 2017:
Collapse publications section
Publications
Edit publication Agile ME 2017 - Speak: Pimp My Agile
publication titleAgile ME 2017 - Speak: Pimp My Agile
publication dateMar 18, 2017 publication descriptionAgile ME 2017
publication descriptionPowerpoint from my speak at Agile ME 2017, about how to optimize your agile process, by having an agile approach to your process as well as your product.
See publication Agile ME 2017 - Speak: Pimp My AgileSee publication
Edit publication Agile ME 2017 - Speak: Product Ownership - A shared sport!
publication titleAgile ME 2017 - Speak: Product Ownership - A shared sport!
publication dateMar 18, 2017 publication descriptionAgile ME 2017
publication description'Product Ownership' is a multi-faceted complex function that gets more and more challenging with additional variables; product industry/project nature, market drivers, technology and functionality being examples of external variables; while distributed teams, team structure and team size being internal variables- to name a few. 'Product Ownership' function is expected to be carried out by Product Owner. In reality it becomes a shared sport of disparate stakeholders. While PO controls and drives priorities and scope, he/she highly depends on team members for effective/efficient decision making across the product/project. In this interactive talk, we will elicit audience's understanding of this function and will try to explore what skillset(s) is/are critical to ensure the success for this function.
Scrum points v1a
The document discusses Agile and Scrum frameworks for project management. It explains that Agile focuses on individuals, interactions, working software, customer collaboration, and responding to change. Scrum is an Agile framework that uses short "sprints" or iterations to incrementally develop a product. Key Scrum roles include the Product Owner who manages requirements, the Development Team who does the work, and the Scrum Master who facilitates the process. The document outlines Scrum meetings and processes like sprint planning, daily standups, reviews, and retrospectives.
Recommended
Scrum retrospective
The sprint retrospective is a meeting that occurs at the end of each sprint cycle in Scrum. The purpose is for the team to inspect how the last sprint went and identify improvements for the next sprint. Key elements include discussing what went well, what went wrong, and what could be improved. The retrospective is collaborative, involving the whole team, and helps the team improve its processes and build ownership over outcomes.
Agile Roles #3 The Product Owner – What is this Mythical Beast?
What the heck is a Product Owner? Why do you need one? And how can the Product Owner help a team soar – or crash horribly?
In this talk Anthony Marter will share his experience developing the Product Owner role in 2 large NZ software organisations. He’ll cover
· The basics of the role, and how an effective Product Owner contributes to the success of a team
· The challenges of the role, especially at scale
· Why an effective Product Owner is key to establishing and maintaining organisational Agility
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.
Team play - Scrum or Kanban - Choose Your Agile Flavour
A brief overview on Scrum and Kanban, Agile methodology.
Comparison between two, taking notes of different and shared things.
SGIN2013-Keynote-Scrum about people-BobHartman
This document appears to be a presentation about collaborative innovation games. It discusses why Scrum projects fail due to forgetting the human factor. It also talks about Scrum values and an approach to success that involves appreciating, protecting, and inspiring people. The presentation provides an update on Scrum Alliance statistics and their efforts to advocate for Agile through user groups, gatherings, and education.
Mrgn.in scrum:agile - Céline Dedaj/Ableton
Agile Project Management with Scrum. A buzzword breakfast?
I briefly presented the core values of Agile Project Management and the basics of Scrum to get an idea of how to implement Agile with it.
Food for thoughts and discussion.
Nice meetup by the way. Thanks for having me!
Product Ownership - A shared sport!
Speak at Agile ME 2017:
Collapse publications section
Publications
Edit publication Agile ME 2017 - Speak: Pimp My Agile
publication titleAgile ME 2017 - Speak: Pimp My Agile
publication dateMar 18, 2017 publication descriptionAgile ME 2017
publication descriptionPowerpoint from my speak at Agile ME 2017, about how to optimize your agile process, by having an agile approach to your process as well as your product.
See publication Agile ME 2017 - Speak: Pimp My AgileSee publication
Edit publication Agile ME 2017 - Speak: Product Ownership - A shared sport!
publication titleAgile ME 2017 - Speak: Product Ownership - A shared sport!
publication dateMar 18, 2017 publication descriptionAgile ME 2017
publication description'Product Ownership' is a multi-faceted complex function that gets more and more challenging with additional variables; product industry/project nature, market drivers, technology and functionality being examples of external variables; while distributed teams, team structure and team size being internal variables- to name a few. 'Product Ownership' function is expected to be carried out by Product Owner. In reality it becomes a shared sport of disparate stakeholders. While PO controls and drives priorities and scope, he/she highly depends on team members for effective/efficient decision making across the product/project. In this interactive talk, we will elicit audience's understanding of this function and will try to explore what skillset(s) is/are critical to ensure the success for this function.
Scrum points v1a
The document discusses Agile and Scrum frameworks for project management. It explains that Agile focuses on individuals, interactions, working software, customer collaboration, and responding to change. Scrum is an Agile framework that uses short "sprints" or iterations to incrementally develop a product. Key Scrum roles include the Product Owner who manages requirements, the Development Team who does the work, and the Scrum Master who facilitates the process. The document outlines Scrum meetings and processes like sprint planning, daily standups, reviews, and retrospectives.
Agile Anti-patterns
A good anti-pattern has 2 elements:
1. A repeated pattern of action that appears beneficial, but ultimately produces more bad consequences than beneficial results.
2. A refactored solution exists that has been proven in actual practice and is repeatable.
So, what are common pitfalls that new (or even experienced) agile practitioners fall into? Learning about and watching out for these anti-patterns is a great way to inspect and adapt your agile practice.
Coaching Anti-Pattens and common smells
Sekhar Burra is an agile transformation coach who has led two large-scale agile transformations. He has experience as an executive agile coach, scrum master, product owner, and engineering manager. The document discusses a scenario where a coach provides feedback to a client about improving their daily stand-ups by addressing the three standard questions. It then defines what patterns and anti-patterns are in the context of agile development before giving examples of common anti-patterns and smells like having no retrospectives or one team member dominating planning meetings. Coaching techniques for addressing anti-patterns at the team and organizational level are discussed, including learning design patterns and using mocks, Jutta Eckstein's perspectives, and retrospective
Building A devopsy Team
This document provides tips for growing a devops team by breaking down historical silos between development and operations. It recommends starting by analyzing pain points, creating a cross-functional team with shared goals, improving communication, getting buy-in, automating processes, measuring success and failure, and giving everyone full access and responsibilities. The overall message is that devops requires cultural and process changes, not buying products, and is a continuous improvement journey.
Why is it so hard? Agile adoption anti-patterns, how to spot them and what to...
This document discusses common agile adoption anti-patterns that organizations should avoid, and presents positive patterns to follow instead. Some anti-patterns discussed include thinking there is a "perfect system", not fully committing to agile and wanting to do other things first, trying to measure and compare teams' performance numbers, thinking there is a single road to success, and focusing only on maximizing productivity. The document recommends focusing on people's interactions, understanding how the organization really works, seeking support and feedback, keeping business outcomes as the focus, allowing experimentation, and recognizing that learning and idle time are important.
Scrum values
The document discusses the five core values of Scrum: focus, courage, openness, commitment, and respect. It explains that these values are important for the health and success of Scrum teams. Focus values concentrating efforts on a few important tasks at a time to deliver work sooner. Courage values undertaking challenges and admitting imperfections with transparency. Openness values openly expressing concerns and collaborating. Commitment values having control over work with dedication to quality, collaboration, learning, and goals. Respect values regarding others with diverse backgrounds and opinions to strengthen the team.
Practical agile TechExeter
- Land Registry registers land ownership in England and Wales and has transitioned from a traditional to a more agile way of building products and services.
- They now take a user-centered approach with user research in each sprint, focus on service design with multi-disciplinary teams, build using microservices and continuous delivery to deploy updates.
- The transition has been challenging and requires clear objectives, executive support, breaking down silos, and ongoing communication but provides benefits like more adaptable and user-focused services.
Scrum in the Enterprise - Making It Work With Distributed Teams - Liz Heier
Liz Heier discusses how to implement Scrum successfully with distributed teams across multiple locations. She emphasizes that it requires having the right process, the right people, and the right tools. For the process, she recommends estimating backlogs, identifying minimum viable products, and using burn-up charts to monitor scope. For people, key roles include the Scrum Master, Product Owner, and development team. Effective communication across all teams is also important. For tools, she suggests using project management software for documentation, collaboration, code reviews, and ensuring transparency. With the right approach in these three areas, Scrum can be implemented effectively even with remote and distributed teams.
Being vs Doing agile
Most of the times I have seen the teams spending immense amount of time in mastering the mechanics than the intent.
Key to successful agile adoption is to have the agile as a team culture than just doing it
The Scrum Master Balance
In this presentation, we explore the concept of “process authority” as it relates to Scrum Masters and consider the various directions it takes us. To do that, this discussion goes far beyond a typical “the role of a Scrum Master” presentation; It explores…
• What it should (and should not) mean when/if “process authority” is used to describe the Scrum Master role
• How the responsibility and expectations of a Scrum Master are different than that of team members
• How different leadership styles play into understanding the role of the Scrum Master
• The importance of trust in a Scrum Master/team relationship
Lean Scaling – From Lean Startup to Lean Enterprise - Itamar Goldminz
Congratulations! You've found the right product-market fit, and it's now time to scale your business. But growing your organization often means slower decision making, increased complexity, and higher chance for misalignments. How can you grow your business while staying lean? Learn five key lessons on how to use smart integration and process to grow with your Atlassian tools.
Overcome the 6 Antipatterns of Agile Adoption
Presented at Global Scrum Gathering Orlando 2016
Because of benefits like predictability, better quality of products, and faster delivery, many companies have adopted or in the process of adopting Agile. However, there are challenges.
David Hawks, CST and Agile Evangelist, explains the common antipatterns of Agile adoption.
The Soup Stone - Catalyst to Agile Adoption
The document is a presentation about introducing agile practices. It begins with an introduction and overview of the presenter and scope of ScrumUP. It then tells a fairytale in three parts about a soup stone to illustrate introducing change. In between the fairytale parts are sections on models for change including the Rightshifting Model and Elephant and Rider model. It includes an exercise for participants to discuss introducing an agile practice to their team using the models. It closes by requesting evaluation of the presentation.
Collaboration is More Than Communication – JIRA Agile - Xavier Morera
Collaboration is defined as "the action of working with someone to produce or create something." Yet, many confuse communicating with collaborating. True collaboration gives you and your project an edge by aligning efforts towards a clear objective. I'll show how teams can achieve true collaboration with JIRA Agile.
Thats not my agile - Agile on the beach 2017
The document discusses challenges with adopting agile practices within large organizations and provides advice on overcoming those challenges. It recommends focusing on users and outcomes rather than strict adherence to processes. Small, fixed cross-functional teams are important to allow autonomy and build trust. Metrics should celebrate successes and identify problems to address rather than constrain teams. Leadership support is key to enabling a culture of trust and continuous learning over rigid processes.
Scrum101
This document provides an overview of Scrum, an agile framework for managing product development. It discusses the Scrum roles of Product Owner, Team, and Scrum Master. The key Scrum ceremonies are planning, daily stand-ups, sprint reviews, and retrospectives. Scrum uses short iterations called sprints to incrementally deliver working software. The document recommends starting with a short initial sprint length and identifying the Product Owner, Scrum Master, and cross-functional Team.
Scrum Shock Therapy: Going Back to Basics - Atlassian Summit 2012
The document discusses using "Scrum shock therapy" to transition a team from Kanban to Scrum by imposing strict rules like one-week sprints and fully estimating all work upfront. This caused pain for the team initially. Key learnings included the importance of good retrospectives and that physical card walls can improve communication but are hindrances to remote work. Barriers to agile adoption include a lack of automation and buy-in from the whole team. In the end, strict rules may only work for very dysfunctional teams and discipline is better achieved through other means.
Core Agility Workout - AgileIndy 2015
The document describes an agile workout consisting of three exercises to demonstrate agile principles. The first exercise shows that individuals are more efficient completing one task at a time rather than multitasking. The second exercise demonstrates that reducing batch sizes decreases overall completion time. The third exercise finds that self-organizing teams perform better than manager-led teams at solving problems. The exercises are intended to help internalize agile concepts such as eliminating waste, rapid delivery, and self-organizing teams.
Servant Leadership for traditional managers
When teams, product development and entire organizations move from traditional processes to Agile, we as Managers, have to be prepared for it. It’s a new world where teams are self-organizing, the project has no deadlines, and we as managers are no longer Kings on the Mountaintop.
Leadership and autonomous teams are the buzz-words of today so we as managers have to go through our own agile transformation in order to survive.
Blogpost: https://agileindubai.com/servant-leadership-for-traditional-managers/
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
UX Lessons from the USSR: The Trouble With Manifestos
This document discusses combining different approaches to product development, known as "process bricolage". It advocates embracing diverse methods from Agile, user-centered design (UCD), Lean, and other processes. The author argues against strict adherence to manifestos and for a moderate, pragmatic approach tailored to each project. Examples provided include incorporating UCD research and modeling into Agile sprints, using story maps and minimum viable products, and getting early input from clients.
Drupal As A RESTful Backend For Client Side Applications
This document discusses using Drupal as a RESTful backend for client-side applications. It introduces REST (REpresentational State Transfer) as an architectural style with five primary constraints: client-server, stateless, cacheable, layered system, and uniform interface. The document explains that client-side and mobile applications benefit from RESTful APIs as they can load data asynchronously after loading. It also describes Drupal's Services module for creating RESTful endpoints to integrate external applications and access API data. Specific HTTP methods for creating, retrieving, updating, and deleting resources are outlined. Finally, the document mentions improvements to REST support in Drupal 8 using Symfony components.
Selling Drupal to the Enterprise
Drupal 8 aims to improve its ability to output data in formats like XML and JSON through web services and a RESTful interface. This will allow Drupal to better support delivering content to different devices in varying page layouts tailored for each device. The goal is to make Drupal equally capable of outputting non-HTML formats as it currently is with HTML pages.
More Related Content
What's hot
Agile Anti-patterns
A good anti-pattern has 2 elements:
1. A repeated pattern of action that appears beneficial, but ultimately produces more bad consequences than beneficial results.
2. A refactored solution exists that has been proven in actual practice and is repeatable.
So, what are common pitfalls that new (or even experienced) agile practitioners fall into? Learning about and watching out for these anti-patterns is a great way to inspect and adapt your agile practice.
Coaching Anti-Pattens and common smells
Sekhar Burra is an agile transformation coach who has led two large-scale agile transformations. He has experience as an executive agile coach, scrum master, product owner, and engineering manager. The document discusses a scenario where a coach provides feedback to a client about improving their daily stand-ups by addressing the three standard questions. It then defines what patterns and anti-patterns are in the context of agile development before giving examples of common anti-patterns and smells like having no retrospectives or one team member dominating planning meetings. Coaching techniques for addressing anti-patterns at the team and organizational level are discussed, including learning design patterns and using mocks, Jutta Eckstein's perspectives, and retrospective
Building A devopsy Team
This document provides tips for growing a devops team by breaking down historical silos between development and operations. It recommends starting by analyzing pain points, creating a cross-functional team with shared goals, improving communication, getting buy-in, automating processes, measuring success and failure, and giving everyone full access and responsibilities. The overall message is that devops requires cultural and process changes, not buying products, and is a continuous improvement journey.
Why is it so hard? Agile adoption anti-patterns, how to spot them and what to...
This document discusses common agile adoption anti-patterns that organizations should avoid, and presents positive patterns to follow instead. Some anti-patterns discussed include thinking there is a "perfect system", not fully committing to agile and wanting to do other things first, trying to measure and compare teams' performance numbers, thinking there is a single road to success, and focusing only on maximizing productivity. The document recommends focusing on people's interactions, understanding how the organization really works, seeking support and feedback, keeping business outcomes as the focus, allowing experimentation, and recognizing that learning and idle time are important.
Scrum values
The document discusses the five core values of Scrum: focus, courage, openness, commitment, and respect. It explains that these values are important for the health and success of Scrum teams. Focus values concentrating efforts on a few important tasks at a time to deliver work sooner. Courage values undertaking challenges and admitting imperfections with transparency. Openness values openly expressing concerns and collaborating. Commitment values having control over work with dedication to quality, collaboration, learning, and goals. Respect values regarding others with diverse backgrounds and opinions to strengthen the team.
Practical agile TechExeter
- Land Registry registers land ownership in England and Wales and has transitioned from a traditional to a more agile way of building products and services.
- They now take a user-centered approach with user research in each sprint, focus on service design with multi-disciplinary teams, build using microservices and continuous delivery to deploy updates.
- The transition has been challenging and requires clear objectives, executive support, breaking down silos, and ongoing communication but provides benefits like more adaptable and user-focused services.
Scrum in the Enterprise - Making It Work With Distributed Teams - Liz Heier
Liz Heier discusses how to implement Scrum successfully with distributed teams across multiple locations. She emphasizes that it requires having the right process, the right people, and the right tools. For the process, she recommends estimating backlogs, identifying minimum viable products, and using burn-up charts to monitor scope. For people, key roles include the Scrum Master, Product Owner, and development team. Effective communication across all teams is also important. For tools, she suggests using project management software for documentation, collaboration, code reviews, and ensuring transparency. With the right approach in these three areas, Scrum can be implemented effectively even with remote and distributed teams.
Being vs Doing agile
Most of the times I have seen the teams spending immense amount of time in mastering the mechanics than the intent.
Key to successful agile adoption is to have the agile as a team culture than just doing it
The Scrum Master Balance
In this presentation, we explore the concept of “process authority” as it relates to Scrum Masters and consider the various directions it takes us. To do that, this discussion goes far beyond a typical “the role of a Scrum Master” presentation; It explores…
• What it should (and should not) mean when/if “process authority” is used to describe the Scrum Master role
• How the responsibility and expectations of a Scrum Master are different than that of team members
• How different leadership styles play into understanding the role of the Scrum Master
• The importance of trust in a Scrum Master/team relationship
Lean Scaling – From Lean Startup to Lean Enterprise - Itamar Goldminz
Congratulations! You've found the right product-market fit, and it's now time to scale your business. But growing your organization often means slower decision making, increased complexity, and higher chance for misalignments. How can you grow your business while staying lean? Learn five key lessons on how to use smart integration and process to grow with your Atlassian tools.
Overcome the 6 Antipatterns of Agile Adoption
Presented at Global Scrum Gathering Orlando 2016
Because of benefits like predictability, better quality of products, and faster delivery, many companies have adopted or in the process of adopting Agile. However, there are challenges.
David Hawks, CST and Agile Evangelist, explains the common antipatterns of Agile adoption.
The Soup Stone - Catalyst to Agile Adoption
The document is a presentation about introducing agile practices. It begins with an introduction and overview of the presenter and scope of ScrumUP. It then tells a fairytale in three parts about a soup stone to illustrate introducing change. In between the fairytale parts are sections on models for change including the Rightshifting Model and Elephant and Rider model. It includes an exercise for participants to discuss introducing an agile practice to their team using the models. It closes by requesting evaluation of the presentation.
Collaboration is More Than Communication – JIRA Agile - Xavier Morera
Collaboration is defined as "the action of working with someone to produce or create something." Yet, many confuse communicating with collaborating. True collaboration gives you and your project an edge by aligning efforts towards a clear objective. I'll show how teams can achieve true collaboration with JIRA Agile.
Thats not my agile - Agile on the beach 2017
The document discusses challenges with adopting agile practices within large organizations and provides advice on overcoming those challenges. It recommends focusing on users and outcomes rather than strict adherence to processes. Small, fixed cross-functional teams are important to allow autonomy and build trust. Metrics should celebrate successes and identify problems to address rather than constrain teams. Leadership support is key to enabling a culture of trust and continuous learning over rigid processes.
Scrum101
This document provides an overview of Scrum, an agile framework for managing product development. It discusses the Scrum roles of Product Owner, Team, and Scrum Master. The key Scrum ceremonies are planning, daily stand-ups, sprint reviews, and retrospectives. Scrum uses short iterations called sprints to incrementally deliver working software. The document recommends starting with a short initial sprint length and identifying the Product Owner, Scrum Master, and cross-functional Team.
Scrum Shock Therapy: Going Back to Basics - Atlassian Summit 2012
The document discusses using "Scrum shock therapy" to transition a team from Kanban to Scrum by imposing strict rules like one-week sprints and fully estimating all work upfront. This caused pain for the team initially. Key learnings included the importance of good retrospectives and that physical card walls can improve communication but are hindrances to remote work. Barriers to agile adoption include a lack of automation and buy-in from the whole team. In the end, strict rules may only work for very dysfunctional teams and discipline is better achieved through other means.
Core Agility Workout - AgileIndy 2015
The document describes an agile workout consisting of three exercises to demonstrate agile principles. The first exercise shows that individuals are more efficient completing one task at a time rather than multitasking. The second exercise demonstrates that reducing batch sizes decreases overall completion time. The third exercise finds that self-organizing teams perform better than manager-led teams at solving problems. The exercises are intended to help internalize agile concepts such as eliminating waste, rapid delivery, and self-organizing teams.
Servant Leadership for traditional managers
When teams, product development and entire organizations move from traditional processes to Agile, we as Managers, have to be prepared for it. It’s a new world where teams are self-organizing, the project has no deadlines, and we as managers are no longer Kings on the Mountaintop.
Leadership and autonomous teams are the buzz-words of today so we as managers have to go through our own agile transformation in order to survive.
Blogpost: https://agileindubai.com/servant-leadership-for-traditional-managers/
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
What's hot (19)
Why is it so hard? Agile adoption anti-patterns, how to spot them and what to...
Why is it so hard? Agile adoption anti-patterns, how to spot them and what to...
Scrum in the Enterprise - Making It Work With Distributed Teams - Liz Heier
Scrum in the Enterprise - Making It Work With Distributed Teams - Liz Heier
Lean Scaling – From Lean Startup to Lean Enterprise - Itamar Goldminz
Lean Scaling – From Lean Startup to Lean Enterprise - Itamar Goldminz
Collaboration is More Than Communication – JIRA Agile - Xavier Morera
Collaboration is More Than Communication – JIRA Agile - Xavier Morera
Scrum Shock Therapy: Going Back to Basics - Atlassian Summit 2012
Scrum Shock Therapy: Going Back to Basics - Atlassian Summit 2012
Viewers also liked
UX Lessons from the USSR: The Trouble With Manifestos
This document discusses combining different approaches to product development, known as "process bricolage". It advocates embracing diverse methods from Agile, user-centered design (UCD), Lean, and other processes. The author argues against strict adherence to manifestos and for a moderate, pragmatic approach tailored to each project. Examples provided include incorporating UCD research and modeling into Agile sprints, using story maps and minimum viable products, and getting early input from clients.
Drupal As A RESTful Backend For Client Side Applications
This document discusses using Drupal as a RESTful backend for client-side applications. It introduces REST (REpresentational State Transfer) as an architectural style with five primary constraints: client-server, stateless, cacheable, layered system, and uniform interface. The document explains that client-side and mobile applications benefit from RESTful APIs as they can load data asynchronously after loading. It also describes Drupal's Services module for creating RESTful endpoints to integrate external applications and access API data. Specific HTTP methods for creating, retrieving, updating, and deleting resources are outlined. Finally, the document mentions improvements to REST support in Drupal 8 using Symfony components.
Selling Drupal to the Enterprise
Drupal 8 aims to improve its ability to output data in formats like XML and JSON through web services and a RESTful interface. This will allow Drupal to better support delivering content to different devices in varying page layouts tailored for each device. The goal is to make Drupal equally capable of outputting non-HTML formats as it currently is with HTML pages.
Coding For Config: Install Profile Development Using Features
This document provides an overview of how to create an install profile in Drupal. It discusses the key files and folders needed, including .info, .profile, .install files to define the profile. It also covers make files needed to build the profile and dependencies, as well as example code for common tasks in install hooks like enabling modules, setting variables, populating menus and vocabularies.
Open Advocacy - Citizens Connected Goes Open Source
The document invites citizens to a code sprint on December 7-8 in Toronto to work on open sourcing the Citizens Connected project and its Drupal modules for civic engagement and advocacy. It outlines the agenda which includes introducing Citizens Connected (CitCon), discussing its future as an open source project, comparing its Drupal modules, highlighting key features, and what remains to be done. Attendees are encouraged to come to the code sprint to contribute.
DataPublic: Building Drupal-Powered Open Government (Nik Garkusha, Microsoft ...
Slides from Nik Garkusha, Open Platforms Lead at Microsoft Canada. Presented at the 2012 Toronto Drupal Business Summit.
How to incrementally integrate QA in an Agile Development Process
This document outlines an incremental approach to QA that combines elements of QA, agile practices, and automation. It emphasizes valuing individuals, working software, customer collaboration, and response to change over rigid processes, documentation, contracts, and plans. The approach involves embedding QA specialists within cross-functional teams to collaboratively develop high-quality software through open discussion.
Viewers also liked (7)
UX Lessons from the USSR: The Trouble With Manifestos
UX Lessons from the USSR: The Trouble With Manifestos
Drupal As A RESTful Backend For Client Side Applications
Drupal As A RESTful Backend For Client Side Applications
Coding For Config: Install Profile Development Using Features
Coding For Config: Install Profile Development Using Features
Open Advocacy - Citizens Connected Goes Open Source
Open Advocacy - Citizens Connected Goes Open Source
DataPublic: Building Drupal-Powered Open Government (Nik Garkusha, Microsoft ...
DataPublic: Building Drupal-Powered Open Government (Nik Garkusha, Microsoft ...
How to incrementally integrate QA in an Agile Development Process
How to incrementally integrate QA in an Agile Development Process
Similar to Agile 101
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.
Mujeebur rahmansaher introduction-to-scrum_v2
This document provides an overview of Scrum, an agile software development framework. It discusses key Scrum concepts like the agile manifesto, roles, ceremonies, and artifacts. The Scrum framework uses short iterations called sprints to incrementally develop working software. It emphasizes self-organizing cross-functional teams, prioritized backlogs, and frequent inspection and adaptation to respond to changes. Surveys find that most organizations using Scrum see benefits like increased productivity, collaboration, and satisfaction over traditional waterfall approaches.
SDEC15: Help the Scrum Master *IS* the Impediment
Talk on how scrum masters can avoid becoming impediments to their agile teams. Presented at SDEC 2015.
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.
Jeff Lopez - To Affinity and Beyond
The document describes a workshop that demonstrates affinity mapping techniques for agile planning. It will show how to quickly generate, estimate, prioritize and evaluate a product backlog through affinity consensus. Attendees will learn techniques like dot voting, grouping and relative sizing. Exercises will guide participants in creating user stories, estimating effort and determining value through affinity facilitation. The goal is to reduce waste and allow for fast decision making through these visual and collaborative techniques.
Jeff Lopez - To Affinity and Beyond
Jeff Lopez Presentation for Agile Impact Conference 2018 Day 1.
"Learn speedy affinity facilitation techniques to eliminate waste and boost productivity in creating, prioritizing and estimating a backlog."
ScrumRio 2016 - Improving Scrum with Lean Thinking
– What's Lean?
– Why use Lean Thinking to drive your organization towards sustainable growth?
– What's the connection between Lean and Scrum?
– How can we improve Scrum with Lean Thinking?
This is an improved version of the same session given at Agile Portugal 2016 :-)
– Once upon a time…
– “Vanilla” Scrum
– Lean Thinking
– The Toyota Way
– Toyota Thinking
– Value
– Waste
– Learning Cycles
– Scrum, from a Lean view
– Scrum + Lean Thinking
Agility2020 key takeaways
This document summarizes key takeaways from the Agility 2020 conference. It discusses topics like achieving business agility, how companies like Blockbuster failed to adapt to digital disruption, and the importance of moving business functions like finance in an agile direction. Other topics covered include using visualizations to enhance communication, impact mapping, applying mindfulness in agile teams, DevOps practices at Persistent, and how games can be used to teach agility principles. The document provides examples and lessons learned from each topic.
How to make your retrospectives the heart of your agile proces
The slides from my talk at WebExpo about how to make your retrospectives the heart of your agile proces
Xebia5ways eu women2
This presentation was given at European Women in Agile 2018. It is an interactive session based upon the principles from Sharon Bowman.
Agile Retrospectives
The document provides guidance on how to conduct effective retrospectives for agile teams. It discusses principles behind agile processes and retrospectives from the Agile Manifesto. It emphasizes that retrospectives should be a check-in rather than post-mortem, focus on learning and improvement rather than blame. Various techniques are presented for designing effective retrospectives, including setting goals, using timeboxes, gathering feedback, identifying themes for improvement, and planning actions to implement lessons learned. Common "smells" or issues that can undermine retrospectives are also identified.
Retrospective & review
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
Agile Retrospective & review
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
The Slippery Slope
This document discusses how teams can unintentionally slip away from Agile practices over time if they are not careful. It provides examples of common "slippery slopes" such as skipping story estimation, not using relative sizing, carrying stories between sprints, and stopping daily standups. The author urges coaches to focus on helping teams form good habits in the first 3-6 months and celebrate successes while also constructively pointing out areas for improvement. Teams are reminded that Agile requires discipline and that changing habits is difficult, so they should avoid picking up bad practices.
Successful Agile Transformation - Jim Grundner - Agile Maine
This document discusses essential patterns for successful agile transformations. It emphasizes the importance of leadership commitment, forming a cross-functional transformation team, and having an adoption strategy such as piloting agile with a small team. It also recommends focusing on empowering teams, limiting work in progress, using metrics to encourage the right behaviors, and embracing an experimental mindset to continuously learn and improve.
Scrum and-xp-from-the-trenches 08 distributed teams & scrum master checklist
This document summarizes strategies for handling distributed and remote teams when using Scrum. It discusses maximizing communication bandwidth between remote team members through tools like video conferencing and pair programming. When offshoring teams, it recommends initially having separated team members rather than fully separated teams. It also provides guidelines for team members working remotely or from home. Finally, it outlines a Scrum Master checklist for the beginning, during, and end of each sprint and emphasizes empowering the self-organizing team over time.
Scrum
Scrum is an agile framework that focuses on iterative development through short cycles called sprints. There are three main roles: the product owner prioritizes features and communicates with stakeholders, the development team implements the features, and the scrum master facilitates the process and removes impediments. Key aspects of scrum include daily stand-up meetings to track progress, prioritized backlogs to plan sprints, and retrospectives after each sprint to improve. The goal is to frequently deliver working software and adapt quickly to changes.
Practical Scrum - day 1
This document provides an overview of practical scrum. It discusses the three scrum roles of product owner, scrum master, and team. It also describes the four scrum ceremonies and three artifacts. Key principles of scrum include self-organizing teams, empirical process, and delivering working software frequently. The document contrasts command-and-control with self-management and explains how the manager's role changes in an agile environment.
Agile Portugal 2016 - Improving Scrum with Lean Thinking
– What's Lean?
– Why use Lean Thinking to drive your organization towards sustainable growth?
– What's the connection between Lean and Scrum?
– How can we improve Scrum with Lean Thinking?
This is my first attempt on trying "to put on paper" my past hands-on experiences and learnings :-)
– Once upon a time…
– “Vanilla” Scrum
– Lean Thinking
– The Toyota Way
– Toyota Thinking
– Value
– Waste
– Learning Cycles
– Scrum, from a Lean view
– Scrum + Lean Thinking
GAC - Scrum Master Training
The document provides information about a Scrum Master position with Gulf Agency Company. It discusses the Scrum Master role and responsibilities, including promoting Scrum values and processes, removing impediments for the team, and facilitating ceremonies like the Daily Scrum and Sprint Planning. It also describes qualities of an effective Scrum Master like being a servant leader, having strong facilitation skills, and helping the Product Owner, team, and organization implement Scrum.
Similar to Agile 101 (20)
ScrumRio 2016 - Improving Scrum with Lean Thinking
ScrumRio 2016 - Improving Scrum with Lean Thinking
How to make your retrospectives the heart of your agile proces
How to make your retrospectives the heart of your agile proces
Successful Agile Transformation - Jim Grundner - Agile Maine
Successful Agile Transformation - Jim Grundner - Agile Maine
Scrum and-xp-from-the-trenches 08 distributed teams & scrum master checklist
Scrum and-xp-from-the-trenches 08 distributed teams & scrum master checklist
Agile Portugal 2016 - Improving Scrum with Lean Thinking
Agile Portugal 2016 - Improving Scrum with Lean Thinking
More from Myplanet Digital
Drupal With SMS And Telephony For Fun And Profit
This document summarizes opportunities for integrating SMS and VoIP capabilities into Drupal websites. It discusses:
1) Popular SMS and VoIP use cases like direct marketing, event organization, and reducing infrastructure costs.
2) Benefits of integrating these services like accessing existing data, automation, and ability to store data.
3) The current state of Drupal 7 modules for SMS and VoIP integration, and opportunities to build custom modules using the Twilio API.
4) Examples of apps the author has built using a custom Twilio module, including a party planning app and a door buzzer app.
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And G...
This document provides 101 tips for getting the website you need while saving time and money. Some key tips include having clearly defined objectives focused on business goals and ROI, being open to vendor ideas, prioritizing quickly, and demanding accountability and demos from vendors. It also discusses using agile principles like valuing working software over documentation and responding quickly to changes. The overall message is to plan effectively, communicate constantly with vendors, and focus on business needs and outcomes above all else.
Stumbling Your Way to Succes: A Myplanet Tale
Myplanet CEO & Director Jason Cottrell presented this keynote address at Markham's Small Business Forum 2012.
Learning from Shopkeepers: Content Strategy for eCommerce
This presentation was created and delivered by Nate Archer, Content Strategy Specialist at Myplanet Digital.
Adaptive Content: Designing For The Unknown
This document discusses the importance of designing content to be adaptive and responsive. It recommends structuring content into chunks and using metadata to make it flexible across different devices and contexts. Content should be technology agnostic and work in any environment. Structured and meaningful content that is created once can be published everywhere, keeping organizations flexible to meet changing user needs.
Responsive Design: Drupal Business Summit (Erik von Stackelberg, Myplanet Dig...
Slides from Erik von Stackelberg, Creative Director at Myplanet Digital. Presented at the 2012 Drupal Business Summits in Toronto, Chicago & NYC.
Capturing Community (Michael Silverman, Duo Consulting)
Slides from Michael Silverman, Founder & CEO of Duo Consulting. Presented at the 2012 Drupal Business Summits in Toronto, Chicago & NYC.
Open Source at The ROM
This document contains a list of proposed new pages and content for the museum's website, organized by section. It includes proposed page URLs, existing content, new content to be added, estimated word counts, priorities, and notes. Sections include Exhibitions & Galleries, with subsections for specific galleries, as well as World Cultures galleries. Marketing will be involved in content development for some pages. The document provides an overview of planned new and updated content for the museum website.
Case Study: Drupal Enabled Mobile -Ontario Physical Health Education Associat...
The document discusses how Ophea, a nonprofit organization supporting children's health in Ontario, transitioned from a legacy system with multiple disconnected tools to a Drupal-based solution. It outlines challenges with the old system like silos of information and high maintenance costs. The new Drupal platform provides a unified CMS, ecommerce capabilities, and standardized program sites. Future plans include responsive mobile applications, social media integration, and content strategies to better organize and deliver information.
Gerry Dimnik's RCM Case Study-DBS 2011
The Royal Conservatory provides music and arts education to over 5 million students nationwide. It is launching a new digital initiative called myDigitalRCM to create an online community for students, teachers, and patrons. This will include social networking, digital marketing, online learning, and distributing multimedia content. The Royal Conservatory is selecting Drupal as its new content management platform to power this digital transformation and achieve its vision of being interactive, relevant, and connecting its community.
Benoit Marchand's BMO Case Study-DBS 2011
This document summarizes BMO's implementation of a Drupal-based community platform to support its online initiatives. It discusses BMO's business needs, including a unified platform for communities, content sharing, and flexibility. It describes how Drupal met these needs with features like multisite setup and reusable functionality. The platform launched on time and facilitated new sites. BMO has observed the implementation and identified next steps like integrating new sites and mobile.
Sean Crowley's Government Talk-DBS 2011
This document summarizes information about Acquia and Drupal adoption in government. It discusses that Acquia has 170 employees and supports Drupal through subscription services, hosting, and a partner program. It also notes that Drupal powers over 2% of websites and has been adopted by many governments around the world, including examples from Canada.
More from Myplanet Digital (12)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And G...
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And G...
Learning from Shopkeepers: Content Strategy for eCommerce
Learning from Shopkeepers: Content Strategy for eCommerce
Responsive Design: Drupal Business Summit (Erik von Stackelberg, Myplanet Dig...
Responsive Design: Drupal Business Summit (Erik von Stackelberg, Myplanet Dig...
Capturing Community (Michael Silverman, Duo Consulting)
Capturing Community (Michael Silverman, Duo Consulting)
Case Study: Drupal Enabled Mobile -Ontario Physical Health Education Associat...
Case Study: Drupal Enabled Mobile -Ontario Physical Health Education Associat...
Recently uploaded
AppSec PNW: Android and iOS Application Security with MobSF
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Principle of conventional tomography-Bibash Shahi ppt..pptx
before the computed tomography, it had been widely used.
Astute Business Solutions | Oracle Cloud Partner |
Your goto partner for Oracle Cloud, PeopleSoft, E-Business Suite, and Ellucian Banner. We are a firm specialized in managed services and consulting.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Essentials of Automations: Exploring Attributes & Automation Parameters
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...Pitangent Analytics & Technology Solutions Pvt. Ltd
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.Northern Engraving | Nameplate Manufacturing Process - 2024
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
The Microsoft 365 Migration Tutorial For Beginner.pptx
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Recently uploaded (20)
AppSec PNW: Android and iOS Application Security with MobSF
AppSec PNW: Android and iOS Application Security with MobSF
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Principle of conventional tomography-Bibash Shahi ppt..pptx
Principle of conventional tomography-Bibash Shahi ppt..pptx
Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
Essentials of Automations: Exploring Attributes & Automation Parameters
Essentials of Automations: Exploring Attributes & Automation Parameters
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Northern Engraving | Nameplate Manufacturing Process - 2024
Northern Engraving | Nameplate Manufacturing Process - 2024
The Microsoft 365 Migration Tutorial For Beginner.pptx
The Microsoft 365 Migration Tutorial For Beginner.pptx
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Agile 101
- 3. Myplanet values… • Innovation • Humanity • Transparency • Focus • Excellence
- 4. Agile An Introduction David Sabine Shanly Suepaul
- 5. Agile.
- 8. The Agile Manifesto • Individuals and interactions – Over processes and tools • Working product or service – Over comprehensive documentation • Customer collaboration – Over contract negotiation • Responding to change – Over following a plan
- 10. The client's relationship with Myplanet. Production Our Production Teams work with you to groom your product backlog and create the product in increments known as Sprints. Our BizDev Group facilitates initial discussions and helps you develop your Agile project charter. Engagement Support Our Strategy & Support Group maintains/supports your product and guides continual improvements.
- 11. Product lifecycle. Sprints The team will timebox their work into short “Sprints” and deliver viable product every Sprint. Your Product Owner will work continuously with you to groom the Product Backlog throughout the project. Our specialists and your new “Product Owner” will work with you to understand the vision for the project and to establish first priorities in the “Product Backlog”. Release Plan Project Plan Release The Product Owner and Team will transition the product to our Strategy & Support Group for ongoing support, study, and improvement.
- 12. Sprints. Work Cycles After the Team makes a commitment to their “Sprint Backlog”, the team works in short cycles with frequent progress meetings (called “Daily Scrums”). The team knows its velocity and they know how much work they can commit to finishing each Sprint. They study the items at the top of the Product Backlog, split the items into tasks, and begin their work. Sprint Plan Demo At the end of each Sprint, the Team will demonstrate the results of their work and ask for feedback from stakeholders. Backlog Grooming
- 13. + Adapt Inspect
- 22. Everybody Scrum.
- 23. I want to play a game.
- 24. Penny game • The object of the game is to be the fastest team to process your pennies. • Pennies are processed when they are flipped five times. • There is a "starter" who can take pennies from the pile and flip them once. • Once the starter has flipped all the pennies once, they can all be passed on to the next team member, who must also flip all the pennies once. Rinse/repeat.
- 25. Penny game • Now, the starter can pass individual pennies as soon as they are flipped once (they don't all have to be flipped before being passed.)
- 26. Penny game • Now, anyone can take and flip the coins five times themselves.
- 27. Scrum • Scrum is a very simple system • Five values • Three artifacts, three ceremonies, three roles
- 30. Ceremonies Roles High Performance • Prioritized Product Backlog • Sprint Backlog • Burndown Chart Artifacts
- 32. • Stand up • Planning • Retrospective / Demo Ceremonies Roles High performance Artifacts
- 34. • Team member • Product Owner • ScrumMaster Ceremonies Roles High performance Artifacts
- 35. + Sprints are like this: 35 Work Standups How many of the top Product Backlog Items will we commit to doing and how will we accomplish them? Planning Ship Retrospect Potentially shippable product.
- 36. The development lifecycle looks like this: