776NovoGuia.5.0

What is the standard used by the Product Owner and Scrum Team to identify unfinished work in a Sprint?. Coding Standard. Definition of Ready. Testing Standard. Definition of “Done”.

What does the Scrum Master manage?. Scrum People. Scrum Framework. Scrum Technology. All of them. None of them.

Which Scrum events facilitate inspection and adaptation?. Sprint. Testing. All four events of Scrum. Analysis.

An important executive wants the Developer to take in a highly critical feature in the current Sprint. The Developers... Work on that since organization priority is more important. Ask the executive to talk to Product Owner. As empowered team, should seek the executive to select an alternative work to be removed instead.

During Daily Scrum, what plan is used as a reference to understand the changes in progress?. Sprint Backlog. Product Backlog. Sprint Burn-down.

Sprint Planning helps in: Building entire technical architecture. Staffing plan. Testing strategy. Release plan. None of the above.

One of the Scrum Teams chose to have a Developer also playing the role of Scrum Master. A Developer cannot also play Scrum Master’s role. True. False.

The team has not completed anything by Sprint end. What is the next step?. Extend the Sprint since Scrum favors "getting done". Advice Product Owner to accept completed portion of story, and plan to complete 100% of it by next Sprint, since Scrum favors "empowered teams". End the Sprint with a retrospective, since Scrum favors time boxing.

The Scrum Team, based on the learning from previous Sprints, decides to revisit the length of the Sprint. What is the appropriate Scrum event to discuss and agree on the change?. Sprint Planning. Sprint Retrospective. Daily Scrum. Sprint Review.

To effectively track the Sprint progress, Scrum mandates: Preparing Sprint burn down charts. Increasing the transparency by frequently updating the remaining work. Earned Value approach.

Only the Product Owner can come up with items that can be considered for Product Backlog. Others cannot provide input / recommendations / ideas about new items. True. False.

Sprint Planning is the only occasion where the Developers estimates the Product Backlog items. True, because without estimate, the team cannot plan what can go into the Sprint. False, estimation of Product Backlog Items is a continuous event throughout.

Which is true about Sprint Restrospective?. It focuses on Product and Sprint Review focuses on development process. It focuses on development process and Sprint Review focuses on Velocity. It focuses on development process and Sprint Review focuses on Product.

During a Sprint Review, the Scrum Master notices that the Product Owner does not use the Product burn-down graph to explain the status to stakeholder. The Scrum Master: Should coach the Product Owner on the importance of using this Scrum tool. Should cancel the review and schedule it back when the Product Owner is ready with this. Do Nothing.

A short expression of the purpose of a Sprint which is often a business need– is called as: Sprint Goal. Acceptance Criteria. Definition of Done. Product Goal.

It is mandatory that the definition of "Done" includes “Release to Production”. True. False.

Under this part of the Sprint Planning, the Developers is more active in planning and Product Owner is mostly observing or clarifying in: Topic One: Why is this Sprint valuable?. Topic Two: What can be Done this Sprint?. Topic Three: How will the chosen work get done?.

What is the definition of “Done”?. Testing strategy for Scrum Team. A standard used by Scrum Team to assess if a product Increment is “done”. Defined by Product Owner and safeguarded by Scrum Master.

A person external to the Scrum Team with a specific interest in and knowledge of a product that is required for Incremental discovery, is known as: Technical/Domain Expert. Stakeholder. Senior Management.

The estimation method recommended by Scrum is: Planning Poker. T-Shirt Sizing. Yesterday’s weather. None of the above.

The Scrum Team tries to put together some guidelines on testing approach. Who will own these guidelines?. Scrum Team. Test Lead. Scrum Master. Product Owner.

Who should participate of the Sprint Retrospective meeting? (choose 3 answers). Product Owner. Stakeholders invited by Product Owner. Scrum Master. Developers. Technical/Domain/Process experts invited by Developers.

What is required during the Sprint Review? (choose 2 answers). Product Owner’s sign-off. Stakeholders active participation. Transition sign-off. Inspection and Adaptation activities.

Does the application of Scrum guarantees the success of software projects? (choose 2 answers). Yes. Compared to Waterfall – Yes. Scrum is a framework to solve complex problems using team work. It does not guarantee anything. Scrum increases the opportunity to control risk and optimizes the predictability of progress.

The Sprint Backlog emerges during the Sprint because the Developers modifies it throughout the Sprint. In the middle of the Sprint, new work is added to Sprint Backlog. As a result, estimated remaining work will: Increase. Decrease. Stay the same.

