PSPO Practice Exam Questions and Answers (Latest 2023 - 2024) Complete Solutions, Exams of Advanced Education

Download PSPO Practice Exam Questions and Answers (Latest 2023 - 2024) Complete Solutions and more Exams Advanced Education in PDF only on Docsity!

PSPO Practice Exam Questions and Answers

(Latest 2023 - 2024) Complete Solutions

W hich of the following is not a good idea to have in a brainstorming session?

Send meeting invites with a clear agenda in advance.

Have an experienced facilitator lead the session.

Allow people to criticisms openly for the ideas so that there will be constructive discussion.

Have a diverse group so as to consider many different perspectives. - Allow people to criticisms openly for the ideas so that there will be constructive discussion.

Brainstorming sessions are used for used for risk management, planning, prioritization, estimation, retrospectives, or problem solving. Allowing people to vent their frustrations or criticize is not leads to constructive discussion.

Who Pull Product Backlog items for the Sprint? - Dev Team

Sam is from product and marketing area, but he is not an expert in software development. He was assigned as the Product Owner. Should we choose another person instead?

Yes, we need an expert on our specialist work, capable of communicating with the customer

Yes, we need an expert on our specialist work, who is part of the Team

No, he doesn't need to be an expert on our specialist work, given that he gets expert help when needed

No, he doesn't need to be an expert on our specialist work, he just needs to be business oriented - No, he doesn't need to be an expert on our specialist work, he just needs to be business oriented

The Product Owner is to be mainly business-oriented, and they do not need to be technical; Development Team handles all the technical aspects of the project.

• If you manage a digital product that end users employ, such as a web or mobile app, then you usually do not require in-depth technical skills, such as, being able to program in Java, write SQL code, or know which machine learning framework there are and if, say, TensorFlow is the right choice for your product.
• if you look after a technical product — a product that is integrated into a larger offering like a physics engine, which forms part of a computer game—then you will require the appropriate technical skills in order to formulate technical requirements and define software interfaces (APIs).
• the same applies if you are a component owner, someone who looks after an architecture building block like a service, component, or layer that forms part of a digital product: You will benefit from having hands-on experience in the appropriate technologies.

How does an organization know that a product built through Scrum is successful?

By measuring that velocity has increased since the last release

By releasing often, and updating key performance indicators (KPIs) on value after every release and feeding this information back into work on the Product Backlog

By measuring the actual time spent on development versus the time estimated for development

By the Product Owner and stakeholders accepting the Increment at the Sprint Review - By releasing often, and updating key performance indicators (KPIs) on value after every release and feeding this information back into work on the Product Backlog

Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. If a product isn't released, the opportunity to capture user and market feedback is lost.

When should the Product Owner update the project plan?

The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.

Before the Sprint Planning to know how much work will have to be done in the Sprint.

After the Daily Scrum to ensure an accurate daily overview of project progress.

Scrum forbids having a project plan.

The Product Owner shouldn't be occupied by that. It is work for the Project Manager. - The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.

The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful.

The Agile Principle "Simplicity - the art of maximizing the amount of work not done - is essential" is best summed up by which phrase?

Maximize your work.

Avoid waste.

Work as little as possible.

What matters is quantity.

Only deliver once completed. - Avoid waste.

Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.

How does Definition of "Done" help to the Scrum Team? Select the three most applicable items.

DoD is used to assess when work is complete on the product Increment

Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning

DoD helps in inspection and adaptation

DoD ensures artifact transparency

DoD helps to calculate velocity of the Scrum Team - DoD is used to assess when work is complete on the product Increment

Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning

DoD ensures artifact transparency

According to Scrum guidelines, who is responsible for hiring or assigning a new person into a Team?

ScrumMaster

Product Owner

This is outside of the scope of Scrum

The self-managing Team - This is outside of the scope of Scrum

Hiring or assigning a new person is outside of the scope of scrum.

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

