Agile
Testing Keywords
Hi again,
Let’s explore Agile in its various definitions
or keywords.
Here I will explain
import keywords or concepts which daily based use in Agile methodology.
Agile
testing is continuous testing, which goes hand in hand with development
work and provides an ongoing feedback loop into the development process. esters
are now part of the agile development team or we can say Agile testing is
a process where QA follows in a dynamic environment where testing requirements
keep changing according to the customer needs
Ø Project Owner: As name suggest, Customer of Product who has the
responsibility of managing the product backlog. Works with end users and
customers and provide proper requirement to the team to build the proper
product
Ø Scrum Master: who works with scrum team to make sure each sprint
gets complete on time. Scrum master ensure proper work flow to the team.
Ø Scrum Team: Each member in the team should be self-organized,
dedicated and responsible for high quality of the work
Ø User Stories: User Stories defines the actual business
requirement. Generally created by Business owner
Ø Epic: A group of related user stories is called an
Epic.
Ø Task: To accomplish the business requirements development
team create tasks.
Ø Task board: Task board is dash board which shows progress of
the project with below mentioned elements
·
To
Do : Tasks that can be
worked on
·
In
Progress : Tasks in progress
·
To
Verify : Tasks pending for
verification or testing
·
Done
: Completed tasks
Ø Test Driven Development: Test-first development technique
in which we add a test first before we write a complete production code. Next
we run the test and based on the result refactor the code to fulfill the test
requirement
Ø Scrum Ban: This is a software development model which is
combination of scrum and kanban. Scrumban is considered for maintenance projects
in which there are frequent changes or unexpected user stories
Ø ABI: Application Binary Interface defines the low level
interface between an application and the operating system.
Ø Zero sprint: Pre step to the first sprint. Activities like
setting development environment, preparing backlog etc needs to be done before
starting of the first sprint and can be treated as Sprint zero
Ø Spike : Solution to resolve some technical issues or
design problem in the project which needs to be resolved first
Ø Daily stand up meeting: Daily stand up meeting is
essential for any team in which
·
Team
discuss about how much work has been completed.
·
What
are the plans to resolve technical issues?
·
What
steps need to do to complete the projects etc
Ø Tracer Bullet: Spike with the current architecture or the current
set of best practices to examine how an end-to-end process will work and
examine feasibility
Ø Velocity of Sprint: This parameter is calculated as a percentage of a
40 hours weeks then completed story points * team capacity where If capacity is
measured in man hours then Completed story points / team capacity
Ø Agile manifesto: Agile manifesto defines an iterative and
people-centric approach to software development with 4 key values and 12
principals
Ø Re-factoring : To improve the performance, the existing code is
modified without changing functionality
Ø Sprint Backlog: It is a subset of the product backlog owned by
development team and commits to deliver it in a sprint.
Ø Product Roadmap: A product
roadmap is the holistic view of product features that create the product
vision.
Happy testing!!!
Comments
Post a Comment