Onlinecourses55 - Start page
Home
LOGIN
REGISTER
LOGIN
REGISTER
Seeker
Test Effective User Stories
Agenda
1st QUESTION: What are User Stories?
Detailed technical specifications
Rigid legal contracts
Marketing documents
Brief descriptions of functionality from the user's point of view
2nd QUESTION: What is the common format of a User Story?
As
, I want
, For
Start, Development, Conclusion
Problem, Solution, Cost
Date, Time, Place
3rd QUESTION: What do Acceptance Criteria ensure?
For the story to be long
That the story is fun
That the story has been implemented correctly (is DONE)
That the story is cheap
4th QUESTION: What should a good User Story focus on?
On the technical solution
In the problem or value to the user
In the graphic design
In the database
QUESTION 5: Who is responsible for finding the technical solution for a story?
The customer
The Development Team
Product Owner
The Scrum Master
QUESTION 6: What format is commonly used for Acceptance Criteria?
Given-When-Then (Given-When-Then)
If-Then-If not
Start-End
Do-Check-Act
7TH QUESTION: What does a user story avoid by focusing on the problem?
Prescribe technical solution
Deliver value
Collaboration
The conversation
8th QUESTION: What does the "For
" part represent in the story format?
The delivery date
The cost of development
The motivation or benefit behind the objective
The name of the developer
Send
This test is only available to students who have purchased the course
INCORRECT QUESTIONS
Previous
Next
Are there any errors or improvements?
Where is the error?
What is the error?
Send