To deliver a single product, three different Scrum Teams are formed. How many Product Owners are needed?. As many as recommended by Scrum Master. Three. One.

What are Scrum Value? (choose 3 answers). Respect and courage. Simplicity. Commitment and Openness. Creativity and Intuition. Focus.

A Scrum Team has five members. Each one works on a different product. What could we infer about the team?. The team will have higher productivity since division of work is clear. The team implements diversity, a principle of Scrum. The potential of team work and benefit of Scrum is less. All of them still will have common definition of “Done”.

The Scrum Framework is founded on: Empiricism. Empiricism and Technical Practices. Empiricism and Emotional Intelligence.

What team Velocity refers to?. Average of amount of Product Backlog Items turned into "Done" Items per Sprint. Average rate of churn of team members in Scrum Team during a Sprint. Average number of defects per Sprint normalized over all defect types.

Scrum Master forecasts the the date of release of product during Sprint Review. True. False.

In the middle of the Sprint, the Developers didn’t get some technical tools that were originally promised. This will slow down the work. What is the next best thing to do?. Scrum Master should escalate to Project Manager. Product Owner should cancel the Sprint. The Developers should assess the impact to meeting the Sprint Goal and the definition of “Done”, and find alternatives to still meet the Sprint Goal without compromising definition of "Done".

A Developers has created the Sprint Backlog in the form of a task board. What is your inference as Scrum Master?. The team can choose to represent it any form that makes sense. It is okay to have it in task board format, but it must be ensured that it follows Kanban guidelines. Scrum Master must coach the team to create proper Sprint Backlog in the form of list of backlog items, related tasks, and estimations.

Velocity is an indication of team performance. Who may use it?. The Scrum Team an internal measure to plan and track their improvements. The managers to do performance appraisals for the team. The organization to aggregate into organization level productivity.

In a new Scrum Team, a Scrum Master notices that a Developer member works on a task that is not contributing to the Sprint Goal or Sprint Backlog. What should the Scrum Master do?. Escalate this to Product Owner. Discuss with team member and educate about Scrum way of working. Do not interrupt since the team is self-managing.

The Scrum Team gathers for Sprint Planning meeting. The Product Owner has some Product Backlog items but the Developers finds that they do not have enough information to understand the work involved and to make forecast. What is the next best thing to do?. The Scrum Master cancels the Sprint. The Developers proceeds with starting with whatever is known. The Developers makes it transparent that they cannot make a forecast with insufficient information, and negotiates with Product Owner on refining the Product Backlog items to ready state. The Scrum Team discusses the root cause in the retrospective.

In the middle of the Sprint, the Developers finds that it has more capacity to take more work. What is the next best thing to do?. Make it transparent to Product Owner immediately, and collaborate to add additional work. Consult and follow Scrum Master’s and follow their direction. Keep that as a contingency to accommodate unplanned work.

The Developers is not having regular Daily Scrums. What do you have to do as a Scrum Master?. Will advise the team to think about conducting regular Scrums, but will let the team take the decision themselves as they are self-managing. Will escalate this to resource managers. Will step in directly to guard the Scrum Framework by asking action-begetting questions to team and positively influencing them to conduct Scrum events.

When a Scrum Team adds new team members for replacing some members going out, the productivity of the team. Will be negatively impacted. Will be positively impacted. Will remain the same.

Who starts the Daily Scrum?. Whoever the Developers decides should start. The person who last broke the build. The person who has the token. The person coming in last. This encourages people to be on time and helps to stay within the time-box. The Scrum Master. This ensures that the Developers has the meeting and stays within the time-box.

What is the role of Scrum Master with respect to Scrum artifacts?. Coach the team to increase the transparency of the artifacts. Decide the format of the artifacts and ensures that the team follows it. Owner of the artifacts and responsible for having them up to date.

Three Scrum Teams are working as part of a big project to develop a product. When Sprints are in motion, there will be: Three Product Backlogs, and three Sprint Backlogs. One Product Backlog, and three Sprint Backlogs. One Product Backlog and one Sprint Backlog.

In empiricism, the decisions are based on: Scientific calculation and Prediction. Meeting and Brainstorming. Observation, experience and experimentation.

