The document discusses key principles of agile software development including valuing individuals and interactions over processes, working software over documentation, and customer collaboration over contract negotiation, and describes Scrum as an agile process framework that involves prioritizing a product backlog, conducting daily standups, and delivering working software in sprints for customer review.
For successful Agile projects, Scrums and Sprints are determined by product backlog prioritization, which is driven by the set of customer concerns such as complexity, stability, cost-benefit analysis, system architecture role and reusability. We offer here directions on compiling a prioritization matrix based on the relative importances of a given backlog item.
User Story Writing & Estimation For Testers By Mahesh VaradharajanAgile Testing Alliance
This session aims to introduce the critical aspects of user story formulation like INVEST principle, requirements hierarchy in Agile - with focus on aspects related to Agile Testing, such that it fits into the overall theme of the event. Through an exercise, with Lego blocks, the session will address the following aspects: Testability of user stories and importance of acceptance criteria. Handling NFRs - either as part of acceptance criteria or a new user stories. DoD and accommodating testing efforts as part of user story estimation; Defects as user stories. Dependency management between user stories via story maps.
Talk including Demo for the learning objectives outlined above
For successful Agile projects, Scrums and Sprints are determined by product backlog prioritization, which is driven by the set of customer concerns such as complexity, stability, cost-benefit analysis, system architecture role and reusability. We offer here directions on compiling a prioritization matrix based on the relative importances of a given backlog item.
User Story Writing & Estimation For Testers By Mahesh VaradharajanAgile Testing Alliance
This session aims to introduce the critical aspects of user story formulation like INVEST principle, requirements hierarchy in Agile - with focus on aspects related to Agile Testing, such that it fits into the overall theme of the event. Through an exercise, with Lego blocks, the session will address the following aspects: Testability of user stories and importance of acceptance criteria. Handling NFRs - either as part of acceptance criteria or a new user stories. DoD and accommodating testing efforts as part of user story estimation; Defects as user stories. Dependency management between user stories via story maps.
Talk including Demo for the learning objectives outlined above
Technique To Prioritize Key Tasks In Agile Process Powerpoint Presentation Sl...SlideTeam
“You can download this product from SlideTeam.net”
A technique that helps the organization to prioritize various activities in their software development project is known as prioritization technique in agile. The following presentation provides an overview of the project and implements agile methodology in the same, once agile methodology is implemented a list of priority task is identified with the help of multiple techniques such as MoSCoW, Kano Model and relative average method. This presentation is helpful for IT organizations and IT managers with an objective to optimize their software development process by identifying tasks that are to be given utmost priority with the help of different types of prioritization techniques. Initially this presentation provides an overview of the project as it displays the project details and the structure of the project team which has scrum master, developers and operational team. Once the project overview is taken the approach for software development is decided. Once the workings and operations of the project are decided, various prioritization techniques are utilized in order to identify key priority tasks. These techniques can be MoSCoW or Must have, should have, could have and would have or Kano model or weighted average method. After utilizing these techniques multiple key priority tasks are identified. After carefully understanding the priority tasks the cost of the entire project is highlighted and the performance of the project is tracked with the help of various KPIs or key performance indicators. https://bit.ly/30FTo2U
Agile product owners-what ails them (philly_dayofagile)Anupam Kundu
Presentation I used at Philadelphia Day of Agile (#dayofagile) http://dayofagile.org/agenda.
It was received well within the audience. Any comments are welcome...
CRM 101: Session 3: Less is More - How to Plan a Successful CRM RolloutSugarCRM
Most implementations fail because they are too complex. Technology Advisors’ Sam Biardo explains the difference between thorough and complicated and will illustrate ways you can plan for the important parts of a CRM rollout without getting sidetracked by details that aren’t so important. Learn what causes project failures, how to prevent them, and what techniques you can use to make your CRM project successful.
This slide share will help users to understand the agile software development methodology and how does it work. It also defines the whole process to implement scrum methodology.
Technique To Prioritize Key Tasks In Agile Process Powerpoint Presentation Sl...SlideTeam
“You can download this product from SlideTeam.net”
A technique that helps the organization to prioritize various activities in their software development project is known as prioritization technique in agile. The following presentation provides an overview of the project and implements agile methodology in the same, once agile methodology is implemented a list of priority task is identified with the help of multiple techniques such as MoSCoW, Kano Model and relative average method. This presentation is helpful for IT organizations and IT managers with an objective to optimize their software development process by identifying tasks that are to be given utmost priority with the help of different types of prioritization techniques. Initially this presentation provides an overview of the project as it displays the project details and the structure of the project team which has scrum master, developers and operational team. Once the project overview is taken the approach for software development is decided. Once the workings and operations of the project are decided, various prioritization techniques are utilized in order to identify key priority tasks. These techniques can be MoSCoW or Must have, should have, could have and would have or Kano model or weighted average method. After utilizing these techniques multiple key priority tasks are identified. After carefully understanding the priority tasks the cost of the entire project is highlighted and the performance of the project is tracked with the help of various KPIs or key performance indicators. https://bit.ly/30FTo2U
Agile product owners-what ails them (philly_dayofagile)Anupam Kundu
Presentation I used at Philadelphia Day of Agile (#dayofagile) http://dayofagile.org/agenda.
It was received well within the audience. Any comments are welcome...
CRM 101: Session 3: Less is More - How to Plan a Successful CRM RolloutSugarCRM
Most implementations fail because they are too complex. Technology Advisors’ Sam Biardo explains the difference between thorough and complicated and will illustrate ways you can plan for the important parts of a CRM rollout without getting sidetracked by details that aren’t so important. Learn what causes project failures, how to prevent them, and what techniques you can use to make your CRM project successful.
This slide share will help users to understand the agile software development methodology and how does it work. It also defines the whole process to implement scrum methodology.
In this advanced business analysis training session, you will learn Use Cases and Its use in Agile World. Topics covered in this session are:
• Requirements Principles
• Identify the principles that lead to effective Agile requirements
• Setting the Stage for Requirements
• Establish the vision as the foundation of Agile requirements
• Levels of Agile Requirements
• Identify the different level of Agile requirements for effective requirements
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
Agile Methodology explained simply, for those unfamiliar. Great to change organisations from waterfall to agile ways of working. Step by Step. Agile Project Delivery simplified. Stakeholders will understand clearly what their role is in implementation. Answers common questions, what is a Scrum Master etc
In this session we'll discuss how agile analysis and project management processes can be applied to Drupal implementation. We'll discuss the setting of expectations for stakeholders when planning and executing a Drupal project, and how to avoid the typical pitfalls. You'll also learn how a multi-disciplined project team can smooth your project execution, and increase your chance for overall success.
Building a Product? the knowledge you will acquire will help with product management and the use of agile scrum to build products. The training provides fundamental guide to building the best solution in the world with some of the best tips, templates and guides in terms of leading trends. This will bring your IDEAS to Live.
Inside Gainsight’s New Post-Sales Structure: Reorganizing the Team to Drive C...Gainsight
In this webinar, Allison Pickens, Gainsight's VP of Customer Success, will give you a detailed explanation of our new org chart as well as the philosophy behind the changes. She'll offer strategies on how to apply these principles and tactics to your own Customer Success team.
Nowadays, all organization works on the principle of Agile methodology, there might be many people like me who don't even know the meaning of Agile and Scrum Master.
I have made the docs from the source available on the internet with all due respect have copied the URL LINK.
The motive behind posting this is you can get an Agile understanding in one document.
Thanks
Feature Prioritization Techniques for an Agile PMs by Microsoft PMProduct School
Main takeaways:
-PMs don't need a lot of data points to prioritize the features for the upcoming sprint. They just need to identify the relevant one's.
-PMs should be skilled to strike the balance between agility in making decisions and accuracy of perceived outcomes
-PMs should be able to prioritize the feature requests with minimum data points available and optimum techniques
How We Reorganized Our Entire Post-Sales OrganizationGainsight
One of Gainsight's principles is to "Carry the Torch" for the Customer Success industry. We've shared a lot about innovations in our processes, but not as much about our organization. In this session, Allison Pickens, VP of Customer Success and Business Operations at Gainsight, will share the story of how we re-organized post-sales to drive success for our customers.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
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.
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.
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.
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.
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/
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.
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.
2. Individuals and interactions over processes and tools
Working software over comprehensive
documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
AGILE MANIFESTO
3. 1. Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes
harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and
support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and
users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity–the art of maximizing the amount of work not done –is essential.
11. The best architectures, requirements, and designs emerge from self -organizing
teams.
12. At regular intervals, the team reflects on how to become more effective, then
tunes and adjusts its behavior accordingly.
THE ’12’ PRINCIPLES
5. Project development is performed in 2-4 weeks
Product Owner Creates a prioritized backlog
Highest Priority features delivered first
The team meets each day to assess progress
At the end of the sprint, the deliverables are reviewed by the
business customers
The team reflects on the process
SCRUM
6. SCRUM IS A PROCESS
ProductBacklog
Prioritized product features desired by client
15 min. Daily meeting.
Team members respond to basics:
A. What did you do since last Scrum Meeting?
B. Do you have any obstacles?
C. What will you do until next Scrum Meeting?
24 hours Scrum
30
DAYS
24
HOURS
New
functionality
Backlog
Items
expanded by
team
Sprint Backlog
Features
assigned to
sprint
7. Minimum viable feature (MVF or MVP)
How do you determine if you need more resources in a Scrum
team?
How big is a Scrum team? 7 +/- 2
Who owns the Product Backlog?
For every Sprint we should have a goal?
SCRUM GENERAL RULES
8. Revisit our Team Charter
Revisit our DoD
DEVELOPMENT TEAM
9. Determines a shared understanding of what “Done means”
Defines the notion that the Product Increment is of high
quality to be shippable
Work remaining “Not Done” is PBI that goes into the Product
Backlog
“When the Product Increment is delivered, it needs to be
"done" according to a shared understanding of what "done"
means. This definition is different for every Scrum Team, and
as the team matures, the Definition of Done will expand and
become more stringent.”
http://agileatlas.org/atlas/scrum#product-increment
DOD
10. DEFINE DOD
With a Sprint
Code is
checked-in
Code Review
Is Complete
All unit tests
Are passing
With a PBI
Integration
Test Passing
Performance
Test Passing
With a Release
Security
Audit
Passing
Regression
Test Passing
Acceptance
Criteria
Passing
11. USER STORY REVIEW
What’s a User Story? It’s a simple, clear, short description of
a customer valued functionality.
3 parts:
Written Description used for planning
Conversation to flush out the details
Tests to determine completeness
3C’s: card, conversation, confirmation
Representation rather than documentation.
12. As a {role}, I want {feature} so that {value}
Define the acceptance criteria for each user story
Attributes of a good user Story
Independent
Negotiable
Valuable
Estimate-able
Small
Test-able
USER STORY FORMAT
13. USER STORY TEMPLATE
Title Priority
As a [type of user], I want to [goal/functionality] so that
[business value]
Notes:
Assumptions:
Constraints:
Estimate:
14. USER STORY EXAMPLE
Check Out using Credit Card 25
As a book shopper, I can checkout using my credit card so that I
can purchase a selected book.
Notes: Support MC, Visa, AMEX
Constraint: Must Use Chase Clearinghouse
13 pts?
15. ACCEPTANCE CRITERIA
Ask the User who’s creating the story to also capture the
acceptance criteria. The acceptance criteria is what’s used to
measure that the story is complete.
Format for the Acceptance Criteria
Given [context]
When [some event]
Then [Outcome]
16. ACCEPTANCE CRITERIA - EXAMPLE
Checkout using Credit Card
Test with valid mc, visa, amex: pass
Test with other credit cards: fails
Test with expired cc: fails
Test with invalid cvv: fails
Test with invalid zip: fails
17. PERSONAS?
Personas are used to represent your market segments or
system users into stakeholders.
Use personas to help you define your user stories.
SFDC – Roles & Profiles
Market Segments (Product specific)
Data to Include: Name, Photo, Title, Description
Data to consider: User responsibilities, Domain Knowledge,
Success Goals, Pain Points, Expected frequency of system
usage…
18. PERSONAS EXAMPLE
About:
His responsibility is to close big
deals on key accounts. The
company needs a process to
identify key accounts so that he
can maximize his time. Juan is a
CRM and mobile savvy user who’s
actively looking for the CRM to
provide him with the most
accurate sales information.
Context:
Juan the Sales rep is always on the road. He needs
access to key accounts and all his contacts on a
mobile device. He’s always working on closing his
next deal. Depends heavily on Sales Ops.
Implications:
Wants a process to identify key
account & related opportunities.
Is keen on being 100% mobile.
He needs reports and dashboards
that show the key account pipeline
on mobile. Also, he wants to see all
previous sales for each account that
he visited.
19. USER STORIES BEST PRACTICES
Write the story from the User’s perspective
Understand the User’s goal of the story
Understand the User’s value from the story **
Use human users, unless you are integration systems.
Avoid Using generic “user” or “as a customer”
Think Personas.
What are the Pain Points that the User’s have?
What’s the value that we are trying to build?
Capture the success criteria. This is very important.
20. USER STORIES FAQ
We have user stories that are not in this format. Can we use
the stories? Yes, re-format the stories and capture the
Acceptance Criteria.
We have user stories that are not depicted as humans? This is
common when systems are being integrated and that one
system, needs the functionality in order to capture value.
We have user stories that define what technical approach
should be used? User stories should not outline a specific
technical solution, rather they should depict a business
function that a user needs and the value.
21. ADDITIONAL TEAM ACTIVITIES
Create Story Maps: This is a key activity that will be covered
with another presentation.
Product Owner prioritizes the user stories in the backlog daily.
The development team will take the user stories and break
them down into tasks [Similar to WBS] during Sprint Planning.
Some user stories will be moved into “Epics” if they are to big
to complete during the sprint timeframe.
22. Is held at the end of each Sprint.
Dedicated time for the team to focus on:
What was learned during the sprint.
What can the team improve on for the next sprint.
1-2 hours of retrospective time for each week of development
Who should attend?
Development team
Product owner
The 12 Principle – “At regular intervals, the team reflects on
how to become more effective, then tunes and adjusts its
behavior accordingly.”
Teams that effectively use retrospectives feel a strong sense
of empowerment as they continually improve the way they
work.
SPRINT RETROSPECTIVE
23. AWS PRODUCT ROLLOUT - TEMPLATE
Vision
Submit and store content from the Enterprise Content Repository into
AWS Cloud. And provide a unified delivery service to partners.
Mission
Provide Enterprise Services (ES) that enables systems & users to
submit content into the AWS cloud. The ES should be automated and
provide mediation, security and delivery capabilities.
Success Criteria
The Enterprise Services (ES) must be operational by MM-DD-YYYY
The following content set must be accessible: A, B, C and D.
The ES will provide reports on the content submitted and retrieved.
The following Service Level Agreements – SLA’s must be met…
24. Is a metaphor developed by Ward Cunningham to help us deal
with a common problem
“Doing things quick and dirty set us up with a technical debt,
which is similar to financial debt.
Leads to extra effort that we have to do in the future(as a form of
payment on the debt)
Two choices – continue to make payments on the interest or pay
down the principal (refactoring)
The savvy developer treats technical debt just as the
entrepreneur does financial debt. They use it. It speeds
delivery, so long as it is properly managed.
http://www.c2.com/cgi/wiki?TechnicalDebt
TECHNICAL DEBT
25. Calculation of the Debt
Debt(in man days) = cost_to_fix_duplications +
cost_to_fix_violations +
cost_to_comment_public_API +
cost_to_fix_uncovered_complexity +
cost_to_bring_complexity_below_threshold +
cost_to_cut_cycles_at_package_level
CALCULATING TECHNICAL DEBT