Scrum by picture
•Download as PPTX, PDF•
4 likes•1,808 views
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.
Report
Share
Report
Share
Recommended
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.
Do better-scrum
This document provides an overview of Scrum roles and events. It describes the three main Scrum roles: Product Owner, Development Team, and Scrum Master. The Product Owner is responsible for maximizing ROI by prioritizing the backlog and helping the team understand what to build. The cross-functional Development Team, consisting of 3-9 members, is responsible for delivering working increments each sprint. The Scrum Master helps the team follow Scrum practices and removes impediments. The document also briefly outlines the Scrum events of the Sprint, Sprint Planning Meeting, Daily Scrum, Sprint Review and Sprint Retrospective.
2020 scrum-guide | The Definitive Guide to Scrum: The Rules of the Game
This document provides an overview of the Scrum framework for project management. It defines Scrum and its core components: roles (Product Owner, Development Team, Scrum Master), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment). It describes how Scrum uses an empirical, iterative process based on transparency, inspection, and adaptation to manage complex work. The document serves as a guide for using Scrum and was developed by its creators, Ken Schwaber and Jeff Sutherland.
Scrum master vs agile coach difference explained
Scrum Master vs Agile Coach: Know the key differences between Scrum Master and Agile Coach. Also, understand the roles & responsibilities of both approaches.
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.
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.
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.
Scrum Gathering Shanghai - April 2010
This was my keynote speech at the the Scrum Gathering in Shanghai, 2010. it's about the use of Scrum with the XP technical practices.
Recommended
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.
Do better-scrum
This document provides an overview of Scrum roles and events. It describes the three main Scrum roles: Product Owner, Development Team, and Scrum Master. The Product Owner is responsible for maximizing ROI by prioritizing the backlog and helping the team understand what to build. The cross-functional Development Team, consisting of 3-9 members, is responsible for delivering working increments each sprint. The Scrum Master helps the team follow Scrum practices and removes impediments. The document also briefly outlines the Scrum events of the Sprint, Sprint Planning Meeting, Daily Scrum, Sprint Review and Sprint Retrospective.
2020 scrum-guide | The Definitive Guide to Scrum: The Rules of the Game
This document provides an overview of the Scrum framework for project management. It defines Scrum and its core components: roles (Product Owner, Development Team, Scrum Master), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment). It describes how Scrum uses an empirical, iterative process based on transparency, inspection, and adaptation to manage complex work. The document serves as a guide for using Scrum and was developed by its creators, Ken Schwaber and Jeff Sutherland.
Scrum master vs agile coach difference explained
Scrum Master vs Agile Coach: Know the key differences between Scrum Master and Agile Coach. Also, understand the roles & responsibilities of both approaches.
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.
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.
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.
Scrum Gathering Shanghai - April 2010
This was my keynote speech at the the Scrum Gathering in Shanghai, 2010. it's about the use of Scrum with the XP technical practices.
Scrum master as a servant leader for the scrum team (2)
How can Scrum Master as a Servant Leader make a Significant Difference in Agile Software Development? Learn about the various roles relevant for Scrum Masters.
Scrum training-manual 1
The training offers an overview of Agile development and Scrum practices, focusing on how the Scrum framework follows the Agile Manifesto principles. ... The Scrum framework uses simple iterative practices for team collaboration on complex projects.
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.
QCon Beijing - April 2010
The document discusses technical debt in software development. It defines technical debt as deferred work that accumulates when high quality standards are not enforced or corners are cut to achieve velocity targets. This debt makes code complex and hard to change, reducing a team's ability to meet business needs. The document recommends practices like continuous integration, test-driven development, and refactoring to avoid debt. It also discusses strategies for identifying and paying off existing debt over time.
Agile Training - Scrum 101
Scrum is a popular agile framework that helps development teams deliver value in small increments, typically 30 days or less, through short sprints. It provides a flexible framework for self-organizing teams to focus on delivering working software frequently. Key roles in Scrum include the product owner who prioritizes backlog items, the Scrum master who facilitates the process, and cross-functional teams of 7 plus or minus 2 members who are responsible for delivering working increments of software.
Welcome to SCRUM
The document provides an overview of how the Scrum process will be used within a software development lifecycle and project. Scrum is an agile methodology that uses iterative increments to optimize predictability and control risk. It has three pillars: transparency, inspection, and adaptation. The key Scrum roles are the Scrum Master, Product Owner, and Development Team. Sprints include planning meetings, daily stand-ups, reviews, and retrospectives. Scrum integrates into the project lifecycle at various stages from requirements to testing. Work items and traceability between artifacts will be managed in Visual Studio Team Services.
Scrum Model
Scrum is an agile framework for managing projects developed by Jeff Sutherland in 1993 based on earlier work. It uses short "sprints" to iteratively develop work items prioritized in a backlog. Key roles include the Product Owner who prioritizes the backlog, the Scrum Master who facilitates the process, and the cross-functional Scrum Team. Each sprint involves planning, daily stand-ups, development, review, and retrospective. The process is intended to be flexible and transparent compared to traditional sequential models like waterfall.
Scrum - An Agile Approach to Software Product Development
This document provides an overview of the Scrum framework for agile software development. Scrum uses short development cycles called sprints (typically 2-4 weeks) to incrementally develop a product. Key Scrum roles include the Product Owner who represents stakeholders, the Scrum Master who facilitates the process, and the self-organizing development team. The team works through a backlog of prioritized product features to complete as many as possible in a sprint. Daily stand-up meetings allow the team to synchronize and the Product Owner to provide feedback and prioritize new items. At the end of each sprint, completed work is reviewed and the process repeats with re-prioritized backlogs.
Agile Engineering Practices
1. Agile engineering practices like continuous integration, test-driven development, refactoring, and pair programming can help software teams build higher quality code more efficiently.
2. Continuous integration involves developers integrating code changes frequently through automated builds and tests to quickly detect errors.
3. Test-driven development uses short development cycles where developers write automated tests before code and refactor code to maintain test coverage.
Illuminating scrum by comparing LEsS with safe - Rowan Bunning
The document discusses scaling Scrum frameworks like SAFe and LeSS. It begins by noting the unrealized potential of Scrum when adopted shallowly only at the team level rather than considering its deeper implications. The speaker will discuss key differences between SAFe and LeSS, including their applicability, team structures, and approaches to coordination. The main point is that Scrum's potential is maximized by questioning why each element exists and ensuring the same purpose at larger scales, as LeSS does, rather than containing Scrum as a building block as in SAFe.
Solit 2014, Scrum guide 2013, Семенченко Антон
Антон Семенченко, опыт в IT более 10 лет, работает в компании ISSoft, специализируется в разработке и автоматизированном тестировании ПО плюс менеджмент\продажи. C++ Architect, Automation Practice Lead, PM, Group Manager
«Agile ValueTeam, учимся понимать Scrum». IT секция. Agile отделение. Для всех уровней подготовки.
«Как эффективно продавать Automation Service». IT секция. Продажи.
«Как эффективно организовать Автоматизацию, если у вас недостаточно времени, ресурсов и денег». Development секция. Отделение тестирования.
Game of SCRUM & VSM
Research Presentation: Why consequently practiced SCRUM constitutes itself inherently as a viable system.
Furthermore it shows that enterprise wide SCRUM is a feasible approach.
Metaphorum 2016, Leeds
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.
SCRUM Master
The document describes a Scrum Master certification course offered by BOOSTurSKILLS. The 3-day course provides training on Scrum framework and methodology. It covers Scrum roles, processes, artifacts like product backlog, sprints, and meetings. The course structure includes lectures, exercises and mock tests. Upon completion, participants receive a 24 contact hour certificate to help with other certifications and professional development units.
Scrumprimer20
This document provides an overview of Scrum, an agile framework for project management. It describes key Scrum roles like the Product Owner, Development Team, and Scrum Master. It also outlines Scrum artifacts such as the Product Backlog, which is a prioritized list of features and requirements. Sprints are short, timed iterations where a cross-functional team selects Product Backlog items to complete. Daily stand-ups, Sprint planning, reviews and retrospectives are meetings that occur within the Scrum process. The document emphasizes inspecting and adapting work through these meetings to maximize value delivery.
Scaling agile using SOS
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)
Scrum difficulties
The document summarizes the challenges faced by a team transitioning from a waterfall methodology to an agile methodology. Some of the major stumbling blocks included inertia to change, a lack of discipline around meeting times and structures, unclear roles and responsibilities, and not properly understanding agile principles like self-organization and empiricism. It took several pilots, training sessions, and ongoing coaching for the team to fully adopt agile practices and see benefits like improved customer satisfaction and fewer bugs.
What does a Scrum Master do, or should do, all day?
A Scrum Master facilitates the Scrum process, creates rhythm and sets expectations for projects and team members. They facilitate daily stand-ups and meetings, enhance communication, and act as an approachable coach through 1:1 meetings and active listening. Scrum Masters also train teams, products, and the organization on Agile practices.
Scrum in 15 Minutes
Introduction to Scrum - A quick overview presenting the main concepts. Useful to make small presentations about it.
2017 Scrum by Picture
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
Running a Scrum process with Trello
An overview of the tips and techniques for managing you Scrum (or Kanban) process in Trello. This is based on things I've seen teams doing while building http://getcorrello.com - Dasboards for Scrum and Kanban teams using Trello.
Learn Scrum Engineering in 5 minutes
This document provides an overview of Scrum, an agile project management framework. Some key points:
- Scrum uses iterative "Sprints" typically lasting 2-4 weeks to develop software in short cycles. A product backlog is prioritized and tasks are broken down for each Sprint.
- Self-organizing Scrum teams of 5-9 people work to complete the Sprint goals. Daily stand-up meetings provide status updates and help remove impediments.
- At the end of each Sprint, working software is demonstrated and the product owner evaluates progress before prioritizing tasks for the next Sprint.
- Scrum aims to improve productivity, adaptability and creativity compared to
More Related Content
What's hot
Scrum master as a servant leader for the scrum team (2)
How can Scrum Master as a Servant Leader make a Significant Difference in Agile Software Development? Learn about the various roles relevant for Scrum Masters.
Scrum training-manual 1
The training offers an overview of Agile development and Scrum practices, focusing on how the Scrum framework follows the Agile Manifesto principles. ... The Scrum framework uses simple iterative practices for team collaboration on complex projects.
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.
QCon Beijing - April 2010
The document discusses technical debt in software development. It defines technical debt as deferred work that accumulates when high quality standards are not enforced or corners are cut to achieve velocity targets. This debt makes code complex and hard to change, reducing a team's ability to meet business needs. The document recommends practices like continuous integration, test-driven development, and refactoring to avoid debt. It also discusses strategies for identifying and paying off existing debt over time.
Agile Training - Scrum 101
Scrum is a popular agile framework that helps development teams deliver value in small increments, typically 30 days or less, through short sprints. It provides a flexible framework for self-organizing teams to focus on delivering working software frequently. Key roles in Scrum include the product owner who prioritizes backlog items, the Scrum master who facilitates the process, and cross-functional teams of 7 plus or minus 2 members who are responsible for delivering working increments of software.
Welcome to SCRUM
The document provides an overview of how the Scrum process will be used within a software development lifecycle and project. Scrum is an agile methodology that uses iterative increments to optimize predictability and control risk. It has three pillars: transparency, inspection, and adaptation. The key Scrum roles are the Scrum Master, Product Owner, and Development Team. Sprints include planning meetings, daily stand-ups, reviews, and retrospectives. Scrum integrates into the project lifecycle at various stages from requirements to testing. Work items and traceability between artifacts will be managed in Visual Studio Team Services.
Scrum Model
Scrum is an agile framework for managing projects developed by Jeff Sutherland in 1993 based on earlier work. It uses short "sprints" to iteratively develop work items prioritized in a backlog. Key roles include the Product Owner who prioritizes the backlog, the Scrum Master who facilitates the process, and the cross-functional Scrum Team. Each sprint involves planning, daily stand-ups, development, review, and retrospective. The process is intended to be flexible and transparent compared to traditional sequential models like waterfall.
Scrum - An Agile Approach to Software Product Development
This document provides an overview of the Scrum framework for agile software development. Scrum uses short development cycles called sprints (typically 2-4 weeks) to incrementally develop a product. Key Scrum roles include the Product Owner who represents stakeholders, the Scrum Master who facilitates the process, and the self-organizing development team. The team works through a backlog of prioritized product features to complete as many as possible in a sprint. Daily stand-up meetings allow the team to synchronize and the Product Owner to provide feedback and prioritize new items. At the end of each sprint, completed work is reviewed and the process repeats with re-prioritized backlogs.
Agile Engineering Practices
1. Agile engineering practices like continuous integration, test-driven development, refactoring, and pair programming can help software teams build higher quality code more efficiently.
2. Continuous integration involves developers integrating code changes frequently through automated builds and tests to quickly detect errors.
3. Test-driven development uses short development cycles where developers write automated tests before code and refactor code to maintain test coverage.
Illuminating scrum by comparing LEsS with safe - Rowan Bunning
The document discusses scaling Scrum frameworks like SAFe and LeSS. It begins by noting the unrealized potential of Scrum when adopted shallowly only at the team level rather than considering its deeper implications. The speaker will discuss key differences between SAFe and LeSS, including their applicability, team structures, and approaches to coordination. The main point is that Scrum's potential is maximized by questioning why each element exists and ensuring the same purpose at larger scales, as LeSS does, rather than containing Scrum as a building block as in SAFe.
Solit 2014, Scrum guide 2013, Семенченко Антон
Антон Семенченко, опыт в IT более 10 лет, работает в компании ISSoft, специализируется в разработке и автоматизированном тестировании ПО плюс менеджмент\продажи. C++ Architect, Automation Practice Lead, PM, Group Manager
«Agile ValueTeam, учимся понимать Scrum». IT секция. Agile отделение. Для всех уровней подготовки.
«Как эффективно продавать Automation Service». IT секция. Продажи.
«Как эффективно организовать Автоматизацию, если у вас недостаточно времени, ресурсов и денег». Development секция. Отделение тестирования.
Game of SCRUM & VSM
Research Presentation: Why consequently practiced SCRUM constitutes itself inherently as a viable system.
Furthermore it shows that enterprise wide SCRUM is a feasible approach.
Metaphorum 2016, Leeds
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.
SCRUM Master
The document describes a Scrum Master certification course offered by BOOSTurSKILLS. The 3-day course provides training on Scrum framework and methodology. It covers Scrum roles, processes, artifacts like product backlog, sprints, and meetings. The course structure includes lectures, exercises and mock tests. Upon completion, participants receive a 24 contact hour certificate to help with other certifications and professional development units.
Scrumprimer20
This document provides an overview of Scrum, an agile framework for project management. It describes key Scrum roles like the Product Owner, Development Team, and Scrum Master. It also outlines Scrum artifacts such as the Product Backlog, which is a prioritized list of features and requirements. Sprints are short, timed iterations where a cross-functional team selects Product Backlog items to complete. Daily stand-ups, Sprint planning, reviews and retrospectives are meetings that occur within the Scrum process. The document emphasizes inspecting and adapting work through these meetings to maximize value delivery.
Scaling agile using SOS
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)
Scrum difficulties
The document summarizes the challenges faced by a team transitioning from a waterfall methodology to an agile methodology. Some of the major stumbling blocks included inertia to change, a lack of discipline around meeting times and structures, unclear roles and responsibilities, and not properly understanding agile principles like self-organization and empiricism. It took several pilots, training sessions, and ongoing coaching for the team to fully adopt agile practices and see benefits like improved customer satisfaction and fewer bugs.
What does a Scrum Master do, or should do, all day?
A Scrum Master facilitates the Scrum process, creates rhythm and sets expectations for projects and team members. They facilitate daily stand-ups and meetings, enhance communication, and act as an approachable coach through 1:1 meetings and active listening. Scrum Masters also train teams, products, and the organization on Agile practices.
What's hot (18)
Scrum master as a servant leader for the scrum team (2)
Scrum master as a servant leader for the scrum team (2)
Scrum - An Agile Approach to Software Product Development
Scrum - An Agile Approach to Software Product Development
Illuminating scrum by comparing LEsS with safe - Rowan Bunning
Illuminating scrum by comparing LEsS with safe - Rowan Bunning
What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day?
Viewers also liked
Scrum in 15 Minutes
Introduction to Scrum - A quick overview presenting the main concepts. Useful to make small presentations about it.
2017 Scrum by Picture
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
Running a Scrum process with Trello
An overview of the tips and techniques for managing you Scrum (or Kanban) process in Trello. This is based on things I've seen teams doing while building http://getcorrello.com - Dasboards for Scrum and Kanban teams using Trello.
Learn Scrum Engineering in 5 minutes
This document provides an overview of Scrum, an agile project management framework. Some key points:
- Scrum uses iterative "Sprints" typically lasting 2-4 weeks to develop software in short cycles. A product backlog is prioritized and tasks are broken down for each Sprint.
- Self-organizing Scrum teams of 5-9 people work to complete the Sprint goals. Daily stand-up meetings provide status updates and help remove impediments.
- At the end of each Sprint, working software is demonstrated and the product owner evaluates progress before prioritizing tasks for the next Sprint.
- Scrum aims to improve productivity, adaptability and creativity compared to
Scrum process powerpoint ppt slides.
The scrum process document outlines the key aspects of running a scrum project. It includes preparation steps like establishing a business case and assembling a team. It then describes the sprint planning meeting where the product backlog is reviewed and the sprint backlog is created. Each sprint involves daily stand up meetings and culminates in a sprint review and retrospective. The goal is to deliver working software increments in short iterations through an adaptive, flexible process.
Scrum introduction
Scrum is an agile framework for managing software development projects that focuses on iterative delivery through short cycles called sprints. It utilizes roles like the product owner, development team, and scrum master. Key artifacts include the product backlog to track features and the sprint backlog to plan work for each iteration. Regular meetings like daily stand-ups, sprint reviews, and retrospectives promote transparency and process improvement. While long-term estimates are challenging, scrum values transparency and frequent delivery to build trust with stakeholders.
The Scrum Model
The document provides an overview of the Scrum model for agile software development. Scrum divides projects into short sprints of 2-4 weeks to focus development. It utilizes daily stand-up meetings, sprint planning and reviews, and retrospectives. Key roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the cross-functional development team. Scrum aims to provide structure while allowing for flexibility, feedback and adapting to changes.
Scrum 101
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Agile Methodology(SCRUM)
The document discusses the Agile Scrum methodology. It describes the key principles of Scrum which value individuals and interaction, working software, customer collaboration, and responding to change over processes, documentation, contracts, and plans. It then explains the main roles in Scrum including the Product Owner, Scrum Master, and self-organizing cross-functional Team. It outlines the core Scrum events like the Sprint, Daily Stand-up, Sprint Review, and Retrospective.
Agile Scrum software methodology
The document provides an overview of the Scrum agile framework for software development. It defines Scrum, outlines its history and components, and describes key aspects like roles, artifacts, and the sprint process. Scrum uses short development iterations called sprints to incrementally develop working software, with daily stand-ups and sprint planning and review meetings. Roles include the product owner, scrum master, and self-organizing cross-functional team. Artifacts include the product and sprint backlogs and burn down charts. The document also discusses scaling Scrum for large projects.
Get Up! Stand Up!
This document provides guidance on effective stand up meetings. It discusses that stand ups should be 15 minutes to synchronize activities and plan for the next day. However, some teams treat it as a status report to the leader, long problem solving meeting, or total chaos. The document recommends focusing on improvement, the team, and keeping status updates brief. It suggests practices like using visual boards, gathering issues to process after, and rotating the facilitator. Large teams may try options like scrum of scrums or fishbowl standups. The goal is sharing with each other, not just reporting, and keeping the energy level high.
What is scrum in Agile methodology?
Scrum is an agile framework that focuses on delivering working software in short iterations called sprints, typically 2-4 weeks. Self-organizing teams work to complete items from a prioritized backlog list. Daily stand-up meetings and sprint planning, review, and retrospective ceremonies provide transparency and opportunities to inspect and adapt the process as needed. The framework aims to rapidly deliver business value through flexible and collaborative teamwork.
Agile Software Development Overview
The document introduces agile software development methods. It discusses the goals of being able to speak confidently about agile and provide solutions to problems teams face. The agenda covers introductions to agile principles, roles, planning, reporting, retrospectives, and estimating. Popular agile methods like Scrum and XP are explained. The roles of product managers and product owners are compared.
Scrum ppt
This document provides an overview of Scrum, an agile software development process. It discusses the history and principles of Scrum, key roles like Product Owner and Scrum Master, artifacts like the Product and Sprint Backlogs, and the Scrum process which involves sprints, daily stand-ups, and sprint reviews. Advantages include delivering working software frequently in short iterations, while disadvantages include potential high implementation costs and training needs. In conclusion, Scrum offers flexibility and a high chance of project success when implemented properly.
Agile Scrum Methodology
The document discusses Agile SCRUM project development methodology. It provides an overview of SCRUM principles and processes including short iterative development cycles called sprints, daily stand-up meetings, sprint planning, tracking sprint backlogs and burn downs, sprint reviews and retrospectives. The roles of product owners, scrum masters and self-organizing cross-functional teams are also summarized.
Introduction to Scrum.ppt
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
Agile Is the New Waterfall
This is supposed to be an introductory presentation on Agile.
In this presentation I give some examples of heavy weight methods and their implications on your project. Then I give a quick overview of Agile methods, the rationale behind it, its origin, its values and principles. I move on to describe that what I see happening today in the industry is really waterfall in the name of Agile. I give some reasons why this is happening and then I give some pointers to move away from this flawed thinking.
Bottom line, Agile is not a Silver Bullet and don't fall pray to marketing gimmicks. Question dogmatic claims. Adapt Agile to your needs and take baby steps.
Scrum In 15 Minutes
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
Scrum 101: Introduction to Scrum
This document provides an introduction to Scrum, an agile framework for project management. It discusses the principles of agile development and Scrum, including self-organizing cross-functional teams, short sprint cycles, daily stand-ups, product backlogs and user stories, estimation techniques, and retrospectives for continuous improvement. The Scrum framework emphasizes empiricism, adaptation, transparency, inspection, and frequent delivery of working software.
Overview of Agile Methodology
This document provides an overview of agile methodology and compares it to traditional waterfall development. It describes waterfall development as a sequential process with distinct phases completed one after another. Agile approaches like Scrum and Kanban are presented as more iterative and adaptive alternatives that focus on delivering working software frequently in short cycles through self-organizing cross-functional teams. Key aspects of Scrum like sprints, daily stand-ups, and product backlogs are defined. Kanban emphasizes visualizing and limiting work in progress to optimize flow. Both aim to incorporate feedback and respond rapidly to changes over rigidly following pre-defined plans.
Viewers also liked (20)
Recently uploaded
"Choosing proper type of scaling", Olena Syrota
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.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.
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
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.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Dmitrii Kamaev, PhD
Senior Product Owner - QIAGEN
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
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.
Dandelion Hashtable: beyond billion requests per second on a commodity server
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Recently uploaded (20)
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
Scrum by picture
- 2. based on The Scrum GuideTM prepared by Paweł Lewiński
- 4. THEORY
- 8. VALUES
- 14. SCRUM TEAM
- 18. EVENTS
- 25. ARTIFACTS
- 29. Creative Commons License Attribution This is a derivative work by Paweł Lewiński based on the Scrum Guide ©2016 by Scrum.Org and ScrumInc, available at http://scrumguides.org. Offered for license under the Attribution Share-Alike license of Creative Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at http://creativecommons.org/licenses/by-sa/4.0/. By utilizing this Scrum Guide you acknowledge and agree that you have read and agree to be bound by the terms of the Attribution ShareAlike license of Creative Commons. This work is not associated with Scrum.org nor Scrum Inc in any way.