What is the correct statement?. The technical design continuously evolves over the Sprints. Hence the team should have some basic guidelines to start with, but try to emerge the design through the Sprints. The team can choose to have an exclusive Sprint only to finalize the technical design. At the end, the design should be approved by the project architect. The team does not need to pay attention on the architecture as it will evolve itself as a by-product of self-organization.

The Developers are often being interrupted in the Sprint midway and assigned to work on “other” high priority items. Frequently, such interruptions lead to not meeting the Sprint Goal. The most likely cause could be. The Developers are not technically competent. The Product Owner authority is ineffective or influenced by another authority. The Sprint Planning is poor.

Select all that apply. In Sprint Planning, a Scrum Team spends lot of time in discussing and estimating Product Backlog items. It also ensures that all the work associated with each Product Backlog item are identified and sufficiently decomposed. The Sprint Planning meetings are always going beyond the time boxing. What could be the possible causes? (choose 2 answers). The Scrum Master is new. The team didn’t invest enough in Backlog Refinement. The Product Backlog size is huge. The Developers is trying to get perfect and detailed Sprint plan before starting any work.

Middle of the Sprint, the Developers finds that some of the Product Backlog Items forecast for this Sprint cannot be finished because they need significant additional effort. However, the Developers can still meet Sprint Goal with rest of the items. What is the next thing to do?. Consult with Product Owner and if they agree, have them cancel the current Sprint, and plan new Sprint with new estimations. Do not cancel or modify the Sprint. Extend the Sprint duration as required for the additional effort. Remove the Product Backlog Items that cannot progress. Collaborate with the Product Owner to add new work up to team’s capacity. Complete the Sprint.

For a Scrum Team that develops software, what provides the shared understanding of standards that software should meet in order to be accepted as complete by Product Owner?. Acceptance Criteria. Definition of ready. Definition of “Done”.

The Product Owner provides the transparency of their product plan to the stakeholders and the Scrum Team through. Sprint Backlog. Planning Backlog. Project Backlog. Product Backlog.

When multiple teams work together on the same product, each team should maintain a separate Product Backlog. True. False.

Burn-up and Burn-down charts show evolution of progress over time. In particular,. Burn-up shows increase in completion, while Burn-down shows remaining effort. Burn-up shows increase in team productivity, while Burn-down shows decrease in productivity. Burn-up shows increase in turn-around time, while Burn-down shows decrease in turn-around time.

A Scrum Team decides to have an exclusive Sprint to evolve the technical architecture. The sole outcome of this Sprint is a finalized architecture design. It is a good practice since it will help the design to emerge. It is not the Scrum approach, since every Sprint must produce at least one releasable functionality. It does not matter, since the team is self-organized about how to perform their work.

In Scrum based software development effort, while the Sprint Goal will deliver a Product Increment, one of the Product Backlog Items is asking for production of a document. It is not okay. Every Product Backlog item must be about a working software requirement. It is not okay. Documentation is not needed until Product Owner chooses to release an Increment to production. It is okay. A Sprint can produce a document as a sole outcome of the Sprint. It is okay. A Sprint can produce other deliverables like document requested by Product Owner along with working Increment.

It is essential for the Product Owner to have these skills. Usually Scrum Master serves the Product Owner by coaching him in: (choose 2 answers). Software application development. Understanding and practicing agility. Coaching team. Product planning in empirical environments.

What is the role of Scrum Master in Sprint Retrospective?. Auditor. Silent Observer. Peer Team Member. None of the above.

A Scrum Team is in the process of defining Product Backlog items. The Scrum Master notices that the team is not using User Story format to capture the backlog items. What should the Scrum Master do?. Correct the team’s behavior by coaching them about user stories. Let the team decide the format of Product Backlog items. Add a business analyst with knowledge of writing user stories to the team, with specific responsibility of documenting backlog in terms of user stories.

An organization decides to have very small Scrum Teams of size fewer than three. The likely result could be: The team may have decreased interaction. The team may have skills shortage. The team may have low productivity gains. All of the above.

The leadership model followed by Scrum Master is: Micro Management. True leader who serve the Scrum Team and the larger organization. Command and Control.

During a Sprint Review, the stakeholders notice that the product development progress is not very clearly visible and lacked transparency. Moreover, they are not able to understand the next steps. Who is responsible for this?. Developers. Product Owner. Scrum Master. Scrum Team.

When more Scrum Teams are added to a project that works on one single product, the productivity of the original Scrum Teams mostly likely will increase. True. False.

