This document provides an overview of the Scrum framework for agile software development. It defines Scrum and agile development, describes when Scrum is applicable, and outlines the core components of Scrum including values, roles, events, artifacts, and a Scrum board. It also discusses pros and cons of the Scrum framework.
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.
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.
This talk is a 101-level introduction to Scrum, the agile methodology, especially in terms of how it works for web development. We'll cover the scrum values, rituals, and team. We'll also discuss some common pitfalls and how to work around them.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
The aim of agile methods is to reduce overheads in the software process (e.g. by limiting documentation) and to be able to respond quickly to changing requirements without excessive rework.
This presentation is about Scrum methodology. First it reviewed traditional SDM and then talk about Agile and Scrum
The slide explains the basics of the Scrum Framework one of the most popular Agile implementations for beginners. You can learn fundamental knowledge about it.
This talk is a 101-level introduction to Scrum, the agile methodology, especially in terms of how it works for web development. We'll cover the scrum values, rituals, and team. We'll also discuss some common pitfalls and how to work around them.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
The aim of agile methods is to reduce overheads in the software process (e.g. by limiting documentation) and to be able to respond quickly to changing requirements without excessive rework.
This presentation is about Scrum methodology. First it reviewed traditional SDM and then talk about Agile and Scrum
The slide explains the basics of the Scrum Framework one of the most popular Agile implementations for beginners. You can learn fundamental knowledge about it.
explains basic scrum jargon and details regarding scrum like duties of product owner,duties of scrum master,duties of development team,sprint planning,daily scrum,sprint overview,sprint retrospective
Software Development Guide To Accelerate PerformanceZaid Shabbir
Scrum is the most widely used framework across all software and business industries. By following complete scrum framework you can improve the quality product deliver in more adaptive way.
Slides contents content guidelines related to scrum framework and how some one become a certified scrum master. Slides elaborate scrum framework by using user friendly diagrams and bulleted points. After grasping the slides any one can easily pass certified scrum examination.
I am sure you will enjoy the contents and its really helpful to become a certified scrum practitioner.
This simple and crisp quick reference card is for Agile and Scrum basics. It is a simple way to glance through all the concepts and use it as a tool for revision, even before an interview.
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
Strategies for Successful Data Migration Tools.pptxvarshanayak241
Data migration is a complex but essential task for organizations aiming to modernize their IT infrastructure and leverage new technologies. By understanding common challenges and implementing these strategies, businesses can achieve a successful migration with minimal disruption. Data Migration Tool like Ask On Data play a pivotal role in this journey, offering features that streamline the process, ensure data integrity, and maintain security. With the right approach and tools, organizations can turn the challenge of data migration into an opportunity for growth and innovation.
top nidhi software solution freedownloadvrstrong314
This presentation emphasizes the importance of data security and legal compliance for Nidhi companies in India. It highlights how online Nidhi software solutions, like Vector Nidhi Software, offer advanced features tailored to these needs. Key aspects include encryption, access controls, and audit trails to ensure data security. The software complies with regulatory guidelines from the MCA and RBI and adheres to Nidhi Rules, 2014. With customizable, user-friendly interfaces and real-time features, these Nidhi software solutions enhance efficiency, support growth, and provide exceptional member services. The presentation concludes with contact information for further inquiries.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Why React Native as a Strategic Advantage for Startup Innovation.pdfayushiqss
Do you know that React Native is being increasingly adopted by startups as well as big companies in the mobile app development industry? Big names like Facebook, Instagram, and Pinterest have already integrated this robust open-source framework.
In fact, according to a report by Statista, the number of React Native developers has been steadily increasing over the years, reaching an estimated 1.9 million by the end of 2024. This means that the demand for this framework in the job market has been growing making it a valuable skill.
But what makes React Native so popular for mobile application development? It offers excellent cross-platform capabilities among other benefits. This way, with React Native, developers can write code once and run it on both iOS and Android devices thus saving time and resources leading to shorter development cycles hence faster time-to-market for your app.
Let’s take the example of a startup, which wanted to release their app on both iOS and Android at once. Through the use of React Native they managed to create an app and bring it into the market within a very short period. This helped them gain an advantage over their competitors because they had access to a large user base who were able to generate revenue quickly for them.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
Advanced Flow Concepts Every Developer Should KnowPeter Caitens
Tim Combridge from Sensible Giraffe and Salesforce Ben presents some important tips that all developers should know when dealing with Flows in Salesforce.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Modern design is crucial in today's digital environment, and this is especially true for SharePoint intranets. The design of these digital hubs is critical to user engagement and productivity enhancement. They are the cornerstone of internal collaboration and interaction within enterprises.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...
professional scrum master
1. CONTENTS
What is scrum?
What is agile?
When to use scrum
Scrum values
Scrum theory
Scrum roles
Scrum events
Scrum artifacts
Scrum board
2. What is Scrum?
• The Professional Scrum Master (PSM) is a course
that covers the principles and (empirical) process theory
underpinning the mechanics, rules and roles of
the Scrum framework.
• Scrum is a subset of Agile. It is a lightweight process
framework for agile development, and the most widely-
used one.
• A “process framework” is a particular set of practices
that must be followed in order for a process to be
consistent with the framework
• “Lightweight” means that the overhead of the process is
kept as small as possible, to maximize the amount of
productive time available for getting useful work done.
3. What is Agile?
• Agile software development refers to a group of
software development methodologies based on
iterative development
• Agile development refers to any development process
that is aligned with the concepts of the Agile
Manifesto.
AGILE MANIFESTO
4. When to use Scrum
1.Scope is not clearly defined.
2.The product will gradually appear during the project.
5.Activities cannot be well defined upfront
6.Estimating (planning) is difficult
3.Requirements change frequently
4.Customer learns more about what they want as the project goes on
7.Process is iterative (numerous cycles)
8.Each cycle heavily depends on the previous one
9.Success is mostly measured by customer satisfaction
10.Incremental results have value and can be used by users (put into production)
5. SCRUM VALUES
• Developers are free to do what they want.
• Scrum gets rid of all paper work and allows the team to start
developing right away.
• All requirements (in the form of stories) must be agreed
before the Development Team is allowed to start working on
the product
• The Scrum Master is like a project manager
• Scrum does not require you to have a Business Case.
• Scrum is just a set of simple rules.
• Scrum allows the Development Team to decide what will be
delivered
• The Product Owner is the project manager
• Scrum tells us everything about managing projects.
• The Product Owner is a representative from the customer.
• Scrum is very easy to implement, even without training
6. SCRUM THEORY
• A basic idea of how a Scrum project works.
• A Vision Statement and Product Map will be provided to define and describe
the vision and the goal of the project.
Vision Statement :
The Vision Statement provides a concise description of the goals
of the project which help the team stay focused on what is
important from the organization point of view.
Product Roadmap:
The Product Roadmap is an initial visual timeline of major
product features to be delivered and is normally created by the
Product Owner; one of the Scrum role.
9. Role 1: The Product
Owner
The Product Owner is
responsible for the Product
Backlog.
The Product Backlog is a
prioritized list of items (aka
stories or user stories) that the
client expects from the project.
It is also the responsibility of
the Product Owner to make
sure that each item (user story)
is easy to understand for the
Scrum Team, and other
stakeholders.
Product Owners should
communicate effectively with
the customer (the inevitable
success.
10. Role 2: Scrum Master
• Scrum Masters are those who fully
understand Scrum, and help the
Scrum Team by coaching them, and
ensuring that all Scrum processes
are implemented correctly.
• The Scrum Master is a management
position, which manages the Scrum
process, rather than the Scrum
Team.
• He/she is a servant-leader for the
Scrum Team.
• The Scrum Master also tries to
remove impediments to the
Development Team, facilitates their
events, and trains and coaches them.
• It is possible for a single person to
be both Scrum Master, and a
member of the Development Team,
although this is not recommended.
11. Role 3: The Development
Team
Members of the Development Team are
application area experts that are responsible
for delivering backlog items, and managing
their own efforts.
They should be capable of doing the A to Z
of the creation of each Product Backlog item.
The Development Team delivers the final
product of the project in step by step
Increments, as defined in the Product
Backlog. They always work in a product-
based way.
It is highly recommended for members of the
Development Team to work full-time in a
single project, to stay focused.
Scrum is mostly effective when there are 3 to
9 Development Team members.
12. SCRUM EVENTS
All the Scrum events must be time-boxed this is an essential concept in
Agile methods, called time-box which is a predefined fixed maximum
duration of time , in order to maximize productivity.
There are just five events in a Scrum Project ,they are
A . Sprint
B . Sprint Planning
C . Daily Scrum
D . Sprint Review
E . Sprint Retrospective
Nature Of Scrum
13. A. SPRINT
Sprint is a time-boxed event, which means we should fix its
duration at the beginning of the project and do not change it
frequently or occasionally. Sprints are usually fixed for one
month or less.
14. Each Scrum project delivers the final product after a number
of cycles, which are called Sprints. An Increment is developed
in each Sprint. An Increment is a potentially releasable part of
the final product .
15. B .Sprint Planning
The first thing to do in each Sprint is Sprint Planning. Sprint Planning is a
time-boxed meeting, usually fixed to 8 hours for a one month Sprint, or shorter
for Sprints of less than a month. All three roles should attend this meeting.
The Sprint Backlog will be ready at the end of this meeting and
the Development Team should be able to describe what items they will
deliver through the Sprint, and how they will do it.
The Sprint Backlog consists of the following:
1. The Sprint Goal
2. Selected items from the Product Backlog, to be delivered
through the sprint
3. A detailed plan for turning the selected items into “Done”
16. This sample Scrum board has also extra features for tracking the
tasks and items in “To Do”, “Doing”, and “Done” columns. The
next figure shows the same Sprint after the first item is complete
and items #2 and #3 are in progress.
17. C . Daily Scrum
• The Daily Scrum is normally a 15 minute meeting for
the Development Team to inspect the work since the
last meeting, and synchronize their work and plan for
the next 24 hours. It must be held on a daily basis.
• During the Daily Scrum, each member of the
Development Team should answer these three
questions:
• 1. What has been accomplished since the last meeting?
• 2. What will be done before the next meeting?
• 3. What obstacles are in the way?
18. The above figure contains the Sprint Burn-Down Chart (the
tracking information) and this can be updated after each Daily
Scrum meeting.
19. D . Sprint Review
At the end of the Sprint, the Scrum Team and
other stakeholders gather and hold a four hour
meeting to present and inspect the “Done” items
(the Increment) from the current Sprint and adapt
the Product Backlog by marking off “Done” items
as complete and add new items or change the
existing ones if necessary. The presentation of the
Increment in this meeting is intended to collect
feedback and raise change requests at the earliest
time possible.
20. Finally, the whole Scrum Team collaborates on revising
the Product Backlog based on the output of the Sprint and
the feedback received from the customer.
21. E .Sprint Retrospective
• This meeting is normally three hours for a one month
Sprint .
• After the Sprint Review and just before the end of the
Sprint, another meeting will be held, aimed at process
improvement (learning lessons), which is called Sprint
Retrospective .
• There is a rule: we should always look for ways to
improve. It does not matter how little the improvement is,
there should be an improvement. This meeting is a formal
opportunity for improvement, even though we do not
limit our improvement to the results of this meeting.
22. 5. Scrum Artifacts
• There are a number of artifacts designed to increase transparency and
provide an opportunity for inspection and adaptation. The Scrum artifacts
are as follows:
1. Product Backlog: an ordered list of everything that might be needed in
the product
2.Sprint Backlog: the plan for a certain Sprint, containing .
3.Increment: the sum of all the Product Backlog items completed (so far in
the project) at the end of a Sprint
4.Definition of “Done”: the shared understanding of what it means for a
piece of work to be considered complete
5.Monitoring Progress toward a Goal: the performance measurement and
forecast for the whole project, which is done by the Product Owner.
6.Monitoring Sprint Progress: the performance measurement and
forecasts for a single Sprint, which is done by the Development Team.
25. Scrum Pros
•Scrum can help teams complete project deliverables quickly
and efficiently
•Scrum ensures effective use of time and money
•Large projects are divided into easily manageable sprints
•Developments are coded and tested during the sprint review
•Works well for fast-moving development projects
•Scrum, being agile, adopts feedback from customers and
stakeholders
•Short sprints enable changes based on feedback a lot more
easily
•The individual effort of each team member is visible during
daily scrum meetings
26. Scrum Cons
•Scrum often leads to scope creep, due to the lack of a definite
end-date
•The chances of project failure are high if individuals aren't very
committed or cooperative
•Adopting the Scrum framework in large teams is challenging
•The framework can be successful only with experienced team
members
•Daily meetings sometimes frustrate team members
•If any team member leaves in the middle of a project, it can have a
huge negative impact on the project
•Quality is hard to implement, until the team goes through
aggressive testing process