This term refers to a short, simple description of a user's interaction with a system
What is a user story
100
A user story should always have this many parts
What is 3
100
This event should happen every day. It should last no longer than 15 minutes and every team member should answer 3 questions.
What is the Daily Scrum or Daily Standup
100
This person is responsible for ensuring Scrum is understood and enacted.
Who is the Scrum Master
100
This is one of the original pilot teams which has successfully released a new app to live
What is the Bond Calculator team
200
These measure relative complexity of user stories
What are story points
200
A story which is less important to the Product Owner can generally be found where in the product backlog
What is toward the bottom
200
This is a time boxed event consisting of several other events
What is a sprint
200
This person is responsible for providing the vision of the product to the team.
Who is the Product Owner
200
This was one of the original pilot teams which has now been joined by 3 other project teams under Returns Analytics umbrella
What is SPAR 3
300
This term refers to all members of the team other than the Product Owner and Scrum Master
What is the Development Team
300
A well written story should include work in all layers of the application. This is known as what principle
What is vertical or cake slicing
300
This event is used to plan out the work the team will agree to complete during a sprint
What is Sprint Planning
300
These people are responsible for verifying the acceptance criteria of a story, creating test plans, and ad hoc testing functionality.
Who are QA
300
This project has 3 different teams working from a single product backlog and is based out of the Boston Office
What is Code Red
400
This describes a complete user interaction with the system.
What is an Epic
400
By acceptance criteria, by keywords, and by User are all common techniques to do what
What is story splitting
400
This event is an opportunity for the scrum team to inspect itself and create a plan for improvements to be enacted during the next sprint
What is the Retrospective
400
In FactSet's best practices, this person is responsible for documenting the "how" of a user story description
Who is the Lead Engineer
400
This team was one of the original pilot teams and maintains a code library utilized by many other teams. They have moved beyond Scrum and use the Kanban framework to manage their work
What is the Web Infrastructure team
500
This makes visible all of the work which the Development Team has identified as necessary to meet the Sprint Goal
What is the Sprint Backlog
500
These two concepts are key to knowing when to start and stop working on a story
What are Ready and Done criteria
500
This event is held a the end of each sprint and the dev team shows what work has been completed during the sprint.
What is the Sprint Review or Demo
500
The rest of the team outside the Scrum Master and Product Owner are known collectively as what
What is the Dev Team
500
This project was part of the original pilot and failed because the team had too many emergencies to deal with every day to follow disciplined scrum.