The architectural features of the product need to be: Evolved along with Sprint deliveries. Completely designed upfront before the Sprints. Decided at least at skeleton level in Sprint zero.

Sprint longer than one calendar month may result in: Too much to inspect in short meetings. Detached stakeholders. Increased complexity needing more traditional controls like documentations. All of the above.

The work left against time is shown by: Team Velocity. Burn-down graph. Story Points Burn. Release Burn-up.

In Sprint Review, along with the review of the product Increment and progress, “what (steps) to do next” is also discussed. False. True, and the scope of the next Sprint is also finalized here. True, and it may capture probable backlog items for next Sprint, but the scope of the next Sprint is deferred until Sprint Planning.

A Scrum Team decides that the frequency of Daily Scrum should be reduced to once per week. Is this consideration correct?. Yes, because the Scrum Team is self-managed. So they can choose their practices. No, self-management is alright but such decisions need to be approved by agile coach. So, they should involve agile coach. No, self-management is about how to get the Sprint work done but subject to following Scrum. So, Scrum Master should strive to coach the team on the essentials of Daily Scrum.

Every Sprint, the working Increment should be tested progressively from unit testing, to integration testing, and then user acceptance testing. Yes. It is the prescribed method. No. The test strategy is decided by the Quality Assurance Lead in the team. Not necessary. While the team needs to ensure that each Increment is thoroughly tested, ensuring that all Increments work together, and meets definition of “Done”, it is up to the team to find best method to achieve this. Incorrect. It should also include non-functional testing.

Definition of “Done” is: Initially defined per product by Scrum Team, but may change throughout the product development duration. Initially defined per Scrum Team, and does not change. Defined after first Sprint based on the new insights obtained from first Sprint Review.

Which of the following statements are true? (choose 2 answers). After Sprint Planning, a Sprint cannot proceed without complete requirement specification. After Sprint Planning, a Sprint cannot proceed without a Sprint Goal. After Sprint Planning, a Sprint can proceed without a complete Sprint Backlog. After Sprint Planning, a Sprint cannot proceed without complete architecture.

The Developers is self-managed and empowered. They are also the authority on deciding what business needs are required to be developed. True. False.

A Product Owner can not send a representative (delegate) to the Sprint Review. True. False.

What is an Increment?. The sum of the value of all increments from previous iterations integrated with the Product Backlog Items “done” in latest Sprint. The sum of Product Backlog Items selected into Sprint Backlog. The sum of Product Backlog Items “done” in latest Sprint.

What are the true statements? (choose 2 answers). Scrum Team is responsible for formulating a Sprint Goal. When existing Product Backlog Items in the Sprint Backlog are modified, the Sprint Goal is bound to become invalid. The coherence between Product Backlog items is made transparent by Sprint Goal. Lack of coherence will lead to Developers working individually.

What events the all member of Scrum Team participates? (choose 3 answers). Sprint Planning. Daily Scrum. Sprint Review. Sprint Retrospective.

A Scrum Team can identify the improvements only during the Sprint Retrospective. True. False.

When a Sprint is cancelled, the Scrum Team discards all the work and refines a new Product Backlog. True. False.

What is a key inspect and adapt meeting for the Developers?. Project Status Meeting. Daily Scrum. Design Sessions.

What are the true statements?(choose 2 answers). Only the Product Owner should update the Product Backlog without delegating to anyone. Only the Developers should be responsible for estimates of Product Backlog Items. Only the Product Owner should cancel the Sprint. Others can influence the decision to cancel. Only the Product Owner can change the Sprint Backlog.

At the end of Sprint Planning, the Developers could not decompose all of the work into units of one day or less. It could decompose the work for only the first few days of the Sprint. The Developers should close the Sprint Planning and start the work. Since the team is self-managed, they should continue Sprint Planning in the following days before they start the work. The Scrum Master should coach the team in required skills.

Which is not a Product Backlog Management activity in Scrum?. Clearly expressing and ordering Product Backlog items. Optimizing the value of the work the Scrum Team performs. Using formal change control to manage Product Backlog when market provides feedback from Product usage. Ensuring the Developers understands items in the Product Backlog to the level needed.

Sprint Backlog is modified throughout the Sprint. What does Developers need to do as soon as a new task is identified?. Product Owner adds it to the Sprint Backlog and communicates about it to Scrum Team. Scrum Master adds it to the Sprint Backlog and communicates about it to Scrum Team. Developers adds it to the Sprint Backlog and communicates about it to Scrum Team.