Show:
Tell me a Story
Use it or Lose it
A Fool with a Tool
Spell it Out
Ceremonial Speeches
100
These are breakdowns of a User Story that detail the specific pieces of work that need to be completed to complete the Story.
What is a Task? (What are Tasks?)
100
This is an external entity that your system interacts with during the course of a use case to help it fulfill its objective.
What is a Secondary Actor?
100
This tool contains the Product and Sprint Backlog.
What is Rational Team Concert (RTC)?
100
The MVP is an Agile Concept that describes smallest set of functionality that makes sense to be released.
What is Minimum Viable Product?
100
This 15 minute meeting enables team members to answer 3 basic questions - What have I accomplished since yesterday, what am I planning to accomplish today, and what issues/roadblocks am I encountering.
What is the Daily Stand-up? (or Daily Scrum)
200
These are specific conditions that a User Story needs fulfill in order to be considered "Done".
What are Acceptance Criteria?
200
This type of section describes exceptions or variations in behavior within a Use Case.
What is an Alternate Flow?
200
In order to work-around tool integration issues, User Story Proxies need to be entered in this tool as a child to a Use Case in order to associate tests to User Stories.
What is RequisitePro (ReqPro)?
200
A CSM is a type of Scrum Accreditation.
What is Certified ScrumMaster?
200
Occurring at the end over every sprint, this allows the team to show their completed work to the Delivery Owner and other Stakeholders/Users.
What is Sprint Demonstration?
300
These 2 words begin the 3rd part of every User Story and serve as the lead-in to the benefit of the Story.
What is "So that"?
300
A concise "Verb-Noun" format should be used to specify this part of a Use Case so that a reader can immediately understand the purpose of the Use Case.
What is the Use Case Name? (title)
300
A set of Requirements is imported and related to Tests in this tool in order provide linkage between tests and Requirements.
What is RQM (Rational Quality Manager)?
300
In an Agile Context, DoD doesn’t' mean "Department of Defense", but rather a way of describing when something is considered finished.
What is Definition of Done?
300
This occurs at the end of each Sprint and allows the team to "self-correct" by discussing what went well, what didn't go well, and ideas for improvements.
What is Sprint Retrospective?
400
This Scrum Role is responsible for prioritizing User Stories on the Backlog.
What is Product Owner(Delivery Owner)?
400
Use Case authors should use this type of voice when phrasing Use Case Step Descriptions to help create unambiguous requirements
What is Active Voice?
400
These rectangular regions are building blocks of Dashboards in RTC that display useful content.
What are Widgets?
400
The "3 Cs" of a User Story emphasize that, in addition to the story itself, teams need to talk and have a definition of done?
What is Card, Conversation, and Confirmation.
400
Occurring at the beginning of each Sprint, this activity results a prioritized set of Stories from the Product Backlog being committed to for the upcoming Sprint.
What is Sprint Planning?
500
The valid values for Story Points Estimates roughly follow this mathematical sequence.
What is the Fibonacci Sequence?
500
This advanced Use Case Technique allows an author to extract common sections from 2 or more Use Cases and place them in a separate Use Case where they can be referenced in order to simplify and reduce duplicate text.
What are "Includes" Use Cases?
500
This RequistePro Attribute is used to "link" a User Story Proxy to a User Story in Rational Team Concert by containing the URL to the Work Item
What is the External Reference?
500
The acronym INVEST defines characteristics that a User Story needs to possess.
What is Independent, Negotiable, Valuable, Estimable, Sized appropriately or Small, and Testable?
500
Collaboratively getting a User Story ready for inclusion into a Sprint by clarifying details in Acceptance Criteria, Adding Tasks, and estimating via Planning Poker is the focus of this activity involving Scrum Team Members, the Delivery Owner, and key Members of the Delivery Backlog Team.
What is Backlog Grooming?