NEW
Font size
WorksheetsAgile Methodologies Quiz
Total questions: 64
Worksheet time: 32mins
Which of the following best describes story points?
A measure of effort required to implement a user story
A type of user story
A stage in the ADAPT framework
A responsibility of the product owner
Can a project have two releases?
Yes
No
Only if approved
Only in Agile
How a scrum master selects which task to prioritize over many tasks?
By team vote
Based on urgency
Random selection
By client request
How Agile promotes flexibility, which is considered when transitioning to Agile methodologies?
By strict rules
Through adaptability
By fixed plans
Through rigid structures
How an Agile team should be organized?
Hierarchically
By roles
Self-organized
By seniority
How can a team determine if the sprint is successful or not?
By team satisfaction
By client feedback
By meeting sprint goals
By project completion
How can you determine how many sprints are needed for the remaining of a project?
By estimating the total story points and dividing by team velocity
By guessing based on team availability
By using the number of team members
By calculating the budget
How is velocity estimated?
By the number of team members
By the average story points completed in past sprints
By the total project budget
By the number of hours worked
How many teams a scrum master could have?
One
Two to three
As many as possible
None
How you characterized the participatory design process?
Involves only designers
Involves stakeholders and users in the design process
Is a solo activity
Is only for software projects
If a complex story is written and PO wants to showcase at a trade show by sprint one, what is the best approach?
Complete the entire story in one sprint
Break down the story into smaller, deliverable parts
Ignore the trade show deadline
Work overtime to finish the story
If a product is extremely complex and has multiple integration points, what is the best recommendation for the team?
Simplify the product by removing features
Focus on one integration point at a time
Work on all integration points simultaneously
Delay the project indefinitely
If a product owner needs to determine the priority of an addition to the product, how should they decide?
Based on personal preference
By considering the potential value to the customer
By the complexity of implementation
By the number of team members available
If a story is written up for better error logging, what is the best way to articulate the value?
By explaining the technical details
By highlighting the potential for reduced debugging time
By focusing on the cost of implementation
By discussing the number of errors logged
If a meeting takes more than 15 minutes because of task assignments, how should the scrum master solve the problem?
Extend the meeting time
Cancel the meeting
Address task assignments outside the meeting
Ignore the time limit
If there are disagreements within the team and the product owner, what would be the best approach for the scrum master?
Take sides with the product owner
Facilitate a discussion to reach a consensus
Ignore the disagreement
Make a decision independently
If there is a dispute between a developer and a tester, how can it be resolved?
By escalating to higher management
By facilitating a discussion to understand both perspectives
By assigning blame to one party
By ignoring the issue
If there is no consensus over a story estimate using planning poker, what should the scrum master do?
Force a decision
Facilitate further discussion to reach agreement
Choose the highest estimate
Choose the lowest estimate
If you have multiple scrum teams, how many product owners do you need?
One for each team
One for all teams
Two for each team
None
If you have multiple stories, how should you pick which one to work on first?
Choose the one with the highest priority
Select the one that is easiest to complete
Pick the one with the most team members interested
Start with the one that has the least impact
In MoSCoW, what is the point of classifying a requirement as Won't?
To indicate it will be done in the next sprint
To show it is not a priority for the current release
To mark it as completed
To highlight it as a critical requirement
Product quality is ensured by what?
Regular team meetings
Continuous testing and feedback
Hiring more developers
Increasing the budget
What could be discussed on a Sprint Review?
Team member salaries
Completed work and feedback
Future project budgets
Personal development plans
What is a key factor when moving to Agile?
Maintaining strict hierarchies
Flexibility and adaptability
Increasing documentation
Reducing team size
What is the best action to have new team members create enough technical documentation?
Assign them to a documentation team
Provide them with templates and guidelines
Let them learn by trial and error
Exclude them from documentation tasks
What is the best way to deal with a member that believes scrum is a fad?
Ignore their opinion
Provide training and education on Scrum benefits
Remove them from the team
Agree with their perspective
What is velocity used for?
Measuring team speed
Estimating project cost
Calculating team size
Determining project scope
What represents a principle of Agile manifesto and a Lean method of simplicity?
Maximizing work done
Reducing waste
Increasing complexity
Expanding team size
What should be the output of the first sprint?
A complete product
A prototype
A project plan
A user manual
What should the agile project manager do when interacting with team members?
Dictate tasks
Encourage collaboration
Avoid communication
Focus on individual work
What should the product owner do if he wants to prioritize a product idea?
Ignore feedback
Conduct market research
Increase budget
Delay decision-making
What should the Scrum Master do if sprint backlog items cannot be delivered?
Extend the sprint indefinitely
Cancel the project
Facilitate a retrospective
Ignore the issue
What does team estimation consist of?
Individual opinions
Random guesses
Collective team input
Managerial decisions
When a team member wants to bring up an idea, when should the idea be included in the product backlog?
During the daily stand-up meeting
At the end of the sprint
During backlog refinement sessions
After the product is released
When is it best to use the Agile Scrum approach?
When the project requirements are fixed
When the project is exploratory and requirements may change
When the team is small and co-located
When the project has a long timeline
When is the definition of done used first?
During the sprint planning meeting
During the sprint review
During the daily stand-up
During the sprint retrospective
When is it good to create and adjust documentation?
At the start of the project
Continuously throughout the project
Only at the end of the project
Only when requested by stakeholders
When is the ideal time to hold a retrospective?
At the beginning of the sprint
In the middle of the sprint
At the end of the sprint
After every two sprints
When transitioning to Scrum, what should the Scrum Master keep doing?
Assigning tasks to team members
Facilitating team meetings and removing impediments
Writing code for the team
Managing the project budget
Which methodologies follow iterative development?
Waterfall
Agile
V-Model
Spiral
Which of the statements of the Agile Manifesto provides guidance about how to resolve conflict?
Retrospective
Story Points
Scrum Master
Design Process Participants
Which step will help reduce the bottleneck using Kanban?
After iteration planning
Project Releases
Scrum
Retrospective
Why could be the reason for a burn down chart dropping rapidly?
Ideal to have no more than four teams
End users are involved from beginning to end
Is most desirable when the product requirements may change in the process
Can have to releases because all increments should be potentially releasable
Why is Awareness important as a first step when introducing Agile?
Definition of Done
Is done first during the estimation of the features in the Product Backlog
Is most desirable when the product requirements may change in the process
Unit of measurement for a user story
What is the primary reason the first 'A' of ADAPT is important?
It helps in building early momentum and encourages others to follow.
It ensures the completion of all tasks on time.
It provides a detailed project plan.
It guarantees a successful project outcome.
What does Agile promote by following an iterative and incremental development life cycle?
Flexibility
Rigidity
Predictability
Stability
Who is responsible for determining the business value of each feature in a project?
Product Owner
Scrum Master
Project Manager
Developer
Why is documentation important when estimating tasks for a future Sprint Backlog?
It allows for adjustments per feature.
It ensures all tasks are completed on time.
It provides a detailed project timeline.
It guarantees project success.
If a sprint cannot be completely delivered, what should you do?
Ask the product owner to revise the order of the Sprint Backlog.
Cancel the sprint and start over.
Ignore the incomplete tasks.
Extend the sprint duration.
What should a Scrum Master do if overwhelmed with a large number of tasks?
Contact a technical expert to help a team member with a particular issue.
Ignore the tasks and focus on new ones.
Delegate all tasks to the team.
Cancel the sprint.
How many sprints would you forecast for 150 points remaining, with an average velocity of 60 for the past 2 sprints and the best sprint having a velocity of 75?
2 sprints
3 sprints
4 sprints
5 sprints
What is the best way to resolve the issue when work of the teams has expanded and cannot be completed by a single team, requiring 4 scrum teams and the PO is burned out?
Add a few POs but have one of them play the role of a lead PO and maintain only one product backlog
Hire more developers
Split the teams into smaller groups
Increase the sprint duration
Which stage of the ADAPT framework is present when an organization is transitioning to Scrum and some pilot teams have been using it for some time with good results?
Awareness
Desire
Ability
Transfer
What would be the most important advantage if an organization decides that all projects will move to scrum at once?
Kanban
May not follow iterative development
An all-in transition will get over quickly
Increased documentation
What is the best way to deal with an opponent of the scrum transition in the team?
Ignore their concerns
Reinforce and reiterate the organization's commitment to scrum
Remove them from the team
Delay the transition
What is used to determine if the team is committing to an appropriate amount of work for the iteration?
Principle of Agile Manifesto
Velocity
Estimation Game
Kanban
How does Agile ensure product quality?
By maximizing the amount of work not done
With more frequent inspection after each iteration
By increasing the sprint duration
By reducing team size
What are the key elements of a user story?
Detailed technical specifications
Conversations about the story, a written description, and success criteria about the story
A list of tasks
A project timeline
What is the key factor for project managers' success moving to Agile?
Shifting from a controlling mindset to a facilitating mindset
Increasing the number of meetings
Reducing team size
Extending project deadlines
What should the team check against if there are outstanding bugs reported during testing that are not showstoppers?
The project timeline
The definition of done agreed upon at the beginning of the Sprint
The budget constraints
The team size
What is the best forum to showcase change to a product feature?
Sprint Review
Daily Standup
Backlog Refinement
Retrospective
How can a dispute between a tester and developer about a story be resolved?
Discuss with the Product Owner and ask if it is a valid scenario
Ignore the dispute and continue work
Let the developer decide
Let the tester decide
If a team is struggling to estimate a complex story due to unfamiliarity with the technology, what should they do?
Write a SPIKE story and time box it
Skip the story and move on
Assign it to the most experienced member
Estimate it randomly
What should a Scrum Master do when interacting with team members?
Phrase statements as a request rather than as a demand
Give direct orders
Avoid communication
Use technical jargon
