The document introduces Agile and Scrum concepts. It discusses Scrum roles like ScrumMaster and Product Owner and the team. The Agile manifesto values individuals and interactions over processes and tools. Sprints occur over 24 hours and 2 weeks where a backlog of user stories is implemented in tasks. User stories follow a format of "As a <role> I want <goal> so that <benefit>". Metrics show Agile can increase productivity, quality, satisfaction while decreasing costs. Resources provided for learning more.
What is Scrum? How to implement Scrum?
- This presentation describes the basic elements of the Scrum Framework.
- My goal is to provide an organized view that will help a novice understand and implement the Scrum foundation quickly.
What is Scrum? How to implement Scrum?
- This presentation describes the basic elements of the Scrum Framework.
- My goal is to provide an organized view that will help a novice understand and implement the Scrum foundation quickly.
Integrate Scrum and Kanban to maximize business value as early as possible by analyzing, developing, delivering, and maintaining complex products and IT services.
Open ScrumBan Manifesto
Delivering the finished product
Over reviewing the artifacts
On-demand release
Over scheduled release
Value flow
Over following dogmas
Progressive improvement
Over mutation driven by Model
Open ScrumBan Principles
Lean Agile
Implement lean thinking into agile practice, pursue value-added and eliminate waste, such as workflow, stable system, etc.
Pursue system thinking, identify various systems and systems of systems, and make decisions based on context
Iteration Rhythm
Pursue single-piece flow, single-piece can be entered into the plan, but single-piece release is not mandatory, and batch delivery is performed at fixed intervals by default
Focus on value delivery, each iteration must have an actual release increment, no longer requiring only potential release increments like Scrum
Respect present
Use Kanban to show the delivery value stream, and analyze improvement opportunities from the perspective of the value stream, such as lead time
When starting, it is not required to immediately change the team according to any team model, and choose the roles and practice according to the situation of the team
Evolutionary optimization
Use evolution instead of revolution to optimize and help teams develop various practices that are suitable for them
Not to tolerate the deficiencies and dysfunctions exposed by Scrum, but to combine the specific environment of different teams to find effective ways to solve them
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...Vidas Vasiliauskas
In this presentation I have talked about scrumban - a mix of routines and techniques for daily use in dynamic environment. Like in startups, product manufacture, support or similar cases.
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
Slide-2: World is VUCA. It was VUCA. It is VUCA and will be VUCA.
Slice-3: The change in VUCA is the speed of change. The rate of change is high due to technological advancements.
Slide-4: The much-hyped Paytm share tank on listing day by nearly 23%, though the predecessor listings (IPO) managed to list with a higher price sometimes double.
Slide-5: The PESTELE is an acronym for environmental factors that infuse change in the business and/or individuals.
Slide-6: The NFT are gaining popularity. Art, music, literature and movies can be secured. Notably, each NFT acts as a kind of certificate of authenticity, showing that a digital asset is unique and not interchangeable.
Slid-7: To gain competitive advantage, the businesses to be agile i.e faster, cheaper, better and less risky to embrace the change.
Slide-8: PDCA is an iterative design and management method used in business for the control and continuous improvement of processes and products. It is also known as the Deming circle/cycle/wheel.
Slide-9: Empiricism is a model to learn for experimentations. The best learning takes place through continuous experimentation. Learning from failure is the best.
Slide-10 to 16: The successful frameworks exist before the Agile Manifesto introduction.
Slide-17: The best practices from each successful framework are reviewed and created Agile manifesto having 4 values and 12 principles. Refer to https://agilemanifesto.org/ for further details.
Slide-18: Elon Musk is a physics guy and leverages first principle for tackling complex problems.
Slide-19: The Scrum framework.
Slide-20: Scrum roles
Slide-21: Story point estimation is for stories and ideal hours for tasks. Story points help the stakeholders to conclude on time it takes to complete backlog based on velocity
Slide-22 to 24: The humbleness of Mr Anand Mahindra after being conferred with the Padma Bhushan award.
Note: This is the slide used for educating on "the Need of being agile" as part of their "Finishing School" program.
This is a presentation I put together for a conference in 2011. It gives a fast, high level view of where Agile Software Development came from, its core values and principles, and its core practices. It is structured as 7 PechaKucha decks in a row, with short breaks in between, which requires high energy, intensity, and a sense of humor. :)
Integrate Scrum and Kanban to maximize business value as early as possible by analyzing, developing, delivering, and maintaining complex products and IT services.
Open ScrumBan Manifesto
Delivering the finished product
Over reviewing the artifacts
On-demand release
Over scheduled release
Value flow
Over following dogmas
Progressive improvement
Over mutation driven by Model
Open ScrumBan Principles
Lean Agile
Implement lean thinking into agile practice, pursue value-added and eliminate waste, such as workflow, stable system, etc.
Pursue system thinking, identify various systems and systems of systems, and make decisions based on context
Iteration Rhythm
Pursue single-piece flow, single-piece can be entered into the plan, but single-piece release is not mandatory, and batch delivery is performed at fixed intervals by default
Focus on value delivery, each iteration must have an actual release increment, no longer requiring only potential release increments like Scrum
Respect present
Use Kanban to show the delivery value stream, and analyze improvement opportunities from the perspective of the value stream, such as lead time
When starting, it is not required to immediately change the team according to any team model, and choose the roles and practice according to the situation of the team
Evolutionary optimization
Use evolution instead of revolution to optimize and help teams develop various practices that are suitable for them
Not to tolerate the deficiencies and dysfunctions exposed by Scrum, but to combine the specific environment of different teams to find effective ways to solve them
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...Vidas Vasiliauskas
In this presentation I have talked about scrumban - a mix of routines and techniques for daily use in dynamic environment. Like in startups, product manufacture, support or similar cases.
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
Slide-2: World is VUCA. It was VUCA. It is VUCA and will be VUCA.
Slice-3: The change in VUCA is the speed of change. The rate of change is high due to technological advancements.
Slide-4: The much-hyped Paytm share tank on listing day by nearly 23%, though the predecessor listings (IPO) managed to list with a higher price sometimes double.
Slide-5: The PESTELE is an acronym for environmental factors that infuse change in the business and/or individuals.
Slide-6: The NFT are gaining popularity. Art, music, literature and movies can be secured. Notably, each NFT acts as a kind of certificate of authenticity, showing that a digital asset is unique and not interchangeable.
Slid-7: To gain competitive advantage, the businesses to be agile i.e faster, cheaper, better and less risky to embrace the change.
Slide-8: PDCA is an iterative design and management method used in business for the control and continuous improvement of processes and products. It is also known as the Deming circle/cycle/wheel.
Slide-9: Empiricism is a model to learn for experimentations. The best learning takes place through continuous experimentation. Learning from failure is the best.
Slide-10 to 16: The successful frameworks exist before the Agile Manifesto introduction.
Slide-17: The best practices from each successful framework are reviewed and created Agile manifesto having 4 values and 12 principles. Refer to https://agilemanifesto.org/ for further details.
Slide-18: Elon Musk is a physics guy and leverages first principle for tackling complex problems.
Slide-19: The Scrum framework.
Slide-20: Scrum roles
Slide-21: Story point estimation is for stories and ideal hours for tasks. Story points help the stakeholders to conclude on time it takes to complete backlog based on velocity
Slide-22 to 24: The humbleness of Mr Anand Mahindra after being conferred with the Padma Bhushan award.
Note: This is the slide used for educating on "the Need of being agile" as part of their "Finishing School" program.
This is a presentation I put together for a conference in 2011. It gives a fast, high level view of where Agile Software Development came from, its core values and principles, and its core practices. It is structured as 7 PechaKucha decks in a row, with short breaks in between, which requires high energy, intensity, and a sense of humor. :)
There are a lot of choices and alternatives for getting started with Agile. It can be confusing. This talk will give you a brief guided tour of Agile methodologies so that you have some understanding of how they are similar and how they differ. We'll cover some of the history of iterative development and waterfall as well as the Agile Manifesto to provide context. At the end of this, you will have an understanding of key principles and the Agile landscape.
Please email me if you would like a download.
Webinar "Differences between Testing in Waterfall and Agile"
presentation by Maria Teryokhina
http://www.exigenservices.ru/webinars/testing-in-waterfall-and-agile
The basics of Agile and Waterfall Project management methodologies. Description when each approach can be applied.
Advices How to create a Product backlog and how to colect requirements. Sprint planning, Burndown chart, Demonstration, Retrospective, Tasks board examples.
Agile and Waterfall are two distinct methods of project management.
The Waterfall model can essentially be described as a linear model of project development. Like its name suggests, waterfall employs a sequential process. Development flows sequentially from start point to end point, with several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.
In contrast, the Agile method proposes an incremental and iterative approach to project development. It was essentially developed in response to the limitations of Waterfall, as a way to give more freedom. The process is broken into individual models that team work on. There is no pre-determined course of action or plan with the Agile method. Rather, team-mates are free to respond to changes in requirements as they arise and make changes as the project progresses. Agile is a pretty new player to the development management. However, it has made substantial gains in use and popularity in the last couple of years.
Presentation (animated) on Agilve vs Iterative vs Waterfall models in SDLC.
Detailed comparison across Process, Planning, Execution and Completion.
#Cricket Analogy#
Waterfall (Test Match) vs Iterative (ODI) Format vs Agile (T20)
#Waterfall: Test Match Format - Strategic-Phase by Phase like Innings by Innings.
Game for Specialists, Slow and Steady.
#One Day (ODI) Format : Strategic approach – First10/Middle/Slog overs.
Mix of Specialists and
All-Rounders, Result oriented.
#T20 Format: Lively,Dynamic, Full of Action. Game for All-Rounders. Changes with every over.
Highly Result oriented
Introduction To Business Architecture – Part 1Alan McSweeney
This is the first of a proposed four part introduction to Business Architecture. It is intended to focus on activities associated with Business Architecture work and engagements.
Business change without a target business architecture and a plan is likely to result in a lack of success and even failure. An effective approach to business architecture and business architecture competency is required to address effectively the pressures on businesses to change. Business architecture connects business strategy to effective implementation and operation:
• Translates business strategic aims to implementations
• Defines the consequences and impacts of strategy
• Isolates focussed business outcomes
• Identifies the changes and deliverables that achieve business success
Enterprise Architecture without Solution Architecture and Business Architecture will not deliver on its potential. Business Architecture is an essential part of the continuum from theory to practice.
Business requirements gathering and analysisMena M. Eissa
Business analysis and requirements management are a key to project success.
This workshop helps candidates perform better based on sharing real life experience with them.
Genuine agility at scale through LeSS Product Ownership - April 2018Rowan Bunning
Scrum is too often seen as a way for development to deliver faster without concern for agility, customer value optimisation or learning. Whilst there may be a role called “Product Owner”, it may be subordinated to little more than a team-centric SME taking orders from stakeholders and feeding “stories” to a team. In this session, we explore how the LeSS (Large-Scale Scrum) guidance on the Product Owner role can be used to address these problems and achieve scalable agility at a whole of customer-centric product level, no matter how many teams contribute.
Learning objectives:
- Recognise the limitations that you may be experiencing with the Product Owner implementation at your organisation
- Be aware of well proven patterns for scaling the Product Owner role to endeavours involving dozens or hundreds of people
- Be equipped to have an informed conversation about how your organisation can increase agility at scale.
As presented at the Global Scrum Gathering Minneapolis 2018.
Learn and Grow:
We give trainings for following courses:
Selenium with Java Online Training
Selenium with C# Online Training
JMeter Online Training
CodedUI Online Training
QTP Online Training
Manual Testing Online Training
ISTQB Certification Training
Scrum Master Training
Website : http://globalsqa.com/onlineTrainings.html
Email : contact@globalsqa.com
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
The Scrum Master and the Product Owner are critical to success of agile development teams using Scrum with the authority to make changes to the process, suggest team members take action, and empower members to do tasks correctly, in support of increasing the probability of project success.
Building A Production-Level Machine Learning PipelineRobert Dempsey
With so many options to choose from how do you select the right technologies to use for your machine learning pipeline? Do you purchase bare metal and hire a devops team, install Spark on EC2 instances, use EMR and other AWS services, combine Spark and Elasticsearch?! View this talk to get a first-hand experience of building ML pipelines: what options were looked at, how the final solution was selected, the tradeoffs made and the final results.
Using PySpark to Process Boat Loads of DataRobert Dempsey
Learn how to use PySpark for processing massive amounts of data. Combined with the GitHub repo - https://github.com/rdempsey/pyspark-for-data-processing - this presentation will help you gain familiarity with processing data using Python and Spark.
If you're thinking about machine learning and not sure if it can help improve your business, but want to find out, set up a free 20-minute consultation with us: https://calendly.com/robertwdempsey/free-consultation
Analyzing Semi-Structured Data At Volume In The CloudRobert Dempsey
Presentation from Snowflake Computing at the November 2015 Data Wranglers DC meetup.
The Cloud, Mobile and Web Applications are producing semi-structured data at an unprecedented rate. IT professionals continue to struggle capturing, transforming, and analyzing these complex data structures mixed with traditional relational style datasets using conventional MPP and/or Hadoop infrastructures. Public cloud infrastructures such as Amazon and Azure provide almost unlimited resources and scalability to handle both structured and semi-structured data (XML, JSON, AVRO) at Petabyte scale. These new capabilities coupled with traditional data management access methods such as SQL allow organizations and businesses new opportunities to leverage analytics at an unprecedented scale while greatly simplifying data pipeline architectures and providing an alternative to the "data lake".
http://robertwdempsey.com
If you’ve been reading books and blog posts on machine learning and predictive analytics and are still left wondering how to create a predictive model in Python and apply it to your own data, this presentation will give you the steps and code you need to do just that.
You'll learn how to go from raw data to a trained predictive model you can implement in a production system, and then how to implement it in production.
Creating Your First Predictive Model In PythonRobert Dempsey
If you’ve been reading books and blog posts on machine learning and predictive analytics and are still left wondering how to create a predictive model and apply it to your own data, this presentation will give you the steps you need to take to do just that.
How is growth hacking different from marketing? Is it just a buzzword or is it the way all business must market in a world where the lines between digital and real life are blurred.
In this presentation I discuss what growth hacking is, some techniques and tools you can put into practice today, and what kind of results you can expect.
Data Wranglers DC December meetup: http://www.meetup.com/Data-Wranglers-DC/events/151563622/
There's a lot of data sitting on websites just waiting to be combined with data you have sitting on your servers. During this talk, Robert Dempsey will show you how to create a dataset using Python by scraping websites for the data you want.
http://dempseymarketing.com/events/content-marketing-strategy-2013-webinar/ - According to the "Quarterly Intelligence Briefing: Digital Trends for 2013," report from Econsultancy and Adobe, content marketing is the most important emerging digital trend facing marketers today, followed closely by conversion rate optimization. However, the challenge remains - how can you use content to increase leads and sales?
On this webinar, we'll show you real-life examples of content marketing strategies we've used for our clients.
Creating Lead-Generating Social Media CampaignsRobert Dempsey
Creating Lead-Generating Social Media Campaigns - How to create measurable social media campaigns that generate leads for your business. http://dempseymarketing.com
During this 1-hour goal writing workshop held for Dempsey Marketing Tribe members, we discussed:
- Common reasons people don't achieve their goals
- The two ingredients that create success
- How to achieve a success mindset
- How to determine your life's purpose
- A way to write goals that works for everyone
- Resources to help you achieve your goals
Join the Dempsey Marketing Tribe to get access to this webinar and many more: http://JoinTri.be/31320
During this 1-hour introduction to Google AdWords webinar held for Dempsey Marketing Tribe members, we discussed:
- The lies Google will tell you
- A (bit more than a) few words on keyword research
- From keywords to ad groups
- Split testing your ads
- Make your website fulfill your promise
- Landing pages and A/B testing
- Tracking everything
- Tips from the trenches
Join the Dempsey Marketing Tribe to get access to this webinar and many more: http://JoinTri.be/31320
20 tips I wish I had when I quit my job many years ago. This is a guide I wrote for my Life Of The Freelancer site, which is now offline. I hope it helps many more peeps.
How To Turn Your Business Into A Media PowerhouseRobert Dempsey
http://lifeofthefreelancer.com
In this presentation that I did at WordCamp MSP, I show you how to dominate over your competition with an all out massive action strategy that turns your company into a media powerhouse.
This presentation introduces inbound marketing - what it is, what it isn't, why you want to use it, and how you do it. It also shows a solid example that I currently use to get business.
Watch the webinar recording: http://thenonmarketer.com/introduction-to-inbound-marketing-video-and-slides/
This presentation covers the why, who, what and when of writing requirements for Agile projects. Then we look at an example and how we can use mindmapping to brainstorm
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.
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.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
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.
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
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.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
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
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
I&#x2019;m the CEO of ADS, a web development shop in Orlando
Simple project management for agile teams
Find me on Twitter
The Old Way
Requirements -> Design -> Implement -> Verify -> Maintain
Waterfall
The Old Way
Requirements -> Design -> Implement -> Verify -> Maintain
Waterfall
The Old Way
Requirements -> Design -> Implement -> Verify -> Maintain
Waterfall
The Old Way
Requirements -> Design -> Implement -> Verify -> Maintain
Waterfall
The Old Way
Requirements -> Design -> Implement -> Verify -> Maintain
Waterfall
The Old Way
Requirements -> Design -> Implement -> Verify -> Maintain
Waterfall
Pros
Find bugs early in the process
Correct requirements now, less problems later (in theory)
Emphasis on documentation - developers hate doing this
Simple and disciplined
Good for stable projects
Cons
Each step is not mutually exclusive
Developers are usually (not) clairvoyant
Documentation overhead
Rigid and inflexible
Stable project?!
Reality
Development phases overlap
Software is emergent - the farther along we go the more we know
&#x201C;Done&#x201D; is a moving target
Flexibility is required - business requirements and the environment changes
Collaboration is essential
Lays out the philosophy for agile development
Individuals and interactions over process and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Agile Myths
Lack of discipline - &#x201C;self-managing&#x201D; = do whatever you want, when you want
Lack of visibility
&#x201C;That won&#x2019;t work here&#x201D;
What is Agile?
Group of philosophies and practices that provides the ablility to handle changing requirements
Iterative development
A lot of collaboration between business and developer
Have self-organizing and self-managing teams
Stressing leadership over management
Utilizing these and a set of practices, a team gains the ability to continuously adapt.
Agile Methods
Extreme Programming (XP)
Test Driven Development (TDD)
Feature Driven Development (FDD)
Behavior Driven Development (BDD)
Scrum
Scrum!
A framework for developing complex products and systems
Grounded in empirical process control theory
Transparency
Inspection
Adaptation
Three inspect and adapt points
Sprint Review and Planning meetings
Daily Scrum
The Retrospective
The Scrum Team
Product Owner
ScrumMaster
The Team
Called pigs: they have their bacon on the line
Involved, but aren&#x2019;t committed
Users, stakeholders (customers, vendors), managers, and business units
The driving force behind the process
Helps the team and organization adopt and use Scrum
A leader, not a manager
Roles they play: coach, teacher, and supporter
Manages and controls the product backlog
Responsible for the value of the work done
Keeps the product backlog in priority order, visible to everyone
A single person, not a committee
Must have authority, and the respect of others to succeed
Single point of contact for the team
The ones turning product backlog items into increments of potentially shippable functionality
Cross-functional: everyone that needs to be on the team to make the stories happen
Self-organized: everyone contributes
No job descriptions, no titles, no exceptions
Sink or swim as a team
Optimal team size: 7, +- 2
Team composition may change at the end of a sprint; be careful in doing so
Product Backlog
Managed by the Product Owner
Evolves along with the product and the environment
Master list of all functionality desired in the product
Includes all features, functions, technologies, enhancements, and bug fixes
Requirements are typically written in user story format
User Stories
How we write our requirements
From the user perspective
User Stories
Product Backlog
Sorted in order of priority
Requirements never stop changing
Minimize work: add fine-grained detail to the highest priority items (for the next few sprints)
Release Planning
Purpose: establish a plan and goals that everyone can understand and communicate
Establishes
The goals of the release
The highest priority Product Backlog items
The major risks
Overall features and functionality that the release will contain
Probable delivery date and cost if nothing changes
Composed of Sprints that deliver increments of the product, starting with the most valuable and most risky
Once enough increments are completed, release!
Most planning is done at the beginning of a release
Sprint
Sprint: 1-4 week block of time; all sprints are the same length
Protected by the ScrumMaster - no changing once it's started
Sprint Planning Meeting
When the iteration is planned
Max 8 hours for a one-month sprint, or 5% of the total Sprint length
Two parts
Sprint Planning Meeting: Part 1 - What
4 hours
The Product Owner and Team mutually determine what functionality will go into the Sprint
Considers the Product Backlog, the latest increment, team capacity, and past performance of the team
Only the team can say what they can accomplish in the upcoming Sprint
Sprint Goal: the purpose statement of the Sprint, the "why"
Sprint Planning Meeting: Part 2 - How
4 hours
Team determines how it will deliver a "done" increment
Identification of tasks - where the details are
A single task should take no more than one day
Sprint backlog - the list of tasks
Team self-organizes to assign and do the work
Negotiation between the Team and the Product Owner happens here
Sprint Backlog
All of the tasks required to turn Product Backlog items into "done" increments
Break each user story down so that changes in progress can be understood in the Daily Scrum
Modified during the Sprint as-needed
Tasks are added and removed if unnecessary
Tasks are estimated in hours, by the Team
Only the Team can change the Sprint Backlog during a Sprint
Highly-visible and real-time
Sprint Backlog
All of the tasks required to turn Product Backlog items into "done" increments
Break each user story down so that changes in progress can be understood in the Daily Scrum
Modified during the Sprint as-needed
Tasks are added and removed if unnecessary
Tasks are estimated in hours, by the Team
Only the Team can change the Sprint Backlog during a Sprint
Highly-visible and real-time
Sprint Backlog
All of the tasks required to turn Product Backlog items into "done" increments
Break each user story down so that changes in progress can be understood in the Daily Scrum
Modified during the Sprint as-needed
Tasks are added and removed if unnecessary
Tasks are estimated in hours, by the Team
Only the Team can change the Sprint Backlog during a Sprint
Highly-visible and real-time
Sprint Backlog
All of the tasks required to turn Product Backlog items into "done" increments
Break each user story down so that changes in progress can be understood in the Daily Scrum
Modified during the Sprint as-needed
Tasks are added and removed if unnecessary
Tasks are estimated in hours, by the Team
Only the Team can change the Sprint Backlog during a Sprint
Highly-visible and real-time
Sprint Backlog
All of the tasks required to turn Product Backlog items into "done" increments
Break each user story down so that changes in progress can be understood in the Daily Scrum
Modified during the Sprint as-needed
Tasks are added and removed if unnecessary
Tasks are estimated in hours, by the Team
Only the Team can change the Sprint Backlog during a Sprint
Highly-visible and real-time
Sprint Backlog
All of the tasks required to turn Product Backlog items into "done" increments
Break each user story down so that changes in progress can be understood in the Daily Scrum
Modified during the Sprint as-needed
Tasks are added and removed if unnecessary
Tasks are estimated in hours, by the Team
Only the Team can change the Sprint Backlog during a Sprint
Highly-visible and real-time
Sprint Burndown
Graph showing the amount of Sprint Backlog work remaining
Variable of interest: work remaining and date
Daily Scrum
15-minute standup
The Team is responsible for having the meeting
The ScrumMaster ensures it happens, and that it stays short
3 questions
Goals
Improve communication
Eliminate other meetings
Identify and remove impediments
Highlight and promote quick decision making
Improve everyone's knowledge
Daily Scrum
15-minute standup
The Team is responsible for having the meeting
The ScrumMaster ensures it happens, and that it stays short
3 questions
Goals
Improve communication
Eliminate other meetings
Identify and remove impediments
Highlight and promote quick decision making
Improve everyone's knowledge
Increment
Potentially shippable software: the Product Owner may decide to put it into production
Bug free, tested, clean code
Must work with everything already in place
This is where regression testing and continuous integration servers come in
Sprint Review
4-hour meeting for a one-month Sprint, or 5% of the total length of the sprint
The Scrum Team and stakeholders collaborate on what was done
Based on the feedback and changes to the Product Backlog during the Sprint, they collaborate about what to do next
Informal meeting intended to foster collaboration
Product Owner - tells what has/hasn't been done
Team - discusses what went well, what problems they ran into, and what they did to resolve them
Team - demos what's been done, and answers questions
Product Owner - discusses the Product Backlog as it stands
Group - collaborates on what to do next
Release Burndown
Graph showing the Product Backlog estimated effort remaining across time
Product Backlog estimates are reviewed and revised
Keep in mind: the Team is responsible for all estimates
Sprint Retrospective
Held between the Sprint Review and the next Sprint Planning meeting
3 hours max
ScrumMaster encourages the Team to revise their development process to become more effective
Purpose: inspect how the last Sprint went in regards to people, relationships, processes and tools
Identify and prioritize the major items that went well, and those that didn't - discuss how they can be done better
Discuss: team composition, meeting arrangements, tools, definition of "done"
Result: actionable improvement measures