Before development, your team creates a spreadsheet with work items to populate the backlog. All work items that describe business requirements are prioritized as Must have. You also create work items to address:
A future enhancement request to group a set of existing steps into a multistep form
A drop-down list that is missing one of the required options --- This work item is in progress because the missing option prevents work from being done
How do you populate the backlog directly from the spreadsheet?
Show Answer
Hide Answer
Correct Answer:
C
When transitioning from planning to development, populating the backlog with work items that clearly articulate business requirements and enhancement requests is key. User stories are well-suited for capturing these needs in an Agile development environment.
C . Create stories: User stories are a fundamental element in Agile methodologies, used to describe features, functionalities, or enhancements from the perspective of the end user. They are concise yet comprehensive, detailing what needs to be done and why. For the scenarios mentioned --- grouping steps into a multistep form as a future enhancement, and addressing a missing option in a dropdown list --- creating user stories allows these requirements to be clearly defined and prioritized in the backlog.
Importing stories (A) might be a method to bulk add pre-defined stories from external sources but does not pertain to the action of creating new stories based on the spreadsheet contents. Creating bugs (B) is more appropriate for issues or errors that need to be fixed, not for new development work or enhancements. Creating feedback (D) could capture suggestions or comments but lacks the structured format of user stories for development purposes.
