Free Agile Business Analysis User Stories and Modeling Questions and Answers — Questions and Answers
Question 1: An Agile team is using the 3 Cs model to develop user stories. During a backlog refinement session, the team discusses a story card, clarifies details, asks questions about functionality, and collectively agrees on the scope. Which of the 3 Cs is PRIMARILY being demonstrated in this scenario?
- Card
- Confirmation
- Conversation (Correct answer)
- Context
Correct answer: Conversation
The 'Conversation' is the collaborative dialogue among the team and stakeholders to flesh out the details of a user story. This scenario, involving discussion, clarification, and questioning to build a shared understanding, is a direct example of the Conversation component of the 3 Cs model.
Question 2: A business analyst is reviewing the following user story: 'As a user, I want to manage my profile so that I can keep my information up to date.' The team finds it difficult to estimate and plan for this story within a single sprint. Which INVEST characteristic does this user story MOST CLEARLY violate?
- Negotiable
- Valuable
- Testable
- Small (Correct answer)
Correct answer: Small
The user story 'manage my profile' is too large and encompasses multiple actions (e.g., create, view, edit, delete profile information). This violates the 'Small' characteristic of the INVEST criteria, which states stories should be granular enough to be completed within one iteration.
Question 3: What is the primary purpose of creating a User Story Map in an Agile project?
- To provide a detailed, technical specification for the development team.
- To create a visual representation of the user's journey, showing the relationship between stories and the overall product experience. (Correct answer)
- To serve as a contractual agreement between the project team and stakeholders.
- To replace the need for a product backlog by listing all requirements chronologically.
Correct answer: To create a visual representation of the user's journey, showing the relationship between stories and the overall product experience.
A User Story Map arranges user stories into a model that tells the story of the user's journey. It helps teams visualize the workflow, understand the big picture, identify gaps, and prioritize work to deliver a cohesive user experience, rather than just a list of features.
Question 4: A product owner has a large feature idea: 'As a customer, I want to pay for my order.' An agile business analyst suggests breaking this down into smaller stories, such as 'Pay with a saved credit card,' 'Pay with a new credit card,' and 'Pay with a gift card.' This is an example of which user story splitting technique?
- Splitting by workflow steps
- Splitting by operational boundaries (CRUD)
- Splitting by data variations or business rules (Correct answer)
- Splitting by user roles
Correct answer: Splitting by data variations or business rules
This technique involves splitting a story based on different data inputs or business rule variations. Here, the core action ('pay for order') is split by the different payment methods (data variations) that the system must support.
Question 5: Which of the following BEST describes the role of Agile Modeling?
- To create comprehensive, detailed documentation before any development begins.
- To produce a rigid set of formal diagrams that must be strictly followed.
- To use lightweight, collaborative methods to create 'just enough' documentation to facilitate communication and guide development. (Correct answer)
- To eliminate all forms of documentation in favor of verbal communication only.
Correct answer: To use lightweight, collaborative methods to create 'just enough' documentation to facilitate communication and guide development.
Agile Modeling is a practice that uses simple, flexible models to explore the problem and solution space. Its primary goal is to enhance communication and shared understanding, creating models that are 'just good enough' rather than exhaustive, formal documents.
Question 6: While a user story describes a user's goal ('what' and 'why'), a traditional use case is more likely to:
- Be written on an index card as a placeholder for a conversation.
- Focus exclusively on non-functional requirements like performance and security.
- Describe the step-by-step interaction between a user (actor) and the system, including alternative paths. (Correct answer)
- Be estimated using story points by the development team.
Correct answer: Describe the step-by-step interaction between a user (actor) and the system, including alternative paths.
A key difference is the level of detail. User stories are intentionally brief to encourage conversation. Use cases are more detailed and structured, specifying the flow of events, including the primary success scenario and various alternative or exception paths an actor might take to achieve a goal.
Free Agile Business Analysis User Stories and Modeling Questions and Answers
An Agile team is using the 3 Cs model to develop user stories.
During a backlog refinement session, the team discusses a story card, clarifies details, asks questions about functionality, and collectively agrees on the scope.
Which of the 3 Cs is PRIMARILY being demonstrated in this scenario?