click below
click below
Normal Size Small Size show me how
SE Agile
Question | Answer |
---|---|
Agile values | - Individuals and interactions - Working software - Customer collaboration - Responding to change |
Scrum | An Agile process that allows us to focus on delivering the highest business value in the shortest time |
Teams ___ to determine the best way to deliver the highest priority features | Self-organize |
Product backlog | A list of all desired work on the project |
Sprint backlog | Requirements that you agreed to work on for this sprint |
Product Owner | Responsible for the project and driving product success |
Scrum Master | Responsible for ensuring Scrum is understood and enacted while supporting the team |
Teams are...? | Self-organizing and cross-functional |
Sprint Goal | A short statement of what the work will be focused on during the sprint |
Work is ___ assigned | Never |
Burndown chart | Shows how much work is left to do |
A product backlog is...? | Never complete and evolves along with the product and the environment in which it will be used |
Grooming | An ongoing process in which the product owner and the team collaborate on the details of the product backlog items, coming to a shared understanding of what is to be accomplished |
The product backlog is constantly ___ | Reprioritized |
Projects progress in a series of ____ | Sprints |
Sprints last around...? | 2-4 weeks |
During a sprint, the product is...? | Designed, coded, and tested |
No changes are made during a sprint that would...? | Endanger the sprint goal |
Tasks in agile projects should take...? | A day or less |
Sprint prioritization | - Analyze and evaluate product backlog - Select sprint goal |
Sprint planning | - Team selects items from the product backlog they can commit to completing - Sprint backlog is created |
Daily Scrum Meeting | - They are commitments in front of peers - Meeting must last 15 minutes or less - They are for coordination, not problem-solving |
Sprint Review | - Team presents what they accomplished during the sprint to the Product Owner - Demo format, informal - Intended to elicit feedback and foster collaboration |
Sprint Retrospective | - Periodically take a look at what is and is not working - Typically 15-30 minutes - Done at the end of each sprint |
Team Rules | Guidelines the team members agree to conduct themselves under in the Sprint as defined by the Scrum team |
User Stories | User requirements written in the customer’s language |
INVEST | Independent Negotiable Valuable Estimable Small Testable |
Acceptance Criteria | The parameters of a user story that determine when it is completed and working as expected |
We use ___ to indicate how long a task is going to take | Fibonacci numbers |
Refinement | Activities around creating and refining, estimating, and prioritizing product backlog items |
Definition of “Ready” | Helps team understand what criteria is needed for a work item to be ready to be worked on |