As much work as the Team can fit into a Sprint.

All of the analysis, design, development, testing and documentation work.

The best amount of work the Team can do given that is usually impossible for QA to finish all of the testing that is needed to prove it can be shipped.

As much work as it has told the Product Owner will be done for every Product Backlog item it selects. - As much work as it has told the Product Owner will be done for every Product Backlog item it selects.

Definition of "Done" is used to assess when work is complete on the product Increment. So development team has to do as much as work it has committed to PO as per DOD.

How does an organization measure effectiveness of scrum & know if a product built is successful?

By measuring that velocity has increased since the last release

By releasing often, and updating key performance indicators (KPIs) on value after every release and feeding this information back into work on the Product Backlog

By measuring the actual time spent on development versus the time estimated for development

By the Product Owner and stakeholders accepting the Increment at the Sprint Review - By releasing often, and updating key performance indicators (KPIs) on value after every release and feeding this information back into work on the Product Backlog

Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. If a product isn't released, the opportunity to capture user and market feedback is lost.

Tom is a member of the Scrum team. He attended a trade conference and came across a feature idea that he felt should be present in the product he was working on. When should that idea be included in the product backlog?

When the team is done with their current Sprint and is ready to start planning the next sprint

After all the features committed for the current release are completed and delivered

When the idea can be prioritized in context of the other product backlog items - As soon as Tom is able to discuss the idea with the Product Owner

Requirements never stop changing, so a Product Backlog is a living artifact. Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog. So discuss new ideas as soon as possible.

A Development Team is waiting for a specific software component that they need to integrate and use. The component should be ready in two months. The Backlog Items with highest priorities depend on this specific component. What should the Product Owner do?

Nothing. The existing order in the Product Backlog already reflects values of specific Items. The most valuable items are on the top.

Re-order the Product Backlog to maximize utilization of the Development Team and deliver at least some Increment of product functionality in the next Sprint

Remove the dependent Items from the Product Backlog and put them in a special wait list. When the dependency is resolved, the Items should be returned back

Transfer the dependent Items to the Integration Team - Re-order the Product Backlog to maximize utilization of the Development Team and deliver at least some Increment of product functionality in the next Sprint

The ordering of the Product Backlog is a key mechanism for reducing and eliminating dependencies. Usually Items with external dependencies are not considered "Ready" for selection unless the other team is at the Sprint Planning to make their commitment. Development Teams should deliver an Increment of product functionality every Sprint.

There is serious issue and delivery slippage happening in a scrum team. The Business Owner calls for a meeting to discuss this. Who should attend the meeting mentioned in the previous question?

Product Owner

Scrum Master

Team

Product Owner and Scrum Master

All three roles - Product Owner is the contact point, and responsible for all the communications

Your team is getting ready to start a new sprint. The product owner refers to a requirements document for a large feature, and begins to break it down into user stories that can be planned in small increments. What is this practice called?

Work breakdown structure

Big requirements up front

Just-in-time requirements refinement

Waterfall approach - Decomposing the work into stories just before you plan an increment is called just-in-time requirements refinement. By breaking down the work right before the work begins, you're sure to take any changes that might have happened to the requirements into account before you build.

Management has planned for over two hundred (200) developers to work on a new, critical product. Prior to them being formed into teams and beginning to develop the software, an overall architecture and integrating design is needed. Which of the following approaches employs Scrum and Agile principles most effectively?

Form a cross-cutting team of architects and designers. This team will serve as consultants to the other Scrum teams as integration questions arise during development.

Form one or two teams of the best developers to create a foundation that represents the nonfunctional requirements and also several high value functions. Then increase the number of teams using the shared architecture.

Design and instantiate an appropriate Service Oriented Architecture (SOA) before beginning feature development. Train Development Teams on how to consume the shared SOA in their feature development, then begin feature development Sprints.

