Tuesday , June 25 2024
Breaking News

Scrum Fundamentals Certified Exam Answers

Scrum Fundamentals Certified
  • 5
  • 6
  • 3
  • 2
  • Product Owner
  • Scrum Master
  • Stakeholder
  • Scrum Team
  • Conduct Daily Standup
  • Create Prioritized Product Backlog
  • Ship Deliverables
  • Retrospect Sprint
  • III – VI
  • III – V – VI
  • I – II – VII – VIII
  • III – IV – VI
  • Specialized teams.
  • Detailed upfront planning.
  • Value-based Prioritization.
  • Non-iterative delivery.
  • Daily Standup: 15 minutes
  • Retrospect Sprint Meeting: 8 hours
  • Sprint Planning Meeting: 8 hours
  • Sprint Review Meeting: 4 hours
  • This principle describes how time is considered a limiting constraint in Scrum, and used to help effectively manage project planning and execution. The elements in Scrum subject to this principle include Sprints, Daily Standup Meetings, Sprint Planning Meetings, and Sprint Review Meetings
  • This principle highlights the focus of Scrum to deliver maximum business value, beginning early in the project and continuing throughout.
  • This principle focuses on today’s workers, who deliver significantly greater value when encouraged to self-organize rather than be subject to the command and control style of traditional project management.
  • This principle focuses on the three core dimensions related to collaborative work: awareness, articulation, and appropriation. It also advocates project management as a shared value-creation process with teams working and interacting together to deliver the greatest value
  • Product development is a shared value-creation process.
  • Iterative development helps manage changes effectively.
  • Emphasis is on delivering maximum business value in a minimum time span.
  • Time is a limiting constraint.
  • Continuous improvement, which leads to better processes.
  • Increased competition, which increases team motivation.
  • Minimized Change Requests, which reduces rework.
  • Mitigated risks, which increases efficiency.
  • Time-Boxing
  • Collaboration
  • Value-based Prioritization
  • Self-organization
  • Product Backlog
  • Acceptance criteria
  • Project Vision
  • Roles and Responsibilities
  • To secure approval and acceptance of the product or service by the Product Owner.
  • To discuss dependencies across teams.
  • To retrospect the project and identify, document, and internalize the lessons learned.
  • To develop the functionality described in each User Story
  • Awareness, Articulation, and Appropriation.
  • Transparency, Precision, and Coordination.
  • Perfection, Cooperation, and Comprehension.
  • Honesty, Responsiveness, and Adaptability.
  • Collaboration.
  • Iterative Development.
  • Refined Reporting.
  • Value-based Prioritization.
  • Ship Deliverables
  • Retrospect Sprint
  • Conduct Daily Standup
  • Create Prioritized Product Backlog
  • Transparency, correction, and initialization
  • Transparency, inspection, and adaptation
  • Initiation, correction, and adaptation
  • Transparency, initiation, and adaptation
  • Develop Epic(s)
  • Form Scrum Team
  • Create Prioritized Product Backlog
  • Create Project Vision
  • Sprints
  • Stages
  • Change requests
  • Daily Standup meetings
  • Team Leader
  • Scrum Team
  • Scrum Master
  • Product Owner
  • It is an optional role, which generally consists of a set of documents and/or a group of experts who are typically involved with defining objectives related to quality, government regulations, security, and other key organizational parameters.
  • It is a collective term that includes customers, users, and sponsors, who frequently interface with the Scrum Core Team, and influence the project throughout development.
  • It is a role in bigger projects with multiple Scrum Teams. This role is responsible for coordinating the work of multiple Product Owners.
  • It is responsible to coordinate Scrum-related activities in large projects which may require multiple Scrum Teams to work in parallel.
  • Product Backlog
  • Project Vision statement
  • Epic(s)
  • Acceptance criteria
  • This principle describes how time is considered a limiting constraint in Scrum, and used to help effectively manage project planning and execution. Time-boxed elements in Scrum include Sprints, Daily Standup Meetings, Sprint Planning Meetings, and Sprint Review Meetings
  • This principle focuses on today’s workers, who deliver significantly greater value when encouraged to self-organize rather than be subject to the command and control style of traditional project management.
  • This principle focuses on the three core dimensions related to collaborative work: awareness, articulation, and appropriation. It also advocates project management as a shared value-creation process with teams working and interacting together to deliver the greatest value
  • This principle highlights the focus of Scrum to deliver maximum business value, beginning early in the project and continuing throughout.
  • Scope
  • Risk
  • Quality
  • Project closure
  • Scrum Master
  • Chief Scrum Master
  • Scrum Guidance Body
  • Program Product Owner
  • He/she is the person responsible for achieving maximum business value for the project. He or she is also responsible for articulating customer requirements and maintaining business justification for the project. They represent the Voice of the customer.
  • He/she is a facilitator who ensures that the Scrum Team is provided with an environment conducive to completing the project successfully. They guide, facilitate, and teach Scrum practices to everyone involved in the project; clear impediments for the team and ensure that Scrum processes are being followed
  • She/he is responsible for creating the Deliverables of the project.
  • He/she is responsible for coordinating Scrum-related activities in large projects which may require multiple Scrum Teams to work in parallel.
  • 4
  • 5
  • 6
  • 7
  • Release Planning
  • Sprint Planning
  • Retrospective Sprint
  • Project Vision
  • This principle emphasizes the core philosophy of Scrum based on the three main ideas of transparency, inspection, and adaptation.
  • This principle focuses on today’s workers, who deliver significantly greater value when encouraged to self-organize rather than be subject to the command and control style of traditional project management.
  • This principle focuses on the three core dimensions related to collaborative work: awareness, articulation, and appropriation. It also advocates project management as a shared value-creation process with teams working and interacting together to deliver the greatest value
  • This principle highlights the focus of Scrum to deliver maximum business value, beginning early in the project and continuing throughout.
  • Flat-hierarchical
  • Dictative
  • Controlled
  • Self-organized
  • 2
  • 5
  • 1
  • 7
  • Empirical Process Control
  • Collaboration
  • Value-based Prioritization
  • Self-organization
  • Daily Standup
  • Scrum of Scrums
  • Sprint Planning Meeting
  • Sprint Review
  • Planning Poker.
  • Release Planning Schedule.
  • Estimate Tasks.
  • Sprint Retrospect Meeting.
  • This principle describes how time is considered a limiting constraint in Scrum, and used to help effectively manage project planning and execution. Time-boxed elements in Scrum include Sprints, Daily Standup Meetings, Sprint Planning Meetings, and Sprint Review Meetings
  • This principle focuses on today’s workers, who deliver significantly greater value when encouraged to self-organize rather than be subject to the command and control style of traditional project management.
  • This principle focuses on the three core dimensions related to collaborative work: awareness, articulation, and appropriation. It also advocates project management as a shared value-creation process with teams working and interacting together to deliver the greatest value
  • This principle highlights the focus of Scrum to deliver maximum business value, beginning early in the project and continuing throughout.
  • Iterative product development
  • Customer value-based prioritization
  • Time-boxing
  • High velocity
  • Stakeholder
  • Chief Product Owner
  • Chief Scrum Master
  • Scrum Master
  • Autocratic
  • Decentralized
  • Persuasive
  • Paternalistic
  • Product Backlog
  • Project Vision statement
  • Business case
  • Acceptance criteria
  • Collaborative
  • Command and control
  • Transactional
  • Transformational
  • A Scrum team generally has 6-10 members.
  • A Scrum Team should be in place before the project is initiated.
  • A Scrum Team will create the deliverables of the project.
  • Length of the Sprint will be agreed between the Product Owner and the Scrum Team.
  • Initiate
  • Organization
  • Scope
  • Plan
  • Release
  • Business Justification
  • Create Deliverables
  • Delegate Responsibilities
  • Create Sprint Backlog
  • Business Justification
  • Review and Retrospect
  • Value-based Prioritization
  • A collaborative enterprise to either create new products or services or to deliver results as defined in the Project Vision Statement.
  • A group of related projects, with the objective to deliver business outcomes as defined in the Program Vision Statement.
  • A collaborative enterprise to sustain the improvements introduced in the operations of an organization.
  • A group of related programs, with the objective to deliver business outcomes as defined in the Portfolio Vision Statement.
  • Release
  • Starting up
  • Delivering
  • Monitoring
  • It makes projects adaptable and open to incorporating change.
  • It minimizes non-essential work and leads to higher efficiency levels.
  • It leads to greater levels of motivation among employees.
  • It ensures that all the benefits are delivered at the end of the project.
  • Retrospect Sprint Meeting
  • Daily Standup Meeting
  • Project Vision Meeting
  • Sprint Review Meeting
  • Product Backlog
  • Acceptance criteria
  • Project Vision Statement
  • Roles and Responsibilities
  • Product Owner
  • Customer
  • Scrum Team
  • Scrum Master
  • Focuses on detailed upfront project planning.
  • Allows Scrum Teams to take ownership of tasks.
  • Enables delegation of authority from one level to another.
  • Emphasizes individual accountability rather than group accountability.
  • Sprint Review Meeting
  • Retrospect Sprint Meeting
  • Sprint Planning Meeting
  • Daily Standup Meeting
  • The pace at which the Scrum Team can work and sustain comfortably for an indefinite period of time.
  • The pace at which the Scrum Team converts User Stories into deliverables in a Sprint.
  • The pace at which the Scrum Team releases project deliverables.
  • The pace at which the Scrum Team can work and sustain comfortably in a set of Sprints leading to a product release.
  • Ensures that the highest value requirements of the customer are satisfied first as it works on the principle of value-based prioritization.
  • Leads to a high trust work environment ensuring low friction among employees as it promotes transparency and collaboration.
  • Leads to an innovative and creative work environment as it creates an environment of introspection, learning and adaptation.
  • Ensures that products are developed over an agreed period of time as it emphasizes detailed planning at the beginning of the project.
  • It enables detailed planning at the beginning of the project hence ensures that all the risks are identified and mitigated.
  • It provides complete control over the project to the Product Owner as he is responsible for all the product development activities in a Sprint.
  • It is based on the principle value-based prioritization thus ensures that highest value is provided in the shortest period possible.
  • It is based on the principle of managing by stages thus ensures that all the expected benefits are realized at the end of the project.
  • Create Project Vision process
  • Develop Epics process
  • Retrospect Sprint process
  • Conduct and Coordinate Sprints
  • Projects with fixed scope and timelines.
  • Projects with changing requirements.
  • Projects with stable requirements.
  • Projects with defined roles and responsibilities.
  • Scrum ensures an open work environment through information radiators such as Scrumboard.
  • Scrum ensures faster resolution to issues through collaboration and colocation of development teams.
  • Scrum ensures a customer-oriented framework through collaborative approach and emphasis on business value.
  • Scrum ensures better coordination among teams through an hierarchical organization structure which delegates authority for all the project aspects from higher level to the lower.
  • Empirical Process Control
  • Value-based prioritization
  • Self-organization
  • Collaboration
  • It refers to emphasizing achieving results by focusing on the needs of the Scrum Team.
  • It refers to delivering maximum business value in a minimum time span.
  • It refers to prioritizing creation of high value deliverables over lower value deliverables
  • It refers to allowing all facets of Scrum process to be observed by everyone.
  • It refers to emphasizing achieving results by focusing on the needs of the Scrum Team.
  • It refers to making improvements through adaptation.
  • It refers to prioritizing creation of high value deliverables over lower value deliverables
  • It refers to allowing all facets of Scrum process to be observed by everyone.
  • It refers to emphasizing achieving results by focusing on the needs of the Scrum Team.
  • It refers to delivering maximum business value in a minimum time span.
  • It refers to prioritizing creation of high value deliverables over lower value deliverables
  • It refers to fixing a certain amount of time for each process and activity in a Scrum project.
  • It refers to using more than one product development cycle to develop the final project deliverables through the learning from the previous development cycles.
  • It refers to developing the final project deliverables in one product development cycle.
  • It refers to developing project deliverables using automated processes.
  • It refers to developing project outputs through detailed upfront planning with emphasis on fixing scope, quality and other project aspects.
  • It refers to individual Scrum Team members being aware of each other’s work.
  • It refers to the Scrum Core Team working together and interfacing with the stakeholders to create and validate the deliverables of the project to meet the stated goals.
  • It refers to achieving results by focusing on the needs of the Scrum Team.
  • It refers to proposes fixing a certain amount of time for each process and activity in a Scrum project.
  • Self-motivation and team responsibility.
  • Delegation of authority through proper planning.
  • Individual responsibilities and accountability.
  • Extensive upfront planning and adherence to the approved plans.
  • 1. Authoritarian.    Between 1 and 2
  • 2. Decentralized
  • 3. Persuasive
  • 4. Assertive
  • Daily Standup Meeting
  • Sprint Planning Meeting
  • Retrospect Project Meeting
  • Retrospect Sprint Meeting
  • It proposes fixing certain timeframe for each activity.
  • It ensures that Scrum Team members do not take up too much or too little work for a particular period of time.
  • It is a principle through which Scrum framework addresses the project constraint of ‘time’.
  • It ensures that there is detailed upfront planning before every Sprint begins.
  • Scrum ensures that the project has an open Prioritized Product Backlog with prioritized User Stories that can be viewed by everyone, both within and outside the Scrum Team.
  • Scrum ensures that there is clear visibility into the team’s progress through the use of a Scrumboard, Burndown Chart, and other information radiators.
  • Scrum ensures transparency through detailed upfront planning in which all the key stakeholders participate.
  • Scrum ensures transparency through a Project Vision Statement that is visible to all the internal and external stakeholders.
  • Storming: Team tries to accomplish work
  • Forming: Team is mature with experience
  • Norming: Team begins to sort out internal differences
  • Performing: Team’s efficiency is at its optimal level
  • Adaptation
  • Appropriation
  • Articulation
  • Awareness
  • Use of Scrumboard to ensure clear visibility into the Scrum Team’s progress.
  • Use of Release Planning Schedule to ensure coordination across multiple Scrum Teams.
  • Use of Prioritized Product Backlog to be viewed by internal and external stakeholders.
  • Use of fixed amount of time for each process and activity in a Scrum project.
  • Provides inputs to creation of Collaboration Plan.
  • Estimates User Stories approved by the Product Owner.
  • Prioritizes items in the Prioritized Product Backlog.  (Possible)
  • Develops Task List.
  • Determination of order and separation of what is done now from what is to be done later.
  • Use of information radiators to show the progress of the Scrum Team on completing the tasks in a Sprint.
  • Collection of feedback from the customer and other stakeholders to ensure continuous improvement.
  • Approval of completed deliverables after verification for compliance with Acceptance Criteria.
  • Determination of order and separation of what is done now from what is to be done later.
  • Use of information radiators to show the progress of the Scrum Team on completing the tasks in a Sprint.
  • Collection of feedback from the customer and other stakeholders to ensure continuous improvement.
  • Approval of completed deliverables after verification for compliance with Acceptance Criteria.
  • It results in low number of frictions among the Scrum Team members.
  • It facilitates formal and informal interaction among the team members.
  • It enables the team members to coordinate, resolve issues and learn from past experience.
  • It enables determination of the order and separation of what must be done now, from what needs to be done later in a Sprint.
  • Value-based Prioritization
  • Time-boxing
  • Stage-by-stage project delivery
  • Self-organization
  • Phase
  • Process
  • Stage
  • Sprint
  • Empirical Process Control, Self-organization, Collaboration, Value-based Prioritization, Time-boxing, Iterative Development
  • Empirical Process Control, Self-organization, Collaboration, Value-based Prioritization, Time-mapping, Iterative Development
  • Empirical Process Control, Self-organization, Collaboration, Cost-based Prioritization, Time-mapping, Iterative Development
  • Empirical Process Control, Self-organization, Collaboration, Cost-based Prioritization, Time-mapping, Cyclic Development
  • Autocratic
  • Decentralized
  • Persuasive
  • Paternalistic
  • Project Vision Statement.
  • Epic(s).
  • Prioritized Product Backlog.
  • Release Planning Schedule.
  • The Project Vision Statement can be accessed by all stakeholders and the Scrum Team.
  • The Prioritized Product Backlog with prioritized User Stories that can be viewed within and outside the Scrum Team.
  • The Release Planning Schedule can be coordinated with multiple Scrum Teams.
  • Burndown charts can be viewed only by the Scrum Team and the Scrum Master.
  • Product Owner
  • Scrum Master
  • Team manager
  • Scrum Team Member
  • Transparency
  • Inspection
  • Association
  • Adaptation
  • Release Planning
  • Sprint Planning
  • Retrospective Sprint
  • Project Vision
  • Empirical Process Control
  • Self-organization
  • Risk-based Prioritization
  • Collaboration
  • Program Product Owner
  • Chief Scrum Master
  • Scrum Master
  • Program Scrum Master
  • 1 – 4 members
  • 6 – 10 members
  • 15 – 20 members
  • Size of team depends on size and complexity of project
  • Process
  • Customer
  • Product
  • Project
  • Identify things that the team needs to keep doing that can serve as best practices.
  • Identify things the team needs to stop doing to process problems and bottlenecks.
  • Identify team members who were vital to the success of the Sprint.
  • Identify things that the team needs to begin doing.
  • Stakeholder
  • Chief Product Owner
  • Chief Scrum Master
  • Scrum Master
  • Risk-driven delivery
  • Value-driven delivery
  • Time-driven delivery
  • Change-drive delivery
  • A
  • A, C and D
  • A, B and C
  • A, B, C and D
  • Only experienced Scrum practitioners
  • Best suited for people with no prior experience or knowledge of Scrum or other project management methodology..
  • Neither experienced Scrum practitioners nor inexperienced people can use it.
  • Both experienced Scrum practitioners as well as people with no prior experience or knowledge of Scrum or other project management methods.
  • Plan conformity
  • Business value
  • Team performance
  • Attrition Level
  • Stakeholder Meeting
  • Daily Standup Meeting
  • Sprint Review Meeting
  • Retrospect Sprint Meeting
  • Prioritized Product Backlog Grooming
  • Sprint Review Meeting
  • Scrum of Scrums Meeting
  • Retrospect Sprint Meeting
  • Awareness, Articulation, and Appropriation.
  • Transparency, Precision, and Coordination.
  • Perfection, Cooperation, and Comprehension.
  • Honesty, Responsiveness, and Adaptability.
  • Product Owner
  • Scrum Team
  • Chief Scrum Master
  • Scrum Master
  • Awareness, Articulation, and Appropriation.
  • Aspects, Articulation, and Assurance.
  • Awareness, Adaptation, and Appropriation.
  • Aspects, Adaptation, and Artifacts.
  • Scrum Master
  • Product Owner
  • Chief Product Owner
  • Vendor
  • 8
  • 4
  • 5
  • 7
  • Initiate
  • Plan and Estimate
  • Implement
  • Review and Retrospect
  • Scrum Master
  • Scrum Team
  • Team Leader
  • Product Owner
  • Possibility and Impact
  • Probability and Impact
  • Change and Impact
  • Probability and Severity
  • Time-Boxing
  • Collaboration
  • Value-based Prioritization
  • Self-organization
  • Conduct Daily Standup
  • Ship Deliverables
  • Groom Prioritized Product Backlog
  • Retrospect Sprint
  • Conduct Daily Standup
  • Create Project Vision
  • Create Deliverables
  • Groom Prioritized Product Backlog
  • Product Owner
  • Scrum Master
  • Stakeholder
  • Scrum Team
  • Scrum Team
  • Scrum Master
  • Product Owner
  • Chief Scrum Master
  • Autocratic
  • Decentralized
  • Persuasive
  • Paternalistic
  • Time-Boxing
  • Iterative Development
  • Value-based Prioritization
  • Self-organization
  • Vendor
  • Chief Product Owner
  • Scrum Guidance Body
  • Stakeholders
  • This principle describes how time is considered a limiting constraint in Scrum, and used to help effectively manage project planning and execution. Time-boxed elements in Scrum include Sprints, Daily Standup Meetings, Sprint Planning Meetings, and Sprint Review Meetings
  • This principle focuses on today’s workers, who deliver significantly greater value when encouraged to self-organize rather than be subject to the command and control style of traditional project management.
  • This principle focuses on the three core dimensions related to collaborative work: awareness, articulation, and appropriation. It also advocates project management as a shared value-creation process with teams working and interacting together to deliver the greatest value
  • This principle highlights the focus of Scrum to deliver maximum business value, beginning early in the project and continuing throughout.
  • Prioritized delivery: Focus only on business value.
  • Appropriation: Adapting technology to one’s own situation.
  • Adaptation: Risk identification is performed and iterated throughout the project.
  • Collaboration: Stakeholders and development team interact continually.
  • Sprint Burndown chart
  • Project Vision statement
  • Product Backlog
  • Scrumboard
  • A, B and C
  • A, C and D
  • A, B, C and D
  • Only A
  • It results in low number of frictions among the Scrum Team members.
  • It facilitates formal and informal interaction among the team members.
  • It enables the team members to coordinate, resolve issues and learn from past experience.
  • It enables determination of the order and separation of what must be done now, from what needs to be done later in a Sprint.
  • Value-based Prioritization
  • Time-boxing
  • Stage-by-stage project delivery
  • Self-organization

About Clear My Certification

Check Also

Automated Testing Professional Certification

Automated Testing Professional Certification

Automated Testing Certification : CLICK HERE Earn your Automated Testing Certification and validate your expertise …

No comments

  1. where’s the link for this course? TQ.

Leave a Reply

Your email address will not be published. Required fields are marked *