Mock-Test Window

After several Sprints, a key stakeholder starts using the product. The stakeholder is surprised by the slow performance and complains to the Product Owner. The Product Owner comes to the Scrum Master asking for advice. What is the best action for a Scrum Master to take?

Wait Until The Next Sprint Retrospective As It Is The Most Opportune Time To Modify The Definition Of Done. Bring The Concern To The Testers In The Development Team And Ask Them To Include Performance Testing Explain To The Product Owner That It’s Up To The Development Team To. Decide On Acceptable Performance Standards As They Own The Definition Of Done. Encourage The Product Owner To Bring The Performance Concerns To The Development Team And Work With Them On How To Improve Performance And Ultimately Have Stronger Definition Of Done.

At The End Of The Sprint. When The Item Has No Work Remaining In Order To Be Potentially Released. When Quality Assurance Reports That The Item Passes All Acceptance Criteria. When All Work In The Sprint Backlog Related To The Item Is Finished.

During Sprint Planning, the Definition of Done will help the Development Team forecast the amount of work, selected from the Product Backlog, deemed feasible to make ‘done’ by the end of the Sprint. Which two items best describes what ‘done’ means? (Choose two.)

All The Work Needed To Prepare The Increment For User Acceptance Testing. All The Work Needed To Prepare The Increment For Integration Testing. Having An Increment Of Working Software That Is Potentially Releasable To The End Users. All The Work Performed As Defined In The Definition Of Done. All The Work Completed Within The Current Skills And Expertise In The Development Team

Which three statements best describe the purpose of having a Definition of Done? (Choose three.)

It Is A Checklist To Monitor The Development Team Member’s Progress On A Task It Provides Guidance To The Development Team When They Are Forecasting Their Sprint Backlog During The Sprint Planning. As The Development Team Is Doing The Work It Provides Guidance On The Remaining Work Needed To Create The Potentially Shippable Increment By The End Of The Sprint It Helps The Development Team Defer Any Pending Work To Subsequent Sprints. It Creates Transparency And Provides A Common Understanding Of The ‘done’ State Of The Increment At The Sprint Review. It Helps The Scrum Team Decide How Much Time Is Needed Before The Sprint Can End

In what ways does the Scrum Master keep a Development Team working at its highest level of productivity?

By Removing Impediments That Hinder The Development Team And Facilitating Development Team Decisions. By Helping The Development Team With User Acceptance Tests And Tracking Defects. By Ensuring Each Member Takes Turns Speaking At The Daily Scrum And Ending The Event On Time By Keeping The Scrum Board And Burn-down Chart Updated Daily

How should multiple Scrum Teams, working from the same Product Backlog, select the Product Backlog items their teams plan to work on?

The Product Owner Will Present The Work And The Development Teams Will Select The Items They Will Work On. The Product Owner Creates Separate Product Backlogs For Each Development Team. Each Scrum Team Would Select An Equal Number Of Items. The Product Owner Assigns The Work To Each Team. The Scrum Team With The Highest Productivity Will Select The Items First

The Development Team discovers that it doesn’t have the tools and infrastructure to make each selected Product Backlog item done. What is the most appropriate action for the Scrum Master to take?

Stop The Sprint And Have The Development Team Work On The Infrastructure Before Continuing Encourage The Product Owner To Accept Partially Done Increments And Complete The Work In The Hardening Sprint. Coach The Development Team To Improve Its Skills Tools And Infrastructure Over Time And Establish A Definition Of “done” That Is Actually Possible To Achieve Given The Current Circumstances.

Your organization requires all Increments to pass user acceptance testing (UAT) before it is allowed to be released to production. Is it a good idea to postpone UAT until the end of the project to prevent the Development Team from being disrupted during the Sprints?

No Because The State Of The Product Increment Won’t Be Transparent And The Feedback Loop Would Be Too Long. T Depends On The Team’s Definition Of Done. Yes Because The Development Team Is A Self-organizing Team And Should Not Be Disrupted During Development. Yes Because Uat Is Done In A Hardening Sprint Before The Release Sprint.

A Scrum Team has been working on a product for several iterations and has an average velocity of 55 units of ‘done’ work per Sprint. A second team will be added to work on the same product. What might be the impact on the original team?

Their Velocity Is Likely Not Affected And Will Remain At 55. Their Velocity Is Likely To Drop And Be Less Than 55. Their Velocity Is Likely To Rise And Be More Than 55.

When technical debt occurs, the system will become more unstable as development progresses and code is added resulting in future work being slowed down.

What action can the Scrum Master take to ensure communication between the Development Team and Product Owner is effective?

Ensure All Communication Goes Through The Scrum Master First. Teach The Product Owner To Talk In Terms Of Technology And Technical Requirements. Observe The Communications Between Them And Facilitate Discussions If Needed Or By Request. Translate The Technologies Used By The Development Team In Order For The Product Owner To Make Decisions.