Have the best designers and developers create an appropriate design and architecture. Include design models that the rest of the developers will include while implementing features. - Form one or two teams of the best developers to create a foundation that represents the nonfunctional requirements and also several high value functions. Then increase the number of teams using the shared architecture.

When a product grows, it is quite possible that the PO will get help from other Product Managers and others in the organization who interact regarding the customer facing activities and knowledge

of the product marketplace. Is it a good idea for the PO to proxy or outsource some of their PO Scrum Team duties to these people (for example, Scrum Team facing duties)?

No

Yes - When a product grows, it is quite possible that the PO will get help from other Product Managers and others in the organization who interact regarding the customer facing activities and knowledge of the product marketplace.

While it is fine for the PO to be aided by the aforementioned people, it is NOT acceptable for the PO to attempt to proxy or outsource their PO Scrum Team duties, especially the Scrum Team facing duties.

Define the term "Selected Product log" in sprint planning meeting. Mark one answer:

Product backlog at the beginning of the session.

Sprint review meeting at end of sprint.

Product backlog at the end of second session.

Impediments impact to resolve them. - Product backlog at the end of second session.

Having set the Sprint Goal in first session, the Development Team decides how it will build this functionality into a "Done" product Increment during the Sprint. The Product Backlog items selected for this Sprint plus the plan for delivering them is called the Sprint Backlog.

The Product Owner's authority to change and update the Product Backlog is unlimited, except for:

Decisions by the CFO, the CEO or the board of directors.

Nothing. The entire organization must respect a Product Owner's decisions.

Decisions by the chief program manager.

Technical and architectural work that needs to be done first, as indicated by the chief enterprise architect.

High impact changes that have not been approved by the change request board.

Work for which impediments exist that the Scrum Master still needs to resolve. - Nothing. The entire organization must respect a Product Owner's decisions.

For the Product Owner to succeed, the entire organization must respect his or her decisions. No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn't allowed to act on what anyone else says.

Remember the future' and 'Prune the product tree' are examples of ___________ and used to ___________.

Estimation techniques, determine relative size of stories

Prioritization techniques, determine relative priorities of stories

Brainstorming techniques, solve problems

Innovation games, collect requirements - Innovation games, collect requirements

Innovation games, also called Collaborative games, are forms of group creativity techniques. Buy a feature, Product box, Prune the product tree, 20/20 vision, Remember the future, Me and my shadow, Sailboat, Bang-for the buck, Start your day, The apprentice, My worst nightmare and Force field analysis are innovation games for collecting requirements.

A team that is proposing to transition to Agile is in the process of designing the office space. There is a lot of discussion and debate about the open seating. Rebecca - who is one of the team members felt it was important to have her own private space where she could feel "at home", have pictures of her family around, etc. How should the team proceed?

Provide some space for private stuff (caves) for doing private work, but keep the project space (commons) open

Provide some space for private stuff (caves) for doing private work, but keep the project space (commons) open

Let Rebecca keep the photographs on her computer's desktop instead of pinning up in the cubicle

Wait for everybody to agree to the idea, do not force the team - Provide some space for private stuff (caves) for doing private work, but keep the project space (commons) open

Explanation: The "caves and commons" arrangement in Agile office space design does allow for some private space that team members often feel they need. But they also combine it with a common space where they reside when they are working on "project" activities

Can the Product Owner and the ScrumMaster be the same person

No. The person would have too much power and it would create confusion

Yes, if the person has the authority and empowerment to do both things

No. It would take too much of one person's time

Yes, as long as the person can balance both responsibilities with care - There are exceptions to every rule, and it is possible for one person to serve both roles successfully. Just keep in mind that this isn't the norm, nor should it be a long-term solution. To give your organization the best chance for success when using scrum, allow two distinct individuals to serve these roles. Even if you're struggling to find those with the right aptitude, you'll be better off with two people who have a passion to grow into their respective roles, rather than one exceptional individual struggling to balance both.

