NEW
Font size
WorksheetsBusiness Agility Quiz
Total questions: 15
Worksheet time: 7mins
The maximum length of the Sprint review (its time box) is :
2 hours
4 hours for a monthly Sprint.For shorter Sprints it is usually shorter
As long as needed
1 day
Which is the first thing does the development team do during the first Sprint
Deliver an increment of potentially releasable software
Determine the complete architecture and infrastructure for the product
Create the complete product backlog to be developed in subsequent Sprints
Develop a plan for the rest of the release
When is a Sprint over?
When all product backlog items meet their definition of done
When the product owner says it is done
When all the tasks are completed
When the time-box expires
What is the major challenge when multiple feature teams work on the same product backlog
Making sure there’s enough work for everyone in the team
Minimizing dependencies between teams
Meeting original scope projections
None of the Above
What does technical debt mean in software development
It reflects the sloppy code, dirty hacks, and unreadable code
It reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.
All of the above
None of the Above
Test Driven Development (TDD) involves creating tests and code almost simultaneously, while constantly improving the design.
Many Agile developers believe TDD helps ensure correct implementation while reducing the cost of change. Is TDD part of Scrum?
Yes - Scrum is a complete methodology containing everything you need to succeed
No - Scrum is only a feedback framework. It does not specify particular technical practices
Some Scrum teams fully embrace Agile technical practices. How often do these teams typically should integrate their work and re-run their regression tests?
Only at the end of each sprint
Once per day
Once per night
Continuously as things change, potentially many times per day
Which statement best describes the Sprint review
It is a mechanism to control the development team's activities during a Sprint
It is when the scrum team and stakeholders inspect the outcome of a Sprint and figure out what to do next
It is a demo at the end of the Sprint for everyone in the organisation to check on the work done
None of the Above
Who owns the Kanban board in the Sprint Backlog?
The Product Owner
The Development Team
All of the Above
None of the Above
What is the Product Owner accountable for in Scrum?
Refining the top level Product Backlog items until they are ready to be handed over to the Development Team
Writing the User Stories so they are understandable to stakeholders
Describing an Increment at the Sprint Planning and make sure that the Development Team delivers it by the end of the Sprint
Clearly expressing a Product Backlog that maximizes value and represents the needs of the stakeholders
The Development Team finds out during the Sprint that they aren't likely to build everything they forecast. What would you expect a Product Owner to do?
Re-negotiate the selected Product Backlog items with the Development Team to meet the Sprint Goal.
Cancel the Sprint.
Change the Sprint Goal.
Inform management that more resources are needed.
The Product Owner manages the Product Backlog. Who is accountable for estimating the effort to complete the Product Backlog items?
The Product Owner. The Product Owner is required to commit on delivery to the users and the stakeholders.
The Development Team. As a collective, they have a complete view of the work needed to transform Product Backlog items into Increments of product.
The PMO. They have all the history on projects delivered, and this enables the IT department to make delivery commitments.
When does the Development Team participate in Product Backlog refinement?
Anytime during the Sprint.
Never. It is the sole responsibility of the Product Owner to refine the Product Backlog.
Only during refinement meetings planned by the Product Owner.
As Part 1 of the Sprint Planning meeting.
What is pair programming?
Managers doing performance reviews by comparing one programmer's code to another's.
Two programmers write code separately. A third programmer integrates the work.
Two developers writing code together, providing constant peer review.
A developer and a tester work together to write and test code.
The Burndown Chart is a graphical representation of work left to do versus time & The Velocity Chart shows the amount of value delivered in each sprint, enabling you to predict the amount of work the team can get done in future sprints
True
False
