The document provides an introduction to Agile development using Scrum. It discusses traditional software project failures and limitations of the Waterfall model. Scrum is then introduced as a framework that uses short Sprints, daily stand-up meetings, sprint reviews and retrospectives. Key Scrum roles include the Product Owner, Scrum Master and self-organizing cross-functional Team.
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 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 presentation gives brief description about a methodology of software engineering which is most using software engineering process in today's IT world and helps student to know how a software company runs and build software product using various software engineering methodologies.
Choosing right agile methodology for your projectPrabhat Sinha
I presented this talk at Drupal Con Dublin. It is very useful for executives and managers who are still figuring out right agile methodologies. Good comparison between - Scrum, Kanban, Scrumban, Extreme Programming (XP), Feature Driven Development (FDD), and Lean development .
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 presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Introduction to Scrum development process. Main concepts. The process. Examples. Issues
Slides for course Software engineering seminar @ Afeka College Of Engineering
this is my experience in Agile Scrum and materials collected over a period of time from various experts, credits goes to all who has directly and indirectly contributed
RIPPLE 2014: "Be Agile in a CMMI level 5 World"Délio Almeida
CRITICAL Software presentation on RIPPLE conference, hosted and sponsored by BLIP in Oporto back in March 2014. The topic is focused on the alignment of Agile/Scrum within a CMMI Maturity Level 5 organization in Portugal.
the presentation gives brief description about a methodology of software engineering which is most using software engineering process in today's IT world and helps student to know how a software company runs and build software product using various software engineering methodologies.
Choosing right agile methodology for your projectPrabhat Sinha
I presented this talk at Drupal Con Dublin. It is very useful for executives and managers who are still figuring out right agile methodologies. Good comparison between - Scrum, Kanban, Scrumban, Extreme Programming (XP), Feature Driven Development (FDD), and Lean development .
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 presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Introduction to Scrum development process. Main concepts. The process. Examples. Issues
Slides for course Software engineering seminar @ Afeka College Of Engineering
this is my experience in Agile Scrum and materials collected over a period of time from various experts, credits goes to all who has directly and indirectly contributed
RIPPLE 2014: "Be Agile in a CMMI level 5 World"Délio Almeida
CRITICAL Software presentation on RIPPLE conference, hosted and sponsored by BLIP in Oporto back in March 2014. The topic is focused on the alignment of Agile/Scrum within a CMMI Maturity Level 5 organization in Portugal.
Agile Software Development Workshop at Sote HubSote ICT
Presentation on agile project management by Maros Korinek, developer at Funding Circle, from his 4-day training in December 2016 at Sote Hub in Voi, Kenya.
Detail Information about Agile Process Frameworks such as SCRUM and CMMI along with agile manifesto. Comparison between scrum and capability maturity model integration
2013 Enterprise Track, Getting GIS done using the Scrum Methodology Jonathan ...GIS in the Rockies
We live in a world where limited resources is a constant battle. One of the biggest struggles is how to get work done and make sure that it brings the most value possible to our customer. Managing GIS work through Scrum provides a way to do this. In this presentation, I will explain the concepts around the Agile methodology and how it could be applied not only in the IT world, but to any GIS work that needs to be done.
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.
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.
Scrum is a Agile framework which allows teams to work together in order to develop a product.
Building complex products for customers is an naturally difficult task.
In the Scrum methodology a sprint is the basic unit of development.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
2. Agenda
• Short
introduc,on
to
Agile
• Scrum
– Overview
– How
it
works
2
3. Tradi4onal
So7ware
Project
Failures
• Nearly
2
/
3
of
the
projects
are
significantly
over
budget
• 64%
of
the
features
in
a
product
are
rarely
used
• An
average
project
exceeds
its
schedule
by
100%
3
4. Main
Causes
• Planning
for
comple4on
of
ac4vi4es
rather
than
features.
• Progress
not
transparent
to
customers,
and
focus
on
ac4vi4es
leading
to
missing-‐forgoRen
features.
• Specializa4on
leading
to
island
culture
and
reduced
involvement.
• Do
not
work
on
the
basis
of
client
priority,
but
o7en
technical.
Team
starts
late
with
important
business
needs
• Ignore
uncertainty
(changing
insights
/
requests?)
5. Limita4ons
of
Waterfall
"Waterfall"
project
approach
is
only
possible
if
• Problem
is
clear;
• Solu4on
is
known;
• Technique
familiar;
• Problem
has
not
changed;
• A
sufficient
knowledge;
• Priori4es
constant.
7. Suppor4ng
Agile
“Sentences”
1. Our
highest
priority
is
to
sa4sfy
the
customer
through
early
and
frequent
delivery
of
valuable
so7ware.
2. Deliver
working
so7ware
frequently,
from
a
couple
of
weeks
to
a
couple
of
months,
with
a
preference
for
the
shorter
4me
scale.
3. Working
so7ware/product
is
the
primary
measure
of
progress.
4. Welcome
changing
requirements,
even
late
in
development
5. Business
people
and
developers
work
together
daily
throughout
the
project.
6. Build
projects
around
mo4vated
individuals.
Give
them
the
environment
and
support
they
need,
and
trust
them
to
get
the
job
done.
8. Agile
Methodologies
• Extreme
Programming
(XP)
• Scrum
• Feature-‐Driven
Development
(FDD)
• Adap4ve
So7ware
Process
• Crystal
Light
Methodologies
• Dynamic
Systems
Development
Method
(DSDM)
• Lean
Development
9. Scrum
A scrum is a term from rugby.
Scrum is a way of re-start
after minor violation, where a
group of players tries to push
the ball obtain control.
11. Sprints
• Scrum
projects
consist
of
a
series
of
"sprints"
• Typically
2-‐4
weeks
in
length.
• A
fixed
constant
length
gives
a
beRer
work
rate.
• Features
are
designed,
built
and
tested
during
a
sprint.
• Customer
can
not
change
job
during
a
sprint.
• Have
a
sprint
goal.
A
brief
statement
about
the
focus
of
the
work
of
the
upcoming
sprint.
13. Product
Owner
• Is
the
voice
of
the
customer.
• Defines
the
features
of
a
product.
• Determines
the
release
date.
• Responsible
for
the
profitability
of
a
product.
• Its
mandate
is
to
make
decisions.
• Priori4zes
the
product
features
based
on
market
value
• Change
features
and
priority
every
itera4on,
if
desired.
• Accepts
or
approves
work
results.
14. Team
• Complete
(all
skills)
• Self
and
self-‐learning
• No
permanent
jobs
• 5
to
9
people
• Work
together,
not
individually.
• Involved
• Produc4ve
and
fun
• Preferably,
cross-‐func4onal.
15. Scrum
Master
• Is
not
a
project
manager!
Facilitates
the
team.
• Responsible
for
the
importa4on
and
compliance
with
Scrum
values
and
prac4ces.
• Solves
problems
for
the
progress
of
projects
iden4fied
by
the
team,
so
that
the
goal
of
Sprint
and
the
deliverables
are
met.
• Ensures
that
the
team
is
fully
focused,
opera4onal
and
produc4ve.
• Ensures
that
all
roles
and
func4ons
work
together.
• Shields
the
team
from
external
disturbances
during
the
sprint.
19. Daily
Scrum
• Daily,
15
minutes,
standing.
• Not
meant
to
solve
problems.
• Anyone
outside
the
team
may
be
present,
only
team
members
are
ac4ve
part
(speaking).
• Helps
to
avoid
unnecessary
mee4ngs
(e
g
weekly
progress
mee4ng)
• Are
not
intended
to
state
the
progress
or
management.
– What
did
you
do
yesterday?
– What
you
are
going
do
today?
– Are
there
any
restric4ons
that
the
comple4on
of
the
sprint
at
risk?
21. Sprint
Review(Demo)
• The
team
presents
the
results
of
the
last
sprint
through
a
demonstra4on
of
the
func4onality
built.
• Informal,
no
slides,
max
2
hours.
• The
whole
team
takes
part
in
the
demonstra4on.
• Stakeholders
and
managers
are
welcome
to
aRend.
22. Sprint
Retrospec4ve
• Is
held
a7er
each
sprint
• Consider
what
works
and
what
does
not
work.
• Priori4za4on
of
the
improvement.
• Ac4on
items
are
defined
to
ensure
that
real
improvements
takes
place
in
the
next
sprint
(s).
• The
whole
team
takes
part
(Scrum
Master,
Product
Owner,
Team).
• Dura4on
vary
depending
on
the
retrospec4ve
approach,
team
size,
length
sprint.
• Usually
30-‐60
minutes
24. Product
Backlog
• The
requirements
• To
Do
list
of
all
the
work
required
in
the
project.
• Expressed
from
the
user
/
client.
• Not
how
but
why.
• By
priority
(by
product
owner.)
• Itera4ve
(changes
ok,
for
each
sprint).
• Visible.
• Items
es4mated
effort
required
(by
team).
• User story format: As <type of user> I want<some goal> so
that <some business reason>.
26. Sprint
Backlog
• List
of
work
done
in
the
next
sprint.
• Breakdown
of
features
into
tasks
(1-‐16
hours).
• Tasks
are
not
assigned
to
team
members.
(More
variety
and
crea4vity.
No
knowledge
islands)
• Tasks
are
es4mated
by
the
team
with
Planning
Poker.
• Tasks
are
picked
based
on
the
right
priori4es
and
the
skills
of
team
member.
• Is
usually
visualized
by
a
Scrum
board
32. Defini4on
of
Done
• Is
determined
by
the
team
• Completed
work
must
meet
this
defini4on
• Elements
to
consider
include:
– Coding style
– Code comment
– Peer review
– Units tests
– Document
– Manual
– ???
34. Summary
• Scrum
is
(almost)
'Magic':
– Timely
feedback.
– Focus
on
working
product.
– Priori4ze
on
added
value.
– Not
plan
ahead
in
detail.
– Self-‐management
and
responsibility.
– Clear
roles
and
responsibili4es.