In this quality assurance training session, you will learn Agile in QA. Topics covered in this course are:
• Introduction to Agile
• Agile - Manifesto
• Agile over Traditional Method
• Principles of Agile
• Roles in Agile
• What is a User Story?
• Relationship of User Stories and Tasks
• How an Agile Team Plans its Work?
• When a Story is Done
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
Agile development model in Software Testing, be it Manual Testing or automation; is likewise a sort of incremental model. In this model, the software is developed in incremental, quick cycles
In this Business Analysis Training, you will learn Agile Methodology. Topics covered in this session are:
• Agile Approach
• What is Agile?
• What does the Agile Manifesto Mean?
• Principles of Agile
• Central: Incremental and Iterative Development
• Agile Methods
• Scrum Lifecycle
• SCRUM team
• Agile Methods – Scrum
For more information, click on this link:
https://www.mindsmapped.com/courses/agile-and-scrum/introduction-to-agile/
Agile development model in Software Testing, be it Manual Testing or automation; is likewise a sort of incremental model. In this model, the software is developed in incremental, quick cycles
In this Business Analysis Training, you will learn Agile Methodology. Topics covered in this session are:
• Agile Approach
• What is Agile?
• What does the Agile Manifesto Mean?
• Principles of Agile
• Central: Incremental and Iterative Development
• Agile Methods
• Scrum Lifecycle
• SCRUM team
• Agile Methods – Scrum
For more information, click on this link:
https://www.mindsmapped.com/courses/agile-and-scrum/introduction-to-agile/
In this interactive session, Scott Ambler explores a vitally important, nitty-gritty, down-in-the-weeds aspect of agile—how to take an agile model-driven development (AMDD) approach to enhance and scale your software delivery capabilities. Correctly applied, AMDD enhances your modeling and documentation efforts, streamlines agile development, and reduces false starts and rework. Scott addresses critical modeling issues that pertain to all agile projects—how to successfully model the complexities of modern-day software without getting bogged-down in mountains of paperwork, how to document systems in an agile manner, how to scale agile development methods with an agile approach to modeling and documentation, how to take an evolutionary approach to user interface and database design, and how modeling extends and supports test-driven development to address the full exploration of requirements, architecture, and design. Join Scott to dig into this vital—yet often ignored—aspect of agile development.
One of the enhanced method for requirement determination is agile methodology in system analysis phase, and this slide presents the strategies available under agile methods for requirement determination with maximum user involvement for developing an information system.
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 document we will explain software development life cycle (SDLC), various steps/stages in SDLC and software development methodologies in detail. Original blog posted here on: http://www.satejinfotech.in/what-is-software-development-lifecycle/
This PPT throws light on some of the essential elements of the Agile methodology which has become crucial to ensure quality in this day and age. To know more on agile methodology, Scrum Model, Agile Principles and Scrum Board go through this presentation as well as the ones coming soon.
A fair analysis of the Agile Methodology. A quick comparison of Agile and Waterfall to clear up misconceptions about the two. Scalability is a major issue with Agile and is worth considering if you're not a large software company.
In this interactive session, Scott Ambler explores a vitally important, nitty-gritty, down-in-the-weeds aspect of agile—how to take an agile model-driven development (AMDD) approach to enhance and scale your software delivery capabilities. Correctly applied, AMDD enhances your modeling and documentation efforts, streamlines agile development, and reduces false starts and rework. Scott addresses critical modeling issues that pertain to all agile projects—how to successfully model the complexities of modern-day software without getting bogged-down in mountains of paperwork, how to document systems in an agile manner, how to scale agile development methods with an agile approach to modeling and documentation, how to take an evolutionary approach to user interface and database design, and how modeling extends and supports test-driven development to address the full exploration of requirements, architecture, and design. Join Scott to dig into this vital—yet often ignored—aspect of agile development.
One of the enhanced method for requirement determination is agile methodology in system analysis phase, and this slide presents the strategies available under agile methods for requirement determination with maximum user involvement for developing an information system.
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 document we will explain software development life cycle (SDLC), various steps/stages in SDLC and software development methodologies in detail. Original blog posted here on: http://www.satejinfotech.in/what-is-software-development-lifecycle/
This PPT throws light on some of the essential elements of the Agile methodology which has become crucial to ensure quality in this day and age. To know more on agile methodology, Scrum Model, Agile Principles and Scrum Board go through this presentation as well as the ones coming soon.
A fair analysis of the Agile Methodology. A quick comparison of Agile and Waterfall to clear up misconceptions about the two. Scalability is a major issue with Agile and is worth considering if you're not a large software company.
Butch Landingin, CTO of Orange & Bronze Software Labs, talks about the Agile Methodology for the Philippine Software Industry Association's Enablement Seminar on April 27 at the AIM.
About O&B:
Orange & Bronze is an offshore product and software development firm in the Philippines, is one of the first companies in Asia to use and advocate Agile Software Development, and has been using it since our inception in 2005, back when Agile was still an emerging movement. O&B offers training courses for Agile with Scrum and XP - these classes were developed and are taught by some of the Philippines' well-known and respected Agile / Scrum coaches and practitioners, and uses the format trusted by some of the best companies in the Philippines.
Increasing the company's profitability and impact is the dream of every company. Nowadays Agility / Agile is the buzz word and the whole world want's it but most of the time companies are confused about how we can achieve the agility dream.
The written material provides a visible how, why and what of agility and what the best practices we need to execute to achieve agility.
This deck gives an overview on the following key areas.
1) Agile Development Principle
2) Scrum Framework
3) User Story Creation
4) Definition of Done
5) Agile – Retrospective
6) Development – Metrics
7) Agile vs Traditional Development Approach
- Agile values and manifesto
- Scrum in details
- Themes, epics, and user stories
- Combining and splitting user stories.
- What could go wrong in Scrum and why?
- Overview in Other Agile methodologies:
- XP Agile Methodology
- KanBan Agile Methodology.
The Agile PMP: What PMPs need to know to compete in today's marketProjectCon
PROJECTCON | AGILECON Midwest 2019 in Indianapolis on May 10, 2019
Presenter: DJ McCord
The Agile PMP: What PMPs need to know to compete in today's market
Agile is not a buzz word. Agile is here to stay. If you organization has not yet adopted Agile in some way, shape, or form, it will soon. In 2018, PMI added Agile to the PMBOK and the PMP exam. This session will discuss why it is critical that PMPs understand what Agile is, how a PMP can improve their marketability, the new Agile content added to the PMBOK, how a PMP can learn the new Agile content included in the PMBOK, and what certifications a PMP can obtain to make them a triple threat in the industry.
Attendees will learn:
An overview of Agile
Why PMPs need to know Agile
Agile additions to the PMBOK 6th Edition
How a PMP can re-up their certification to include Agile
What combination of certifications a PMP should hold to gain a competitive advantage
Event Website: https://projectconevent.com
LinkedIn: https://www.linkedin.com/company/projectcon-llc
Facebook: http://www.facebook.com/ProjectConEvent
Twitter: http://www.twitter.com/projectconevent
YouTube: https://www.youtube.com/channel/UCLLG1SGPs1L5YLoFndvGGhQ
Instagram: https://www.instagram.com/projectconevent
Presentation Slides: https://slideshare.com/projectcon
Post Event Trailer: https://youtu.be/1_RzFBnZ7bo
ProjectCon AgileCon Project Management
Agile is a mindset that includes respect, collaboration, improvement and learning cycles, pride in ownership, focus on delivering value, and the ability to adapt to change - often used for the successful, iterative implementation of products that a team builds.
Agile management, or agile process management, or simply agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development.
In this quality assurance training session, you will learn HP LoadRunner. Topics covered in this course are:
• Introduction to Performance Testing
• Why do performance testing?
• Load Testing
• Stress Testing
• Volume testing
• Performance testing tool
• Why LoadRunner
• Why LoadRunner
• LoadRunner Components
• LoadRunner Architecture
• How LoadRunner Works
• LoadRunner load testing process
• The script development process in VUGen
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn VBScript in testing. Topics covered in this course are:
• Overview of VB Script
• Variables
• Rules for Declaring Variables
• Option Explicit
• Comments
• Arrays
• Functions
• Calling a Function
• Function Parameters and return
• Sub Procedures
• Types of Conditional Statements
• Types of Looping Statements
• Loop Control Statements
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Selenium WebDriver Testing. Topics covered in this course are:
• Overview of Selenium WebDriver
• Get Selenium WebDriver Java
• Selenium – JAVA Configuration
• WebDriver in Different Browsers
• Open Application
• Browser Settings
• Locating Elements
• Object Identification Methods
• Locator ID, Name
• Locators –LinkText, partialLinkText, CSS, CSS
• Accessing different objects in application
• Switch Window
• Wait in WebDriver
• Verifications
• WebTable
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Core Java for Selenium Testing. Topics covered in this course are:
• What is JAVA?
• Steps to install Java for Development
• What is IDE?
• Eclipse
• Variables and Types
• Conditions
• Loops
• Arrays
• Oops Concepts
• Class and Object
• Encapsulation
• Inheritance
• Polymorphism
• Abstraction
• Java Access Modifiers
• Constructor in Java
• Errors & Exceptions
• Exceptions handling
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn introduction to automation testing. Topics covered in this course are:
• Introduction
• Why Automated Testing?
• What can I Automate?
• Test Automation Process
• Automation Tool
• Automation Framework
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn HP ALM QC. Topics covered in this course are:
• HP ALM Overview
• HP ALM Solution
• HP ALM Segments
• QA Process
• Requirements
• Test Plan
• Test LAB
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Defect Life Cycle. Topics covered in this course are:
• Defect Life Cycle
• Defect States
• Defect Content
• Severity Vs Priority
• Severity Levels
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Testing Concepts and Manual Testing. Topics covered in this course are:
• Overview of Testing Life Cycle
• Testing Methodologies
• Black Box Testing
• White Box Testing
• Gray Box Testing
• Integration Testing
• System Testing
• Regression Testing
• User Acceptance Testing (UAT)
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Introduction to Software Testing. Topics covered in this course are:
• Agile Approach
• What does the Agile Manifesto Mean?
• 12 Principles of Agile
• Central: Incremental and Iterative Development
• Agile Methods
• Scrum Lifecycle
• Agile Methods – Scrum
• Scrum Values
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Introduction to Software Testing. Topics covered in this course are:
• SDLC and Quality Standard
• What is SDLC and Stages
• Phases of SDLC
• SDLC Models
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Introduction to Software Testing. Topics covered in this course are:
• Defect/Bugs in Software Testing
• Quality Team Roles and Responsibilities
• Career options available for a Test Engineer
• Testing Market and Opportunities
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Test case design. Topics covered in this course are:
• Test Case Design and Techniques
• Black-box: Three major approaches
• Steps for drawing cause-Effect Diagram:
• Behavior Testing
• Random Testing
• White Box Techniques
• Path Testing
• Statement Coverage
• Data Flow Testing
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Testing Strategies and Planning. Topics covered in this course are:
• Test Strategy and Planning
• Test Strategy Document
• Test Planning
• Test Estimation Techniques
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Testing Management. Topics covered in this course are:
• Requirement Management
• Configuration Management
• Project Management
• Risk Management
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
In this quality assurance training session, you will learn Testing Types. Topics covered in this course are:
• Types of Testing
• Start and Stop of Testing
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
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.
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.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
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.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
2. Page 2Classification: Restricted
Agenda
• Introduction to Agile
• Agile - Manifesto
• Agile over Traditional Method
• Principles of Agile
• Roles in Agile
• What is a User Story?
• Relationship of User Stories and Tasks
• How an Agile Team Plans its Work?
• When a Story is Done
3. Page 3Classification: Restricted
Introduction
• Agile is a software development methodology to build a software
incrementally using short iterations of 1 to 4 weeks so that the
development process is aligned with the changing business needs.
• Instead of a single-pass development of 6 to 18 months where all
the requirements and risks are predicted upfront
• Agile adopts a process of frequent feedback where a workable
product is delivered after 1 to 4 week iteration.
4. Page 4Classification: Restricted
Agile - Manifesto
• In February 2001, at the Snowbird resort in Utah, 17 software
developers met to discuss lightweight development methods. The
outcome of their meeting was the following Agile Manifesto for
software development −
• We are uncovering better ways of developing software by doing it
and helping others do it. Through this work, we have come to
value −
6. Page 6Classification: Restricted
Agile - Manifesto
• 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.
8. Page 8Classification: Restricted
Principles of Agile
• Customer Satisfaction − Highest priority is given to satisfy the
requirements of customers through early and continuous delivery
of valuable software.
• Deliver a Working Software − Deliver a working software
frequently, ranging from a few weeks to a few months, considering
shorter time-scale.
• Measure the Progress as per the Working Software − Working
software is the key and it should be the primary measure of
progress.
• Welcome Change − Changes are inevitable during software
development. Ever-changing requirements should be welcome,
even late in the development phase. Agile processes should work
to increase customers' competitive advantage.
• Collaboration − Business people and developers must work
together during the entire life of a project.
9. Page 9Classification: Restricted
Principles of Agile
• Motivation − Projects should be built around motivated
individuals. Provide an environment to support individual team
members and trust them so as to make them feel responsible to
get the job done.
• Face-to-face Conversation − Face-to-face conversation is the most
efficient and effective method of conveying information to and
within a development team.
• Self-organized Teams − An agile team should be self-organized and
should not depend heavily on other teams because the best
architectures, requirements, and designs emerge from self-
organized teams.
• Maintain Constant Pace − Agile processes aim towards sustainable
development. The business, the developers, and the users should
be able to maintain a constant pace with the project.
10. Page 10Classification: Restricted
Principles of Agile
• Monitoring − Pay regular attention to technical excellence and
good design to enhance agility.
• Simplicity − Keep things simple and use simple terms to measure
the work that is not completed.
• Review the Work Regularly − Review the work done at regular
intervals so that the team can reflect on how to become more
effective and adjust its behavior accordingly.
12. Page 12Classification: Restricted
Roles in Agile
• Scrum Master - is a team leader and facilitator who helps the team members to
follow agile practices so that they can meet their commitments.
• The responsibilities of a scrum master are -
• To enable close co-operation between all roles and functions.
• To remove any blocks.
• To shield the team from any disturbances.
• To work with the organization to track the progress and processes of the
company.
• To ensure that Agile Inspect & Adapt processes are leveraged properly
which includes
• Daily stand-ups,
• Planned meetings,
• Demo,
• Review,
• Retrospective Meetings, and
• To facilitate team meetings and decision-making process.
13. Page 13Classification: Restricted
Roles in Agile
• Product Owner - is the one who drives the product from business
perspective.
• The responsibilities or a Product Owner are -
• To define the requirements and prioritize their values.
• To determine the release date and contents.
• To take an active role in iteration planning and release planning
meetings.
• To ensure that team is working on the most valued requirement.
• To represent the voice of the customer.
• To accept the user stories that meet the definition of done and
defined acceptance criteria.
14. Page 14Classification: Restricted
What is a User Story?
• A user story is a requirement which defines what is required
by the user as functionality.
• During release planning, a rough estimate is given to a user
story using relative scale as points. During iteration planning,
the story is broken down into tasks.
15. Page 15Classification: Restricted
Relationship of User Stories and Tasks
• User story talks about what is to be done. It defines what a
user needs.
• Task talks about how it is to be done. It defines how a
functionality is to be implemented.
• Stories are implemented by tasks. Each story is a collection of
tasks.
• User story is divided into tasks when it is planned in current
iteration.
• Tasks are estimated in hours,
• Stories are validated using acceptance tests.
16. Page 16Classification: Restricted
How an Agile Team Plans its Work?
• An Agile team works in iterations to deliver user stories where each
iteration is of 10 to 15 days. Each user story is planned based on its
backlog prioritization and size. The team uses its capacity − how many
hours are available with team to work on tasks − to decide how much
scope they have to plan.
17. Page 17Classification: Restricted
When a Story is Done
The team decides what done means. The criteria may be −
• All tasks (development, testing) are completed.
• All acceptance tests are running and are passed.
• No defect is open.
• Product owner has accepted the story.
• Deliverable to the end-user.
