This document provides an overview of agile principles and the Scrum framework. It discusses the history and development of agile methodologies from the 1970s to present day. Key topics covered include the Scrum roles of Product Owner, ScrumMaster, and Development Team, as well as Scrum events such as Sprint Planning, Daily Scrum, Sprint Review, and Retrospective. The document contrasts traditional plan-driven and agile approaches to software development.
Instructional designers are often called upon to act as project leads and project managers on e-learning projects, yet they rarely receive formal project management training. There are unique project management issues related to e-learning and unique ways of adapting project management techniques and tools to address those issues. In this 2012 webinar I delivered at an eLearning Guild Online Forum, I discuss a variety of best practices related to managing stakeholders; managing process dependencies, collaborations, and handoffs; and managing quality issues related to interactivity, media, and contextualization.
Instructional designers are often called upon to act as project leads and project managers on e-learning projects, yet they rarely receive formal project management training. There are unique project management issues related to e-learning and unique ways of adapting project management techniques and tools to address those issues. In this 2012 webinar I delivered at an eLearning Guild Online Forum, I discuss a variety of best practices related to managing stakeholders; managing process dependencies, collaborations, and handoffs; and managing quality issues related to interactivity, media, and contextualization.
Integrating SCRUM with classical Project ManagementJens Hoffmann
SCRUM and PRINCE2 integrated, is a powerfull solution to scale the agile method for large projects. The conventional and mature project management approaches like PRINCE2 or PMI PMBOK are gaining more resillience from this as the become more flexible and adabtible to changing demands and needs.
From Waterfall to Agile - from predictive to adaptive methodsBjörn Jónsson
In this introduction into Agile methods, the background and environment of Software Development is discussed. Results of the 1995 Chaos report are mentioned, as well as interests in adaptive "lightweight" methods. Agile methods are explained in general and Scrum method taken as a concrete sample.
Integrating SCRUM with classical Project ManagementJens Hoffmann
SCRUM and PRINCE2 integrated, is a powerfull solution to scale the agile method for large projects. The conventional and mature project management approaches like PRINCE2 or PMI PMBOK are gaining more resillience from this as the become more flexible and adabtible to changing demands and needs.
From Waterfall to Agile - from predictive to adaptive methodsBjörn Jónsson
In this introduction into Agile methods, the background and environment of Software Development is discussed. Results of the 1995 Chaos report are mentioned, as well as interests in adaptive "lightweight" methods. Agile methods are explained in general and Scrum method taken as a concrete sample.
Calen Legaspi, O&B CEO, discusses a quick overview of Agile Software Development for the absolute beginner.
About O&B:
Orange & Bronze is a proponent of Agile Software Development. We believe that software development requires a collaborative environment where the software can start and evolve into a useful and strategic system. A common vision between O&B and the client is essential to have an effective collaborative environment. This, along with constant communication and repeated testing, ensures that the project will be delivered on time, all the time.
Orange & Bronze is an offshore product and software development firm in the Philippines, is one of the first companies in Asia to use and advocate Agile Software Development, and has been using it since our inception in 2005, back when Agile was still an emerging movement. O&B offers training courses for Agile with Scrum and XP - these classes were developed and are taught by some of the Philippines' well-known and respected Agile / Scrum coaches and practitioners, and uses the format trusted by some of the best companies in the Philippines.
Ik gebruik deze checklist zelf als Scrum coach. De mindmap bevat een samenvatting van alle waarden rondom Scrum.
Door op deze waarden te letten, naast het eenvoudig kijken naar de "mechanica" van Scrum, ontstaat er een veel betere Scrum implementatie. Zo wordt Scrum "naar de geest" toegepast.
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.
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.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Unsubscribed: Combat Subscription Fatigue With a Membership Mentality by Head...
About scrum
1.
2. • Introduction to agile principles
• Scrum framework overview
• Further (and related) topics
3.
4. - Managing the - A Spiral Model of - Dynamic Systems - XP was gained
1990s
1970s
1980s
2000s
Development of Software Development “momentum”.
Large Software Development and Methodology - Adaptive Software
Systems by Dr. Enhancement by (DSDM). Development by Jim
Winston W. Royce. Barry Boehm. - Crystal Highsmith.
- Evolutionary - The Mythical Man Methodologies by - Agile Manifesto.
processes process Month by Fred Alistair Cockburn.
introduced by Tom Brooks. - Agile methodologies
- First toughts and and practicies
Gilb. - PeopleWare by testing on Scrum for growing significantly
DeMarco and Lister. SW projects by Jeff in the market.
- Scrum roots on the S. And Ken S.
NNPDG article by - Origins of Extreme
Takeuchi and Programming (XP)
Nonaka. from Kent Beck.
- RUP Objectory v1.0 - Feature Driven
- Capability Maturity Development by
Model (CMM) and Peter Coad and Jeff
Managing the De Luca.
Software Process
book by Watts
Humphrey's.
5. Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right,
we value the items on the left more.
reference: http://agilemanifesto.org
6. Welcome changing Deliver working
Our highest priority is to requirements, even late in software frequently, Business people and
satisfy the customer development. Agile from a developers must
through early and continuous processes harness change
delivery couple of weeks to a couple work
for of months, with a together daily throughout
of valuable software the customer's competitive preference to the shorter the project
advantage timescale
Build projects around The most efficient and Agile processes promote
motivated individuals. effective method of sustainable
Give them the environment conveying information to and Working software is development.
and support they need, within a development the primary measure The sponsors, developers,
and trust them to get the team is face-to-face of progress and users should be able
conversation to maintain a constant pace
job done indefinitely
Continuous attention to The best architectures,
technical Simplicity--the art of requirements, and
At regular intervals, the team
reflects on how
maximizing the amount designs
excellence of work not done--is
to become more effective,
and good design emerge from self- then tunes and adjusts
enhances agility
essential organizing teams its behavior accordingly
reference: http://agilemanifesto.org
7. Far from
agreement
Here’s where
Requirements
Scrum Excels
Close to
agreement
Close to Technology Far from
certainty certainty
reference: adapted from schwaber, 2003
8. I know all details about End with all
where I should go (start requirements Plan-Driven
with plan and all completed
requirements)
Inspect and adapt
I know what is the
End with Vision and $$
product/project vision Value-Driven
Goals met
(start with goals and
some priority
requirements)
reference: adapted from schwaber, 2003
11. “THE PERSON WHO KNEW THAT
HER SON/DAUGHTER COULD
HAVE MARRIED BETTER, AND
WHO INTENDS TO HELP YOU BE
GOOD ENOUGH. YOU HAVE
JUST INVITED HER TO COME
LIVE WITH YOU”
– KEN SCHWABER
12. • Co-created by Jeff Sutherland and
Ken Schwaber
• Inspirations comes from Japanese
manufacturing (and the HBR article
“The New New Product Development
Game“ from Hirotaka Takeuchi and
Ikujiro Nonaka, published in 1986) Ken Schwaber and Jeff Sutherland
- Scrum Fathers
13. • Grounded in empirical process control theory, employs
an iterative, incremental approach to optmize
predictability and control risk
• Is about
– Transparency
– Inspection
– Adaptation
14. • Scrum teams and associated roles
• Time-boxes
• Artifacts
• Rules
15. • Product Owner
• ScrumMaster
• Scrum Team Manager Stakeholders...
ScrumMaster
Product Owner
Scrum Team
User
Customer
16.
17. • Define the features of the product
• Decide on release dates and contents
• Responsible for the profitability (ROI)
• Prioritize features according to market value
• Adjust priorities at every Sprint, as needed
• Accept or reject work results
• Is one person, not a committee “ROI = $$ and I like that!
Nice to meet you, Im the PO”
18.
19. • Ensures that the team is fully functional and productive
• Enable close cooperation across all roles
and functions
• Remove barriers
• Shield the team from external interferences
• Ensure that the process is followed
• Review and Sprint Planning meetings “The sheepdog for the team”
20. • Cross functional. Organizes itself and its work
• Team members must have all necessary skills to
create an increment of work
• Everyone chips in, even if that requires learning
new skills or remembering old ones
• 5 - 9 team members
• Has the right to do everything within the
boundaries of the project guidelines to reach the
Sprint goal Multi-skill ninja team
• Demonstrates work results to the Product Owner
22. 1 Release Planning
Meeting
2 Sprint planning
meeting 1
3 Sprint planning
5 meeting 2
4 The Sprint
Selected 5 Daily Scrum
Product Backlog 6 Sprint Review
7 Sprint Retrospective
4
Vision
Anticipated ROI,
Releases, Milestones 1 New functionality
2 3 is demonstrated
at the enf of
Sprint
Functional and
nonfunctional emerging Requirements
and prioritized requirements brake down into activities/tasks
23. • Establish a plan and goals that the Scrum Teams and
the rest of the organizations can understand and
communicate
• Release planning requires estimating and
prioritizing the Product Backlog for the Release
• Release planning is not a commitment to precise
details
• Release planning is entirely optional. If Scrum Setting the vision and the strategic
teams start work without the meeting, the absence plan
of its artifacts will become apparent as an impediment
that needs to be resolved
24. • A Sprint is an iteration
• Time-boxed
• All work is done in Sprints
• Consisted by the Sprint Planning,
development work, Sprint Review and the
Sprint Retrospective
• Sprints can be cancelled before the Sprint
time box is over. Only the Product Owner has
the authority to cancel the Sprint
It’s time to run!
25. • Is where the Sprint is planned
• Splited in two moments:
– The PO with the ScrumTeam support selects
the Product Backlog items that will compose
the Sprint Backlog (needs to consider team
velocity, etc. during this selection)
– With the Sprint Backlog defined, the team
works together to came up with a plan to the Operational plan being defined
Sprint that is beginning
– Meeting output: Sprint Backlog
26. • The Scrum heartbeat
• 15 minutes
• 3 questions
– What did you do yesterday?
– What will you do today?
– Are there any impediments in your way?
• The Daily Scrum is not a status meeting
• The Daily Scrum is an inspection of the progress “Look, our burndown is about to screw up,
we need to attack more harder to change that”
toward the Sprint Goal that the team was committed for
27. • The team presents to the PO and stakeholders
functionality that is done and answer
questions.
• The Product Owner identifies what has
been done and what hasn’t been done
• The Team discusses what went well during
the Sprint and what problems it ran into, and
how it solved these problems
“Let me show you that story operating”
• The entire group then collaborates about what it
has seen and what this means regarding what to do next
28. • Time to review the good and the bads
• Inspect how the last Sprint went in regards to
people, relationships, process and tools
• The meeting is from the team to the team
• PO attendance is not obrigatory
• ScrumMaster hold this meeting
• Team identify the actions to adapt and improve
the ongoing process “Definetely we need more automation in our
tests, we are wasting a lot of time doing
manual qualification...”
30. • The PO “wish list”
• Items prioritized by the
business importance/value
• The PO is the owner
• As long as a product exists,
the Product Backlog also exists
img source: http://epf.eclipse.org/wikis/scrum/
31. user
stories
Sprint
themes
Release Priority
Next Release epics
32. • Details the work, or tasks, that
the team defines to turning the
Product Backlog it selected for
that Sprint into an increment of
potentially shippable product
functionality img source: http://epf.eclipse.org/wikis/scrum/
33. • Shows the Release progress
• How much selected Product
Backlog was “burned”
• Updated at the end of each Sprint
• Normally the unit measure is Story
Points (not a rule) against Sprints
img source: http://epf.eclipse.org/wikis/scrum/
34. • Shows the Sprint progress
• How much the team already
“burned” in that Sprint
• Primary tool for the Daily Scrum
meetings (with task boards or
Sprint activities list)
• Normally the unit measure is img source: http://epf.eclipse.org/wikis/scrum/
Hours against time (daily basis)
35.
36.
37. • Scrum requires teams to build an increment of
product functionality every Sprint
• This increment must be potentially shippable, for
Product Owner may choose to immediately
implement the functionality
• The detailed definition of Done should be agreed
between the ScrumTeam and the PO
38. • Plannig Poker
• User Stories and Story Points
• Technical Debt
• Team Velocity
• Complex Adaptive Systems
• Lean manufacturing
• Constraints Theory
• Kanban