Agile Roles
In a Scrum team, who crafts the Sprint Goal for each sprint?
Scrum Master
Scrum Team
Product Owner
Development Team
None of the above
Scrum Team
Who is responsible for knowing and applying Agile Principles and Practices at all times?
Scrum Master
Product Owner
Architect
Every Member of the Team (Including Me)
Every Member of the Team (Including Me)
Which of the following is the last event of Sprint?
Sprint Retrospective
Sprint Planning
Sprint Review
Sprint Demo
Sprint Retrospective
Which of the following is an Agile Manifesto value?
Individuals and interactions over following a plan
Working software over processes and tools
Responding to change over comprehensive documentation
Customer collaborations over contract negotiation
Customer collaborations over contract negotiation
Quick Filters can be used to further filter the issues in the board based on the additional JQL query.
True
False
True
Which of the following is a characteristic of a good Scrum Team?
Its members all have similar skills.
It waits for tasks to be assigned to it.
It seeks direction from the Scrum Master.
It is self-managing.
It is self-managing.
There is no difference between incremental and iterative development?
True
False
False
The Three Question format for Daily Scrum is compulsory
True
False
False
When was the agile manifesto written?
1991
2001
2010
2015
2001
Which view in Jira gives breakdown of the # of story points for each associate for a sprint?
Backlog
Who can make changes to Product Backlog?
Only the Development Team.
Only the Scrum Master.
Anyone can influence the Product Owner to make changes, but Product Owner has final decision.
Anyone can make the changes, but Product Owner has to get a notification about what was changed.
Anyone can influence the Product Owner to make changes, but Product Owner has final decision.
What should be an ideal way to approach architecture as recommended by the principles of Agile Manifesto? (choose the best option)(M)
Architecture emerges in Agile during execution.
Architecture is not important, but functionality is important for stakeholders/business owners.
Architecture is defined and planned up front during the planning phases in Agile.
Architecture is defined and implemented in the first iterations/sprints.
Architecture emerges in Agile during execution.
Product Backlog should be ordered based on? (M)
Priority of the items being delivered.
Value of the items being delivered.
Size of the items being delivered.
Risk associated with completion/non-completion of the items.
Value of the items being delivered.
What is MOST important according to Agile Manifesto?
Documentation & Planning
People and How they communicate
Control and Management
Processes and Tools
People and How they communicate
Name 3 reports that you can pull from JIRA
What are:
Sprint Reports, Burndown Chart, Velocity
The Scrum Master
Controls the priority order of items in the Product backlog.
Is the keeper of the product vision.
Creates, refines and communicates customer requirements to the Dev Team.
Is the Scrum Team's Scrum expert and focuses on continual improvement.
Is the Scrum Team's Scrum expert and focuses on continual improvement.
Which of the following is NOT a principle of the manifesto for agile software development?
Commitment to the plan despite changing circumstances.
Projects are built around motivated individuals, who should be trusted.
Working software is delivered frequently (weeks rather than months).
Face-to-face conversation is the best form of communication (co-location).
Commitment to the plan despite changing circumstances.
The primary output of a Sprint Planning session is:
Product backlog
Product Increment
Sprint backlog
Sprint goal
Sprint backlog
Which of the following BEST describes the Agile Manifesto attitude towards customer collaboration?
Regular and frequent feedback from the customer is essential.
Consensus from customers is required before new functional requirements can be inserted into a Sprint.
The Team must communicate what functionality will be produced in a Sprint and the goal of the Team for the release.
Collaborate closely with the customer and ensure all functionality is defined prior to the build phase of a project.
Regular and frequent feedback from the customer is essential.
Order the below in correct hierarchy as in our current Jira
Epic
Story
Sub Task
Initiative
Theme
What are: Epic, Story, Sub Task
What is the approach that Scrum encourages when Developers determines it will be difficult to deliver any value by the end of a Sprint?
Extend the Sprint by a few days to accommodate the extra work.
Immediately escalate to Senior Management.
Together with the Product Owner, focus on what can be done and identify a way to deliver something valuable at the end of each Sprint.
Suggest the Product Owner abnormally terminate the Sprint
Together with the Product Owner, focus on what can be done and identify a way to deliver something valuable at the end of each Sprint.
Which of these Agile terms is paired with its correct definition?
User personas: a summary of a feature from the user's perspective.
Use cases: a characterization of your intended end user.
User stories: documentation of user paths through an app.
Acceptance criteria: what needs to be done for a user story to be achieved.
Acceptance criteria: what needs to be done for a user story to be achieved.
Which are the 3 question do we focus on during Sprint Planning
WHAT, HOW, HOW MUCH
WHO, WHY, WHAT
WHY, WHAT, HOW
WHO, WHAT, WHY
WHY, WHAT, HOW
Agile Manifesto says to value responding to change over following a plan. Which of the following statements illustrates this?
Changes are accepted up until the point that the first Sprint begins. Then, changes are deferred to a future release.
Changes are accepted only if other features are removed from the backlog such that a fixed end-date is maintained.
Changes are accepted up until about halfway through the project, then all changes are deferred to a future release.
Changes are accepted at any time during the development effort depending on the business value of the change, the PO's acceptance, and the ability of the Scrum Team to respond in a timeframe acceptable to the PO.
Changes are accepted at any time during the development effort depending on the business value of the change, the PO's acceptance, and the ability of the Scrum Team to respond in a timeframe acceptable to the PO.
Graphical representation of work left to do versus time
Burn up chart
Burn down chart
Velocity chart
Sprint Report
Burn down chart