Agile Easy
Which of the following is delivered at the end of the Sprint?
a. A document containing test cases for the current sprint
b. An architectural design of the solution
c. An increment of Done software
d. Wireframes designs for User Interface
c. An increment of Done software
Reasoning
The output of every Sprint is an Increment of a Done Software which can be shipped off to the end user for usage. An item is only marked done if it matches the definition of done.
What should a Development Team do during a Sprint Planning meeting when they have realized that they have selected more than the items they can complete in a Sprint?
a. Get more developers onboard
b. Seek help from the other Scrum Team Members
c. Work overtime
d. Inform the Product Owner
e. Take a call to remove some of the Sprint Backlog Items
d. Inform the Product Owner
e. Take a call to remove some of the Sprint Backlog Items
Reasoning
As we are still in the Sprint Planning meeting i.e. haven’t started the Sprint yet, the developers are free to make changes to the Sprint Backlog items. They can choose to remove some of the items which they think that cannot be completed with the current Development Team’s capacity.
Note that addition or removal should always be done in consensus with the Product Owner as he is the one who decides on the Priority of these items. The removal is not allowed once the Sprint has started.
Product Backlog should be ordered on the basis of?
a. Value of the items being delivered
b. The complexity of the items being delivered
c. Size of the items being delivered
d. The risk associated with the items
e. Based on the Scrum Team choice
a. Value of the items being delivered
Reasoning
Product Backlog is ordered on the basis of the value they provide to the business.
The value may be influenced by several other factors like risk, complexity, and criticality but are not the direct basis for calculating the Value. The value of the item being delivered is calculated by the Product Owner and he is the one who is responsible for ordering the Product Backlog.
Who is responsible to measure the Project’s performance?
a. The Scrum Master
b. The Delivery Manager
c. The Product Owner
d. The Development Team
e. The Scrum Team
c. The Product Owner
Reasoning
Being the customer’s voice, it is the Product Owner’s responsibility to measure the Project’s and Release performance and see if the team is on track to complete the project on time.
In an Agile environment, what is the main responsibility of a tester?
a. Create test scenarios and test cases
b. Finding bugs
c. Create automation scripts
d. Send test execution reports to the stakeholders
e. There is no role as a Tester in Scrum
e. There is no role as a Tester in Scrum
Reasoning
In a Scrum Team, there are only three roles: Scrum Master, Product Owner, and the Development Team. No other role is allowed and there is no exception to this rule.
What does a BurnDown Chart display?
a. Project Progress
b. Amount of remaining work with respect to time
c. The velocity of the team
d. The capacity of the team members
e. How many more items can be picked up in a Sprint
b. Amount of remaining work with respect to time
Reasoning
A burndown chart represents the amount of remaining work with respect to the time.
The horizontal axis represents time whereas the vertical axis represents the amount of work remaining. The burndown chart is one of the several metrics that is used in Scrum to project the completion date of the project given the product backlog, team’s capacity and team’s velocity remains the same.
When is a Sprint Retrospective ceremony performed?
a. Whenever the team suggests
b. At the end of each Sprint
c. Whenever needed
d. Whenever the Product Owner suggests
e. Whenever the Scrum Master suggests
b. At the end of each Sprint
Reasoning
In Scrum, it is mandatory to conduct all the Scrum ceremonies including Sprint Retrospective.
Sprint Retrospective is a meeting where all the team members sit and retrospect from their current sprint and lay out the action items to improvise for the upcoming sprints. For the very same reason, Sprint Retrospective is conducted at the end of each Sprint.
What are the main responsibilities of a Scrum Master?
a. Removing Impediments
b. Facilitating meeting as and when requested
c. Helps the Product Owner order the Product Backlog
d. Consulting the Development Team and Product Owner
e. Bridging the Gap between the Team and the Customer
a. Removing Impediments
b. Facilitating meeting as and when requested
d. Consulting the Development Team and Product Owner
Reasoning
Scrum Master is the person who is responsible for facilitating/coaching the Development Team and the Product Owner to work on the day to day development activities. He is the one who ensures that the team understands the Scrum Values and Principles and is able to practice them.
At the same time, Scrum Master also assures that the Team feels enthusiastic about Agile in order to achieve the best out of the framework. Scrum Master also helps and supports the team to become self-organized and removes impediment for them.
When can a Sprint be canceled?
a. The Sprint items are no longer needed
b. Sprint can never be canceled
c. When Development is unable to complete the work
d. Information required to start the development is not available
e. Whenever the Product Owner says
e. Whenever the Product Owner says
Reasoning
The power to cancel the Sprint lies only with the Product Owner. He/She can call to cancel an ongoing Sprint when the Sprint Items are no longer required by the business i.e. the items have become obsolete.
In Scrum, when is a Sprint Over?
a. When all the Sprint Backlog Items are completed
b. When the Product Owner suggests
c. When all the Sprint Backlog tasks are completed
d. When the final testing is completed
e. When the time box expires
e. When the time box expires
Reasoning
All the Sprint activities are time boxed including Sprint. Unlike other Sprint activities, Sprint can neither be extended nor shortened.
If for instance, all the items of a Sprint are not completed, the Sprint is still marked over and the remaining item(s) is moved to the Product Backlog from where it can be scheduled to any of the subsequent sprint based on the revised priority. Similarly, the Sprint can never be shortened.
If all the Sprint items are completed before time, the development team is free to pull in the top Product Backlog items and start the development.