Methodology Tools (3% Weighting) Flashcards
Explain the advantages of using agile tools to support an agile development process
What are the 5 core scrum values?
- Focus
- Courage
- Openness
- Commitment
- Respect
One of the key attributes of Scrum at Salesforce is:
A. It’s a framework to organize delivery to customers.
B. Teams work in long iterations or sprints.
C. Everyone is organized into large, specialist teams.
D. It’s a framework used in sports teams, especially soccer
A. It’s a framework to organize delivery to customers.
What are the main scrum team role (Team, Scrum Master, Product Owner) traits?
The Team does the work,
The Scrum Master helps facilitate the process
The product owner defines the direction for the team
Which of the following is true of the Scrum elements of delivery?
A. A product backlog is a list of everything that we think needs to be done
B. Potentially shippable increments are always released each sprint
C. The sprint backlog is a list of all work that can potentially be done on the project
D. We focus on output, not outcome
A. A product backlog is a list of everything that we think needs to be done
Why is finishing work in a sprint is important?
We value eliminating waste, and unfinished work is a form of waste that does not help us deliver value to our customers
What is the difference between a product backlog and a sprint backlog?
Product backlog is everything that can possibly be needed,
Sprint backlog is the work committed by the team for the next 2 weeks
What are the two main types of Scrum meetings we have at Salesforce?
A) Planning and inspection, and status updates
B) Sprint and planning meetings
C) Inspect and adapt, and planning meetings
D) Release planning and sprint demos
C) Inspect and adapt, and planning meetings
Which meetings are important for planning?
A) Demo/review, retros, status meetings
B) Release planning, sprint planning, backlog refinement, daily standup
C) Long term planning, reviews, demos
D) Status meetings, backlog refinement, demo/review
B) Release planning, sprint planning, backlog refinement, daily standup
The primary difference between a demo/review and retrospective is:
A) Demo/reviews are only done by teams that build products, and retros are done by all teams
B) Retrospectives happen at release boundaries, while demos/reviews happen at least monthly
C) There’s not a difference
D) The first inspects and adapts the product or service, and the second inspects how the team works
D) The first inspects and adapts the product or service, and the second inspects how the team works
Kanban teams deliver fast by
A) Setting expectations with customers, using a Kanban board, talking to each other, having a workflow
B) Visualizing flow, limiting work in progress with visual indicators, managing flow, and adapting with evolutionary changes
C) Managing process flow, a single point of contact with customers, effective monitoring capabilities and tools
D) Customer focus, keeping work small, daily meetings, and tracking lead time
B) Visualizing flow, limiting work in progress with visual indicators, managing flow, and adapting with evolutionary changes
Kanban teams respond to unplanned work and changes by:
A) Putting the new request at the bottom of the backlog
B) Dropping everything to jump on the new request
C) Assessing the priority of the new request and starting the work when it’s at the top of the backlog
D) Giving the customer/stakeholder daily updates
C) Assessing the priority of the new request and starting the work when it’s at the top of the backlog
Kanban teams use which practices to manage flow:
A) Storypoints, timebox, work in progress, velocity
B) Retrospectives, planning, support policies, velocity
C) Iterations, epics, subject matter experts, refinement
D) Cycle time, lead time, small batch size, and throughput
D) Cycle time, lead time, small batch size, and throughput
Which process would be better to use (Scrum, Kanban or both) when it is the product owner that prioritizes the product backlog?
Both!
Which process would be better to use (Scrum, Kanban or both) when the product backlog is reordered for the next sprint?
Scrum
Which process would be better to use (Scrum, Kanban or both) when the product backlog is continuously reordered for the next available person with capacity?
Kanban