Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

iSQI Exam CTFL_Syll2018 Topic 5 Question 90 Discussion

Actual exam question for iSQI's CTFL_Syll2018 exam
Question #: 90
Topic #: 5
[All CTFL_Syll2018 Questions]

The following checklist has been produced to help reviewers detect defects with user stones:

User Story Checklist:

1. The user story must have a unique identifier

2 The user story must contain the user/customer

3 The user story must contain the need

4. The user story must contain the reason.

5. The user story must contain testable acceptance Criteria-Using the checklist above what is wrong with the following user story?

User Story US2018

As a bank account customer, I would like to transfer money from one account to another using the mobile banking application by using the drag

and drop feature.

This is acceptable when

* I can drag and drop from one account to another and select any of the pre-defined amounts

* I can drag and drop from one account to another and type in any positive amount

* Once I confirm the details the amount is debited from the first account and credited to the second account

Show Suggested Answer Hide Answer
Suggested Answer: C

According to the user story checklist, the user story must contain the reason for the need, which is usually expressed by using the word ''so that'' or ''because''. For example, the user story could be rewritten as:

User Story US2018 As a bank account customer, I would like to transfer money from one account to another using the mobile banking application by using the drag and drop feature,so that I can easily manage my finances.

This way, the user story provides a clear value proposition and a justification for the need. The reason also helps to define the scope and priority of the user story, as well as to verify the acceptance criteria.


Contribute your Thoughts:

Mel
4 months ago
This user story is more slippery than a greased pig. I bet the dev team is going to have a field day trying to implement this one.
upvoted 0 times
Yaeko
3 months ago
D
upvoted 0 times
...
Erasmo
3 months ago
B
upvoted 0 times
...
Ernestine
4 months ago
A
upvoted 0 times
...
...
Hubert
5 months ago
Unique identifier? What is this, a dating app? Oh wait, it's a user story. My bad, guess I'm not cut out for this agile stuff.
upvoted 0 times
Ashton
4 months ago
The user story is missing the unique identifier.
upvoted 0 times
...
Rickie
5 months ago
It's not a dating app, it's about user stories.
upvoted 0 times
...
...
Bo
5 months ago
I think the user story lacks a unique identifier, that's a crucial aspect to include.
upvoted 0 times
...
Pa
5 months ago
I believe the acceptance criteria is not testable, that's the main problem here.
upvoted 0 times
...
Charlene
5 months ago
Agreed, the user story is missing the customer and the reason. Without those key elements, it's not a complete user story.
upvoted 0 times
Lashawnda
4 months ago
C) The user story does not contain the reason
upvoted 0 times
...
Jeannine
5 months ago
B) The user story does not contain the customer.
upvoted 0 times
...
...
Natalie
6 months ago
I agree with Katie, the user story should include the customer for clarity.
upvoted 0 times
...
Deeanna
6 months ago
The acceptance criteria is definitely not testable. How can you test 'drag and drop'? That's just a feature, not a concrete step.
upvoted 0 times
Lavera
5 months ago
B) The user story does not contain the customer.
upvoted 0 times
...
Daniela
5 months ago
A) The acceptance criteria is not testable
upvoted 0 times
...
...
Katie
6 months ago
I think the issue is that the user story does not contain the customer.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77