The ScrumMaster is one individual who focuses on supporting the team and protecting the team. Trying to help them achieve a sustainable pace, help them as they try to deliver high quality, and really be a servant to the team.

The Product Owner is focused on prioritizing, getting the backlog ready, and they're asking for "more, more, more" when it comes to business value. So, those two can be in conflict, and that can be healthy.

What part of the Sprint Backlog is used for the Sprint burndown chart?

The percentage of work completed by each Team member.

The number of Product Backlog items completed by all the Team members.

The actual time spent on each task by each team member.

The remaining time required to complete each task by each team member. - The remaining time required to complete each task by each team member.

The Sprint Burndown Chart makes the work of the Team visible. It is a graphic representation of the rate at which work is completed and how much work remains to be done

Software dependencies could influence how the Product Owner orders Product Backlog Items.

True

False - Software dependencies doesn't influence PO ordering of backlog items. Backlog items are order as per value and to best achieve goals and missions.

A team is working on a cutting-edge technology and does not have a lot of familiarity with the technical environment. As a result, it is struggling to estimate a complex story because the approach itself is not clear. How should the team proceed?

Make a suitable assumption and proceed with planning - setting clear expectations that there is no guarantee about the estimates

Write a SPIKE story (a story for carrying out the research and technical investigation) and time box it before accepting the main story for planning

Cancel the Sprint and send the entire team for a technical training so that such issues can be avoided in the future

Defer the story and first pick up stories which are clearer to the team - The best way to remove uncertainty of a technical nature is to perform experimentation - which is the intent of a SPIKE story. When a story cannot be estimated because the team needs to experiment, the best approach is to write a spike story before working on the main story

For an organization planning to transition to Scrum, the Scrum coach is planning for a few training sessions to develop the ability to succeed in Agile and Scrum methods. Which of the following trainings is most relevant for programmers or developers?

Design patterns and architecture

Evolutionary design

Scrum Master training

Team working - We make the assumption that programmers have basic knowledge about ideas like design patterns or working with teams. When they move to Scrum, one of the first things that will change is that the design will evolve rather than be determined upfront. Therefore, evolutionary design is the most relevant training at this stage.

Which is one of the most popular product backlog prioritization techniques?

Kano modelling

Canoe modelling

Wedding cake model

Planning Poker - The Kano modelling is one of the most popular backlog prioritization techniques where in this method, the requirements are prioritized based on the customer preferences.

• Attractive
• One-Dimensional
• Multi-Dimensional
• Must-Be
• Indifferent
• Reverse

What is the Product Owner accountable for in Scrum?

A) Describing an Increment at the Sprint Planning and make sure that the Development Team delivers it by the end of the Sprint

Missed correct answer

B) Clearly expressing a Product Backlog that maximizes value and represents the needs of the stakeholders

C) Refining the top level Product Backlog items until they are ready to be handed over to the Development Team

D) Writing the User Stories so they are understandable to stakeholders - B

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. The primary tool to do so is the Product Backlog.

The Scrum Team should choose at least one high priority process improvement, identified during the Sprint Retrospective, and place it in the Product Backlog.

True

False - False, to ensure continuous improvement, the Sprint Backlog rather than the Product Backlog includes at least one high priority process improvement identified in the previous Sprint Retrospective meeting.

An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?

A) Without a new vocabulary as a reminder of the change, very little change may actually happen.

Incorrect answer

B) The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost.

C) Management may feel less anxious.

D) All answers apply. - D

What focus areas that are considered in executing Value Driven Development by the Product Owner? - In executing Value Driven Development, the Product Owner must consider the focus areas of:

i. Product Value Maximizer

ii. Product Visionary

iii. Product Marketplace Expert

iv. Product Release Decision Maker

v. Lead Facilitator of Key Stakeholder Involvement

vi. Other Product Owner role Considerations