Steven is a Scrum Master of a Scrum Team that is new to Scrum. At the halfway point of the Sprint, the Product Owner comes to Steven telling him that he is concerned the Development Team will not be able to complete the entire Sprint Backlog by the end of the Sprint. What should Steven do in this situation?

Motivate The Development Team To Meet Their Commitment To The Product Owner Coach The Product Owner That With Complex Software Development You Cannot Promise The Entire Scope That Was Forecast During Sprint Planning. As More Is Learned During The Sprint Work May Emerge That Affects The Sprint Backlog. Advise The Product Owner That The Development Team Owns The Sprint Backlog And It Is Up To Them To Meet Their Commitments. No One Tells The Development Team How To Turn Product Backlog Into Increments Of Potentially Releasable Functionality Add More People To The Development Team To Meet The Product Owner’s Expectations.

They Are Not Related Because Technical Debt Is Non-functional And Velocity Is Calculated Based On End User Functionality. As The Development Team Is Working On New Product Backlog Items They May Unexpectedly Run Into Technical Debt That Will Result The Team’s Velocity Dropping. A Development Team Can Artificially Increase Velocity By Allowing Technical Debt To Be Incurred Adding Estimates To Technical Debt Will Allow The Development Team To Maintain Constant Velocity Therefore Ensuring Predictability.

Scrum addresses which of the following four risks in software development? (Choose four.)

The Complexity And Unpredictability Of The Requirements. The Stability And Complexity Of The Technology. The Skills And Working Relationships Of The People On The Teams. The Timescale Of The Planned Work. The Clear Definitions Of Stages And Gateways In The Overall Governance Model. The Definition Of Incentive And Bonus Strategies By Hr For All Team Members.

How much work must a Development Team do to a Product Backlog item it selects for a Sprint?

An Equal Amount Of Time On Analysis Design Programming Testing And Documentation. As Much As It Has Informed The Product Owner Will Be Done For Every Product Backlog Item It Selects In Conformance With The Definition Of “done”. All Development Work And At Least Some Testing. As Much As It Can Fit Into The Sprint. Any Remaining Work Will Be Moved To A Subsequent Sprint

Steven is a Scrum Master for three Scrum Teams building the same product and working from the same Product Backlog. Management wants to standardize how velocity is calculated across all three teams in order to identify which teams are high performing and which teams need more support. What would be the best two responses Steven could provide to management? (Choose two.)

There Is No Direct Relationship Between Velocity And Value. Standardizing Velocity Across Teams Is A Good Way To Understand Which Teams Are Producing The Most Value Providing Incentives Based On Velocity Can Increase The Scrum Team’s Motivation To Produce More Value. Velocity Is The Amount Of Business Functionality That A Scrum Team Creates In A Sprint. It Is Unique To That Team And Used As An Input To Sprint Planning.

The Company Founder The Board Of Directors The Head Of Product The Product’s Users

As a Scrum Master, what would you strive for if five new Scrum Teams were to work on one product?

There Should Be Five Product Owners One For Each Scrum Team The Product Has One Product Backlog And One Product Owner There Should Be Five Product Backlogs And One Product Owner To Manage Them There Should Be Five Product Backlogs And Five Product Owners.

A Clearly Defined Methodology That Defines The Software Development Process A Manual For Defining Best Practices For Software Development. A Clearly Defined And Predictable Process That Follows The Principles Of Computer Science A Framework To Address Complex Products In Complex Environment

Your company has notified the stakeholders that they will be delivering the first release of a new product within ten Sprints. On the seventh Sprint, the Scrum Team discovers that they will not be able to include all of the expected features within the first release. The Product Owner believes if they remove some items from the Definition of Done they will be able to accelerate the development process. The Development Team objects to this idea as it will lead to technical debt. As a Scrum Master, what would be the best two ways to explain to the Product Owner the impact of technical debt? (Choose two.)

As Long As There Is Still Technical Debt In The Current Release Feature Development For The Next Release Cannot Be Started. The Product Owner Must First Agree To This Impact Before Allowing Changes To The Definition Of Done. Reducing The Definition Of Done Will Introduce Unknown Errors As Development Progresses And Functionality Is Added. The System Can Become More Difficult To Stabilize As Work Progresses. Development For The Actual Release As Well As Future Releases Will Be Slowed Down In Unpredictable Ways. Releasing The Version Upon A Reduced Definition Of Done Creates False Assumptions About The Actual State Of The System. This Will Create Many Interruptions During The Development Of The Next Release As Fixes Will Need To Be Done To The Previous Release Caused From A Reduction Of Quality. The Amount Of Technical Debt Will Need To Be Analyzed In Order To Understand The Impact On Subsequent Releases In Order To Allocate Additional Sprints At The End Of The Project.

Professional scrum master 2 Quiz

🏅