Buscar
Estás en modo de exploración. debe iniciar sesión para usar MEMORY

   Inicia sesión para empezar

SDET Flashcards - Agile


🇬🇧
In Inglés
Creado:


Public
Creado por:
Ed Howard


0 / 5  (0 calificaciones)



» To start learning, click login

1 / 13

[Front]


What is agile? List some of Agile Frameworks?
[Back]


Agile is a general approach to software development. All agile methods emphasize teamwork, frequent deliveries of working software, close customer collaboration, and the ability to respond quickly to change. Scrum, Kanban, ScrumBan, Extreme Programming

Practique preguntas conocidas

Manténgase al día con sus preguntas pendientes

Completa 5 preguntas para habilitar la práctica

Exámenes

Examen: pon a prueba tus habilidades

Course needs 15 questions

Aprenda nuevas preguntas

Modos dinámicos

InteligenteMezcla inteligente de todos los modos
PersonalizadoUtilice la configuración para ponderar los modos dinámicos

Modo manual [beta]

El propietario del curso no ha habilitado el modo manual
Modos específicos

Aprende con fichas
Expresión oralResponde con voz
Expresión oral y comprensión auditivaPractica la pronunciación

SDET Flashcards - Agile - Marcador

1 usuario ha completado este curso

Ningún usuario ha jugado este curso todavía, sé el primero


SDET Flashcards - Agile - Detalles

Niveles:

Preguntas:

13 preguntas
🇬🇧🇬🇧
What is agile? List some of Agile Frameworks?
Agile is a general approach to software development. All agile methods emphasize teamwork, frequent deliveries of working software, close customer collaboration, and the ability to respond quickly to change. Scrum, Kanban, ScrumBan, Extreme Programming
How is agile methodology different from the traditional waterfall process?
In agile, features are delivered frequently so that the testing is done at the same time as development. Test time is short because small features need to be tested at once. Changes are welcomed. Waterfall: changes are hard and testing takes place at the end of the project.
How long is your sprint?
2 weeks long or 3 weeks long sprint.
What’s a user story?
User stories or requirements, are short and simple descriptions of capabilities. They are written from the perspective of a user or customer of the system.
What is an epic?
An epic is a large user story that cannot be delivered as defined within a single Sprint .It is large enough to be split into smaller user stories.
What is spike?
Spike is the type of story where the team needs to do some research related to the design or technical issues. Spikes will have 0 story points.
What is a parking lot?
A problem not relating to the entire team that requires a separate meeting with those who are involved.
Explain what Velocity is in Agile?
The sum of story points that a scrum team completes over a sprint. It figures out how much work a team can complete in a sprint to finish a project.
How do you track your progress in a sprint?
The progress is tracked by a “Burn-Down chart”. A burndown chart is a graphical representation of work left to do versus time.
What is DoD? How is this achieved?
DoD stands for Definition of done. It is achieved when ● The story development is complete, ● QA complete ● Story regression is complete ● The feature is eligible to be in production.
What challenges have you had in an agile environment?
● Changing of Requirements. ● Not Enough Information on the Story ● Estimating Time For Completing Task ● Waiting on Development to be completed before testing
Is it possible that you come across different story points for development and testing efforts? In that case how do you resolve this conflict?
Yes, this is a very common scenario. There may be a chance that the story point given by the development team is, say 3 but the tester gives it 5. In that case both the developer and tester have to justify their story point, have discussion in the meeting and collaborate to conclude a common story point.
You are in the middle of a sprint and suddenly the product owner comes with a new requirement, what will you do?
In an ideal case, the requirement becomes a story and moves to the backlog. Then based on the priority, the team can take it up in the next sprint. But if the priority of the requirement is really high, then the team will have to accommodate it in the sprint but it has to be very well communicated to the stakeholders that incorporating a story in the middle of the sprint may result in spilling over a few stories to the next sprint.