The Product Owner wants to apply some non-functional requirements to the Product. What is the best way to proceed?

Find a way to convert non-functional requirements into Product features and act accordingly

Add the non-functional requirements to the DoD and check every Increment against these criteria

Create a new Item for every requirement in the Product Backlog

Non-functional requirements cannot be handled within the bounds of Scrum - Add the non- functional requirements to the DoD and check every Increment against these criteria

Non-functional requirements describe qualities of the Product being developed. For example, the Product should be secure and extensible. The only way to meet such requirements is to have them as a part of the DoD and check every Increment against these criteria.

What is Product Owner work that a Product Owner might delegate?

Write User Stories

Order the Product Backlog

Represent stakeholders to the Scrum team

Attend the Sprint Review - Order the Product Backlog

The Product Owner is the sole person responsible for the Product Backlog. However, he or she can delegate some work related to product backlog management to the Development Team.. Product Backlog management includes:

Clearly expressing Product Backlog items;

Ordering the items in the Product Backlog to best achieve goals and missions;

Optimizing the value of the work the Development Team performs;

Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,

Ensuring the Development Team understands items in the Product Backlog to the level needed.

Which two (2) metrics will help a Product Owner establish that value is being delivered?

Time to market

Customer satisfaction

Velocity

Productivity

Budget spent - Customer satisfaction and velocity of scrum team are the two metrics which help a PO to establish the value that is being delivered.

How does Definition of "Done" help to the Scrum Team? Select the three most applicable items.

DoD is used to assess when work is complete on the product Increment

Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning

DoD helps in inspection and adaptation

DoD ensures artifact transparency

DoD helps to calculate velocity of the Scrum Team - DoD is used to assess when work is complete on the product Increment

Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning

DoD ensures artifact transparency

Which questions are asked in the Daily Scrum Call? Select all that apply.

What was done yesterday?

What will be done today?

Are there any impediments?

None of them - There are no questions asked in the Daily Scrum Call, the participants simply informs/explains the team what was done yesterday, what is planned to be done that day, and if there are any issues/impediments that the participant may be facing.

By use of which methods, the development team can identify the relationship between user stories and release plans.

Hierarchical trees

Tree Mapping

Story Mapping

Stakeholders - Story mapping consists of ordering user stories along two independent dimensions. The "map" arranges user activities along the horizontal axis in rough order of priority (or "the order in which you would describe activities to explain the behavior of the system"). Down the vertical axis, it represents increasing sophistication of the implementation.

A property functioning Scrum Team will have at least one Release Sprint and may well have several.

True

False - False

The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done".

Development Teams deliver an Increment of product functionality every Sprint. This Increment is useable, so a Product Owner may choose to immediately release it but to release or not its dependent on POs discretion. The increment must be in useable condition regardless of whether the Product Owner decides to release it.

In the context of Scrum, what is meant by "Staging" requirements? Choose only ONE best answer.

Non-functional requirements for scaling

Showing 'done' requirements to stakeholders

Organizing requirements into different stages

Functional requirements for demonstration - Non-functional requirements for scaling

The process of defining and prioritizing the nonfunctional requirements for scaling is called staging. Staging occurs prior to the start of the first Sprint and takes just one day. During this day, the nonfunctional scaling requirements for this particular project are determined and placed in the Product Backlog.

What is true regarding Grooming Horizon on large Scrum Projects?

Grooming horizon increases

Grooming horizon decreases

Grooming horizon doesn't change

No Grooming is performed on large Scrum projects - Grooming horizon increases

Product backlog items are still decomposed and refined just in time on large Scrum projects. But the grooming horizon changes. Rather than focusing on the subsequent sprint, large projects look ahead to the next two to three sprints when preparing the product backlog

Could the Product Owner and the Scrum Master be a part of the Development Team?

No

Yes - Yes. Scrum does not prohibit the Product Owner or the Scrum Master do development work. However, it is not the best practice because it could create a conflict of interest.

