Organize the Captured User Stories Flashcards
1
Q
- What is the primary goal of the “Initiation Phase” in an OutSystems project?
A) To design and develop the user interface.
B) To gather and document customer requirements.
C) To implement the application’s logic.
D) To test and deploy the application. - Which of the following is NOT typically involved in capturing requirements during the Initiation Phase?
A) Business Analyst
B) Product Owner
C) Developer
D) Subject Matter Expert - Why are user roles important in an OutSystems project?
A) They help to define the technical architecture of the system.
B) They ensure that the system is secure and compliant with regulations.
C) They provide a clear understanding of the different users and their needs.
D) They define the budget and timeline for the project. - How can you identify and define user roles effectively?
A) By asking users to complete a detailed questionnaire.
B) By analyzing the application’s code and logic.
C) By brainstorming with the team and validating with the customer.
D) By relying on the experience of the development team. - What is a good approach for grouping users into roles?
A) By their job title.
B) By their location.
C) By their department.
D) By their common needs and functionalities used in the system. - What is the primary purpose of personas in OutSystems projects?
A) To define the technical architecture of the system.
B) To create visual representations of the user interface.
C) To represent fictitious users based on real user data.
D) To manage the project backlog. - Which of the following is an example of a non-human or system role?
A) Sales Representative
B) Customer Service Agent
C) CRM System
D) Project Manager - Why is it important to cross-check user requirements with different stakeholders?
A) To ensure everyone is using the same terminology.
B) To gather diverse perspectives and avoid biases.
C) To identify any conflicts or inconsistencies in requirements.
D) All of the above. - Which of the following is NOT a technique for gathering user requirements?
A) User interviews
B) Observations
C) Code reviews
D) Workshops - What is the purpose of asking “How will we know when we have the user story done?”?
A) To define the acceptance criteria for the user story.
B) To determine the priority of the user story.
C) To estimate the time and effort required for the user story.
D) To identify the user role associated with the user story.
User Stories
- What is the primary purpose of writing user stories in an OutSystems project?
A) To document the technical specifications of the application.
B) To communicate customer needs and requirements in a clear and concise way.
C) To plan the project timeline and budget.
D) To manage the development team’s workflow. - What are the three elements of the 3-liner user story syntax?
A) User role, action, value.
B) Feature, action, result.
C) Role, task, benefit.
D) User, action, outcome. - What is the INVEST principle used for?
A) To define the stages of an OutSystems project.
B) To create user personas.
C) To ensure user stories are well-formed and effective.
D) To prioritize user stories in the project backlog. - What does the “Independent” rule of INVEST mean?
A) User stories should be easy to understand and implement.
B) User stories should not rely on other user stories to be completed.
C) User stories should be valuable to the user and the business.
D) User stories should be testable and have clear acceptance criteria. - What is the purpose of the “Negotiable” rule of INVEST?
A) To ensure that all stakeholders agree on the scope of the user story.
B) To allow for flexibility and adjustments to the user story during development.
C) To define the priority of the user story in the backlog.
D) To estimate the time and effort required for the user story. - What does the “Valuable” rule of INVEST mean?
A) User stories should be technically sound and well-designed.
B) User stories should provide a clear benefit to the user and the business.
C) User stories should be easy to implement and test.
D) User stories should be small and manageable. - What is the purpose of the “Estimable” rule of INVEST?
A) To ensure that user stories are well-defined and understood.
B) To estimate the time and effort required to complete the user story.
C) To define the acceptance criteria for the user story.
D) To prioritize the user story in the backlog. - What does the “Small” rule of INVEST mean?
A) User stories should be broken down into smaller, manageable tasks.
B) User stories should be detailed and comprehensive.
C) User stories should be focused on a single user role.
D) User stories should be easy to test and validate. - What does the “Testable” rule of INVEST mean?
A) User stories should have clear acceptance criteria that can be tested.
B) User stories should be implemented using automated testing tools.
C) User stories should be designed for easy integration with external systems.
D) User stories should be prioritized based on their testability. - What are the “three C’s” of user stories?
A) Card, Conversation, Confirmation.
B) Concept, Content, Confirmation.
C) Context, Content, Confirmation.
D) Card, Content, Confirmation.
Organizing User Stories
- What is the purpose of “Epics” in User Story Mapping?
A) To define the overall goals and objectives of the project.
B) To group together user stories that are too large or complex for a single iteration.
C) To prioritize user stories in the backlog.
D) To manage the technical dependencies between user stories. - What is the purpose of “Themes” in User Story Mapping?
A) To group user stories based on their common subject matter.
B) To define the user roles involved in the project.
C) To manage the project timeline and budget.
D) To define the technical architecture of the system. - What is the benefit of organizing user stories into a hierarchy of Themes, Epics, and User Stories?
A) It helps to ensure that the project is delivered on time and within budget.
B) It improves the understanding of the overall project scope and goals.
C) It facilitates the creation of a detailed project backlog.
D) All of the above. - What is the benefit of organizing user stories by their relationship in time?
A) It helps to identify and manage dependencies between user stories.
B) It provides a clear understanding of the workflow and sequence of events.
C) It helps to prioritize user stories based on their importance.
D) All of the above. - What are some methods for representing the time-based relationships between user stories?
A) User Story Maps
B) Activity Diagrams
C) Process Flows
D) All of the above. - How can the organization of user stories help with the creation of a project backlog?
A) It ensures that the backlog is prioritized based on user needs.
B) It provides a clear overview of the scope and requirements of the project.
C) It makes it easier to manage the project and track progress.
D) All of the above.
User Stories - Additional Questions
- Which of the following is a good practice for writing a user story’s 3-liner?
A) Use technical jargon to ensure clarity.
B) Focus on the user’s needs and value.
C) Include detailed technical specifications.
D) Describe how the functionality will be implemented. - What is the purpose of providing business context and value in a user story?
A) To explain the technical details of the implementation.
B) To clarify the reason why the user story is important.
C) To define the acceptance criteria for the user story.
D) To estimate the time and effort required for the user story. - Why is it important to map a user story to a business process?
A) To ensure that the user story aligns with the overall workflow.
B) To identify any potential conflicts or inconsistencies with existing processes.
C) To understand the impact of the user story on the business.
D) All of the above. - What is the purpose of using Gherkin language for acceptance criteria?
A) To define the user interface design for the user story.
B) To create test cases for the user story.
C) To document the technical implementation details.
D) To estimate the time and effort required for the user story. - What are non-functional requirements, also known as quality requirements?
A) They define the specific functions of the system.
B) They define the user roles and permissions.
C) They define the technical architecture of the system.
D) They define the quality attributes of the system, such as performance, security, and usability. - Which of the following is NOT a common non-functional requirement?
A) Performance
B) Security
C) Usability
D) Budget - Why is it important to include mockups or screenshots in user stories?
A) To provide a visual representation of the user experience.
B) To define the technical details of the user interface design.
C) To estimate the time and effort required for the user story.
D) To identify the user role associated with the user story. - What is the purpose of using real sample data in user stories?
A) To make the user story more realistic and relevant.
B) To define the database schema for the application.
C) To estimate the size and complexity of the application.
D) To identify any potential security vulnerabilities. - What is the purpose of identifying the impact of a user story on the prior and next steps in a business process?
A) To ensure that the user story fits seamlessly into the overall workflow.
B) To define the acceptance criteria for the user story.
C) To estimate the time and effort required for the user story.
D) To prioritize the user story in the backlog. - What are the benefits of using a template for writing user stories?
A) It ensures that all user stories are consistent in format and content.
B) It provides a clear framework for capturing all the essential elements of a user story.
C) It helps to streamline the user story writing process.
D) All of the above. - What is the difference between functional and non-functional requirements?
A) Functional requirements define what the system does, while non-functional requirements define how well it does it.
B) Functional requirements are captured during the Initiation Phase, while non-functional requirements are captured during the Iteration Development Phase.
C) Functional requirements are prioritized higher than non-functional requirements.
D) Functional requirements are easier to test than non-functional requirements. - How can the INVEST principle be applied to non-functional requirements?
A) Non-functional requirements should be defined as separate user stories.
B) Non-functional requirements should be considered as constraints when implementing functional requirements.
C) Non-functional requirements should be prioritized based on their impact on the user experience.
D) Non-functional requirements should be documented in a separate document. - Why is it important to refine user stories throughout the project?
A) To ensure that the user stories are always up-to-date with the latest requirements.
B) To improve the clarity and understanding of the user stories.
C) To identify and address any inconsistencies or errors.
D) All of the above. - How can you ensure that user stories are truly valuable to the user and the business?
A) By focusing on the user’s needs and the value they receive.
B) By conducting user testing and gathering feedback.
C) By regularly reviewing and refining the user stories.
D) All of the above.
A
User Requirements & Roles
- What is the primary goal of the “Initiation Phase” in an OutSystems project?
B) To gather and document customer requirements. - Which of the following is NOT typically involved in capturing requirements during the Initiation Phase?
C) Developer - Why are user roles important in an OutSystems project?
C) They provide a clear understanding of the different users and their needs. - How can you identify and define user roles effectively?
C) By brainstorming with the team and validating with the customer. - What is a good approach for grouping users into roles?
D) By their common needs and functionalities used in the system. - What is the primary purpose of personas in OutSystems projects?
C) To represent fictitious users based on real user data. - Which of the following is an example of a non-human or system role?
C) CRM System - Why is it important to cross-check user requirements with different stakeholders?
D) All of the above. - Which of the following is NOT a technique for gathering user requirements?
C) Code reviews - What is the purpose of asking “How will we know when we have the user story done?”?
A) To define the acceptance criteria for the user story.
User Stories
- What is the primary purpose of writing user stories in an OutSystems project?
B) To communicate customer needs and requirements in a clear and concise way. - What are the three elements of the 3-liner user story syntax?
D) User, action, outcome. - What is the INVEST principle used for?
C) To ensure user stories are well-formed and effective. - What does the “Independent” rule of INVEST mean?
B) User stories should not rely on other user stories to be completed. - What is the purpose of the “Negotiable” rule of INVEST?
B) To allow for flexibility and adjustments to the user story during development. - What does the “Valuable” rule of INVEST mean?
B) User stories should provide a clear benefit to the user and the business. - What is the purpose of the “Estimable” rule of INVEST?
B) To estimate the time and effort required to complete the user story. - What does the “Small” rule of INVEST mean?
A) User stories should be broken down into smaller, manageable tasks. - What does the “Testable” rule of INVEST mean?
A) User stories should have clear acceptance criteria that can be tested. - What are the “three C’s” of user stories?
A) Card, Conversation, Confirmation.
Organizing User Stories
- What is the purpose of “Epics” in User Story Mapping?
B) To group together user stories that are too large or complex for a single iteration. - What is the purpose of “Themes” in User Story Mapping?
A) To group user stories based on their common subject matter. - What is the benefit of organizing user stories into a hierarchy of Themes, Epics, and User Stories?
D) All of the above. - What is the benefit of organizing user stories by their relationship in time?
D) All of the above. - What are some methods for representing the time-based relationships between user stories?
D) All of the above. - How can the organization of user stories help with the creation of a project backlog?
D) All of the above.
User Stories - Additional Questions
- Which of the following is a good practice for writing a user story’s 3-liner?
B) Focus on the user’s needs and value. - What is the purpose of providing business context and value in a user story?
B) To clarify the reason why the user story is important. - Why is it important to map a user story to a business process?
D) All of the above. - What is the purpose of using Gherkin language for acceptance criteria?
B) To create test cases for the user story. - What are non-functional requirements, also known as quality requirements?
D) They define the quality attributes of the system, such as performance, security, and usability. - Which of the following is NOT a common non-functional requirement?
D) Budget - Why is it important to include mockups or screenshots in user stories?
A) To provide a visual representation of the user experience. - What is the purpose of using real sample data in user stories?
A) To make the user story more realistic and relevant. - What is the purpose of identifying the impact of a user story on the prior and next steps in a business process?
A) To ensure that the user story fits seamlessly into the overall workflow. - What are the benefits of using a template for writing user stories?
D) All of the above. - What is the difference between functional and non-functional requirements?
A) Functional requirements define what the system does, while non-functional requirements define how well it does it. - How can the INVEST principle be applied to non-functional requirements?
B) Non-functional requirements should be considered as constraints when implementing functional requirements. - Why is it important to refine user stories throughout the project?
D) All of the above. - How can you ensure that user stories are truly valuable to the user and the business?
D) All of the above.
