This document discusses the transition from a traditional waterfall process to Scrum in an IT team. It describes the key aspects of Scrum including sprint planning, daily stand-ups, product increments and sprint reviews. It outlines challenges faced during implementation, such as getting stakeholders involved and changing team dynamics. The presentation aims to show how Scrum improved processes, increased collaboration and delivered working software more frequently compared to the previous waterfall approach.
Check out following slidedeck where i visualized the contents of the official Scrum Guide from scrum.org. This definitely helped me passing my Professional Scrum Master Exam.
Summary of The Scrum Guide in one slide. That's not all you should know about Scrum, but it gives you a guidance especially when studying for a Scrum Master certification.
Check out following slidedeck where i visualized the contents of the official Scrum Guide from scrum.org. This definitely helped me passing my Professional Scrum Master Exam.
Summary of The Scrum Guide in one slide. That's not all you should know about Scrum, but it gives you a guidance especially when studying for a Scrum Master certification.
Covers SCRUM Artifacts topic in detail along with necessary linked topics understanding.
Below are SCRUM Artifacts covered in this presentation:
Product Backlog
Sprint Backlog
Increment / Product Increment
This is a basic-level presentation on the Scrum framework, primarily based on the official Scrum guide. This will be useful for readers who are getting started on Scrum, as well as experienced Scrum practitioners as a quick refresher.
"We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
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."
This is the manifesto for Agile Software Development. Well, In this slide I tried to explain what actually agile is, what it's motive and the benefit at a glance. I rather used to explain by some meaningful picture then description. I also showed here the side by side methodology called Scrum, which is actually current trend at most of our software industries. Well, I guarantee it will not waste your time. Thank you.
Scrum is about Teams producing Results in an agile way. Scrum Teams achieve results anyway they can by using a simple set of rules to guide effort. We will describe scrum as a simple applied model so that a central understanding of scrum can be built. This talk will conclude with a Quick Summary of Scrum.
How to Manage Marketing Projects and People (Without Going Insane)LeadMD
Marketing departments face the perfect storm of issues: too-small budgets leading to too-few people with huge financial return expectations. To keep shifting priorities in check, marketers need to adopt an agile framework, like Scrum, to bring visibility -- and productivity -- to the forefront.
This power point presentation is an introduction to Scrum and covers the following topics:
* Problems with a traditional approach
* What is Scrum?
* Why use Scrum?
* How does Scrum work?
* The Product Owner
* The Scrum Master
* The Team
* The Product Backlog
* Benefits of using a Product Backlog
* The Sprint Backlog
* The Scrum Cycle
* The Burn Down Chart
You can copy, distribute, and use the content of the presentation in accordance to Creative Commons Attribution 2.5 License.
Scrum User Group South Africa
Event # 3: 19 March 2009 in Centurion, Pretoria, South Africa
How to implement Scrum within your organisation?
Presenter: Arrie van der Dussen, Agile Business Manager at www.kaizania.co.za
Covers SCRUM Artifacts topic in detail along with necessary linked topics understanding.
Below are SCRUM Artifacts covered in this presentation:
Product Backlog
Sprint Backlog
Increment / Product Increment
This is a basic-level presentation on the Scrum framework, primarily based on the official Scrum guide. This will be useful for readers who are getting started on Scrum, as well as experienced Scrum practitioners as a quick refresher.
"We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
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."
This is the manifesto for Agile Software Development. Well, In this slide I tried to explain what actually agile is, what it's motive and the benefit at a glance. I rather used to explain by some meaningful picture then description. I also showed here the side by side methodology called Scrum, which is actually current trend at most of our software industries. Well, I guarantee it will not waste your time. Thank you.
Scrum is about Teams producing Results in an agile way. Scrum Teams achieve results anyway they can by using a simple set of rules to guide effort. We will describe scrum as a simple applied model so that a central understanding of scrum can be built. This talk will conclude with a Quick Summary of Scrum.
How to Manage Marketing Projects and People (Without Going Insane)LeadMD
Marketing departments face the perfect storm of issues: too-small budgets leading to too-few people with huge financial return expectations. To keep shifting priorities in check, marketers need to adopt an agile framework, like Scrum, to bring visibility -- and productivity -- to the forefront.
This power point presentation is an introduction to Scrum and covers the following topics:
* Problems with a traditional approach
* What is Scrum?
* Why use Scrum?
* How does Scrum work?
* The Product Owner
* The Scrum Master
* The Team
* The Product Backlog
* Benefits of using a Product Backlog
* The Sprint Backlog
* The Scrum Cycle
* The Burn Down Chart
You can copy, distribute, and use the content of the presentation in accordance to Creative Commons Attribution 2.5 License.
Scrum User Group South Africa
Event # 3: 19 March 2009 in Centurion, Pretoria, South Africa
How to implement Scrum within your organisation?
Presenter: Arrie van der Dussen, Agile Business Manager at www.kaizania.co.za
A couple years ago, a company I was working with, asked me to share with them the use cases and benefits of Scrum. It must have really sparked the management’s interest as they asked me to come up with an Agile implementation strategy for the company. This is the presentation I would like to share with you as I believe many curious, mid size, web development shops out there might be seriously thinking about adopting Agile or some hybrid form to supplement their Waterfall process.
This presentation is about the challenges faced when doing prototypes and to make sure that these prototypes are useful for the developers.
It is about how the prototyping activity fits into the iterative implementation cycles (Scrum Sprints) and how the triangle of UX, development and visual design works together, in particular if external service providers are involved.
In the third Installment of TechXpla Agile webinar Anushree Verma Discussed Scrum Frame Work . Scrum is one of the popular method to reach goal of Agile.
Increase productivity and improve the predictability of software projects. Interest in the Scrum Agile process framework is exploding as companies discover that Scrum enables them to manage software projects with greater reliability and improve responsiveness to customers. This class introduces the skills that project managers and team leaders need to perform the basic steps of a Scrum process for software development.
-Learn how Scrum practices relate to project management fundamentals
-Learn the essentials of Scrum as a software development process
-Learn the three Scrum roles, three Scrum meetings, and three Scrum artifacts
-Project Managers and team leads learn basic planning, tracking, and management skills
-Product Managers learn how to develop and prioritize requirements
-Team members learn how to estimate and break down work
Scrum has garnered increasing popularity in the agile software development community due to its simplicity, proven productivity, and ability to act as a wrapper for various engineering practices promoted by other agile methodologies.
Agile , SCRUM
Introduction
What is Agile Methodology?
What is Scrum?
History of Scrum
Functionality of Scrum
Components of Scrum
Scrum Roles
The Process
Scrum Artifacts
Scaling Scrum
Q & A Session
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.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
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
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.
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
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.
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.
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/
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.
Accelerate your Kubernetes clusters with Varnish Caching
Life B4 and After Scrum
1. The life before and after Scrum Michel Goldenberg CSM/CSP Payam Afkari CSM
2. About this presentation This presentation talks about some cases showing the processes in the IT team before Scrum; How Scrum was implemented; Some problems that appeared during the implementation and how they were solved; What Scrum changed in the IT teams. 2 www.scrumusergroup.ca
3. Michel Goldenberg Agile Coach acting in Montréal area; Over 10 years of experience in IT; Expertise: Coaching people and implementing Scrum in big corporations. Cofounder of Montreal’s Scrum user group 3 www.scrumusergroup.ca
4. Payam Afkari Scrum Master and Business analyst in montreal area Close to 10 years in IT. Cofounder of Montreal’s Scrum user group 4 www.scrumusergroup.ca
5. The waterfall approach Etude opportunite Preliminary analysis Architecture Developpement testing Implementation Request for Change Add pictures www.scrumusergroup.ca 5
6. The waterfall approach Requirement Gathering and analysis Client see for the first time System design Implementation testing Deployment Yes Maintenance Client approval RFC No New functionality
12. Vision Before: Client came with his vision and wanted his solution. After : the team works with the client to validate the needs and to come up with a better vision and solution www.scrumusergroup.ca 12
14. Release planning (Before) Project manager creates the plan and all the activities that he thinks is necessary. The activities are assigned to members . The release date is scheduled (imposed). Every body think they know their job for the project. www.scrumusergroup.ca 14
15. Release Planning (After ) A product backlog is created with the help of the client (product owner, PO); The PO prioritize the product backlog items; Team has an idea of what should be done; A release date can be proposed, based on the performance (velocity) of the team. www.scrumusergroup.ca 15
16. Release planning - Challenges we went through Project manager wants to take control; Work on task instead of activities; Moving from a service provider to a partnership with the client; Identify a PO; Getting the client (PO) to work with the team; Client wants to sign a contracts; Client is hesitant. www.scrumusergroup.ca 16
19. Sprint planning (Before) Activity planning done by the Project manager. No such thing as sprint. No negotiation. www.scrumusergroup.ca 19
20. Sprint planning (After) Team works with the client to prioritize the items that would be done in this sprint; Items broken into tasks; Evaluating the tasks; Commitment to deliver the sprint; Lots of room for negotiation. www.scrumusergroup.ca 20
21. Sprint planning - Challenges we went through Explaining the value of Scrum; Changing the team spirit; Used to being told what to do; Trusting each other; Make developers to talk together; Working together. www.scrumusergroup.ca 21
22. Sprint planning Sprint 1 Sprint planning Story Story Sprint Plan Story Ongoing Done Planned Task Task Story Task Task Task Task Task Task Task Task Task Task Task Task www.scrumusergroup.ca 22
26. Sprint (After) Fewer features; Better quality; Suitable for the client; Easier to manage; Faster feedback; Team spirit. www.scrumusergroup.ca 26
27. Sprint - Challenges we went through Not every one ready for sprinting; Members still need to be told what to do; Hero personality; Zero personality; Collaboration between team member; Team effort vs individual effort; Team commitment vs individual commitment. www.scrumusergroup.ca 27
29. Daily Standup (Before) Not really daily standup; Not for the benefice of the team but rather for the PM management status; Scheduled and driven by the PM. www.scrumusergroup.ca 29
30. Daily Standup(After) For the team; By the team; About the team; For a better product. www.scrumusergroup.ca 30
31. Daily Standup - Challenges we went through PM trying to take control. PM interrupting the team. Members not speaking freely. Focus on what was done yesterday and what will be done today. Keep it short. Keep other discussion for later.
34. Product increment (After) Team decide of the definition of Done; This definition helps up having a potentially shippable product; When ever the PO find it satisfactory, it can be shipped.
35.
36. Focus on the story, even if the functionality is not complete.
39. Sprint review (After ) Demo of working functionnality Assist client with future functionality decision Add/remove functionality Change priority Burndown chart Statistics/metrics Risk/Issues www.scrumusergroup.ca 38
40. Sprint review (Challenges ) Clients attitude. That’s what I want; Organising the presentation with the client’s busy schedule; Client’s feedback: Focus on important things; Client expectation (not finished functionality?); Controlling developers (planning bugs for next sprint).
43. Sprint retrospective - After Retrospection is the heart of Scrum – creating and responding to change about how the team will perform; Retrospective can occur anytime the team feels they need one. www.scrumusergroup.ca 42