Who is the leader in terms of getting feedback from the Key Stakeholders in the Sprint Review?

The Scrum Master

The Product Owner

The Scrum Team

The Development Team - The Product Owner is a vital leader in terms of getting feedback from the key stakeholders in the Sprint Review.

What is the Sprint Backlog?

The Product Backlog items selected for this Sprint

The Product Backlog items selected for this Sprint plus the plan for delivering them

The Product Backlog items selected for this Sprint plus a set of Development Team internal tasks

Superset of Product backlog including detailed tasks and acceptance criteria. - The Product Backlog items selected for this Sprint plus the plan for delivering them

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

What One of your stakeholder wants more detail than the vision statement provides, but not the overwhelming detail of the release and iteration plans. Which of the following progress report will you share with this stakeholder?

Roadmap

Status email

Iteration plan

Productivity chart

Burn down chart - Roadmap

Some stakeholders may want more detail than the vision statement provides, but not the overwhelming detail of the release and iteration plans. For these stakeholders, consider maintaining a document or slide deck that summarizes planned releases and the significant features in each one.

What does the word "development" mean in the context of Scrum? Select the best option.

Product development, its releasing and sustaining

Development of an operational environment for the Product

Complex work that can include all the suggested options and even more

Software and hardware development

Research and identifying of viable markets, technologies, and Product capabilities - When the words "develop" and "development" are used in the Scrum Guide, they refer to complex work including software and hardware development, development and releasing of products and enhancements, development and sustaining product operational environments, research and identifying of viable markets and technologies, and even more.

All the Scrum Teams working on the same product should have the same Sprint length.

True

False - False. Sprints don't have to be synchronized or of the same length, but it will probably be more efficient if they are.

Also, Sprint lengths don't have to be the same, but the boundaries should align. For example a team might reasonably conduct 2 Sprints of 2 weeks within a Nexus 4 week Sprint, but a 3 week team Sprint would be less feasible as it would not articulate to the Nexus cadence.

A done Increment is valuable if: (Choose 2 answers)

It is likely to increase customer satisfaction

It meets the business analyst's specifications

It is delivered when the Product Owner expected it

It reduces long-term operational costs

It has all the features that the Product Owner wanted in that Sprint - At the end of a Sprint, the new Increment must be "Done," which means it must be in useable condition and meet the Scrum Team's definition of "Done". So it should be as per PO expectation and should contain all features.

Which one of the following is a key feature of documentation that you would expect to find in an Agile project?

System documentation created at the end of each increment, at the start of the deployment

User Stories held in a spreadsheet or specialist database, where full details of user conversations are recorded for future purposes, like handover to maintenance or support

User Story cards containing only enough detail for planning and development, which will need to be supplemented by further face-to-face conversations

No written documentation, as all good communication is face-to-face - User Story cards containing only enough detail for planning and development, which will need to be supplemented by further face-to-face conversations

User stories are part of an agile approach that helps shift the focus from writing about requirements to talking about them. All agile user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality. User stories are often written on index cards or sticky notes and arranged on walls or tables to facilitate planning and discussion. As such, they strongly shift the focus from writing about features to discussing them. In fact, these discussions are more important than whatever text is written.

How does an organization know that a product built through Scrum is successful? (choose 2 answers)

Choose ALL answers that apply.

A Reduced costs

B Increased customer satisfaction

C Delivering an increment every Sprint

D Through frequent releases and meeting value metrics or KPIs

E Improve the velocity - B,D

Customer and end user satisfaction is important. It's not an abstract measure like lines of code or velocity.There can be some KPIs for measuring the value of the releases, and when improved, will show our success. Increased velocity is desired, but it's not directly connected to value and can be misleading. That's the same with production cost.It's mandatory to deliver an Increment every Sprint.

Who are the typical Key Stakeholders (select three)?

Choose ALL answers that apply.

A The people responsible for making the funding decisions for the product development effort

B The people responsible for product marketing

C The human people who actually use the product under development

D The people responsible for paying to use the product

E The people responsible for product development - The correct answer is 'A' 'C' 'D'

A typical stakeholder is a man who is responsible for making the funding decisions for the product development effort, the user of the product, the man who is responsible for paying to use the product

How should the Product Owner forecast the completion date?

Choose only ONE best answer.

A By any method she or he finds appropriate

B By dividing the remaining amount of work in the Product Backlog to the latest calculated velocity

C By using a trend line in the burn-down chart

D This is the responsibility of the Scrum Master to forecast the completion date - The correct answer is 'A'

Using a trend line in the burn-down chart can help (if the team is using that chart), as well as simple or complex formulas such as the one mentioned above. But all of these are just guides for the Product Owner and s/he should consider all factors and come up with a reliable completion date forecast.

Who should know the most about the project performance?

Choose only ONE best answer.

A The Scrum Master

B The Scrum Team

C The Product Owner

D The project manager

E The Development Team - Measuring the release or project performance is the Product Owner's responsibility.

Measuring the Sprint performance is the Development Team's responsibility.

Which KVA categories should the Product Owner consider to measure and track the creation and delivery of value to the marketplace (select three)?

Choose ALL answers that apply.

A Employee Satisfaction

B Current Value

C Ability to Innovate

D Capability Building

E Time-to-Market - The correct answer is 'B' 'C' 'E'

The current value is the organization's current value in the marketplace. The three pillars of value are:

• ability of employees to generate revenues
• likelihood of the employees to continue creating value
• likelihood of the customer to continue generating revenues

There are other measurements that could have been used. However, most either was later reflected in these measures, or they were circumstantial, explained in a number of indirect ways.

Time to market consists of direct evidence of the software organization's ability to bring new features, functions, and products to the customers. Productivity was excluded, as speed is only one component of time to market; lean, focused functionality comes to market quicker than overburdened functionality developed with higher productivity. Much of the software in the marketplace is encumbered. Despite being able to get it to the market rapidly, the customers may not want to implement it. They may have found that it was too hard to implement the last release, that much of the functionality was irrelevant to their needs, and that the overall product was flawed with unneeded functionality as well as hard to use because of defects. As this occurs to software,

more and more of the software organization's budget is consumed maintaining the product, further reducing the funds available to innovate.

In which meetings the Key Stakeholders are allowed to participate?

The Sprint Review

The Sprint Retrospective

The Sprint Planning

The Daily Scrum - The Key Stakeholders are allowed to participate only in the Sprint Review meeting. However, any member of the Scrum Team can interact with them any time.

When the Scrum Team is allowed to interact with the Key Stakeholders (select the most applicable option)?

The Daily Scrum

The Sprint Review

Any time where it's valuable to have the Stakeholder input

The Sprint Retrospective - The Product Owner is responsible for making sure that the Key Stakeholders attend and interact in the Sprint Reviews, but really the Stakeholders can be involved with the Scrum Team any time where it's valuable to have the Stakeholder input.

Who is responsible for monitoring progress toward Goals?

The Scrum Master and The Development Team

The Scrum Team

The Product Owner

The Product Owner and The Development Team

The Scrum Master

The Development Team - The Product Owner tracks total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders.

Where Scrum can be used? Check all the applicable items.

Research and identifying of viable markets, technologies, and product capabilities

Development and sustaining of Cloud and other operational environments

Development of software and hardware

Development of products and enhancements

Managing the operation of an organization

Development of almost everything we use in our daily lives as individuals and societies - All - as written in SG

Who is responsible for coping with incomplete artifact transparency?

The Product Owner

The Scrum Team

The Development Team

The Scrum Master - The Scrum Master's job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change.

What belongs solely to the Development Team?

The Definition of Done

The Product Backlog