Digital Marketing

Categories

 

 

Request More Info

Seeking details for:

Myself
My team/Organization
Corporate/Customized Training

PeopleCert SCRUM Master I

Scrum is a framework that helps teams work together. It increases team productivity by encouraging team players to learn through experiences, self-organise, and continuously improve. IT teams use Scrum to develop, deliver, and maintain complex software products. However, Scrum principles can be applied to all kinds of areas: Research, Sales, Marketing, and Customer support - to name a few.

How does Scrum work? Based on Agile principles, it enables teams to self-organise by encouraging close collaboration between all team members and specialisms involved. Scrum challenges the assumptions of the sequential approach to Product development and replaces it with an Iterative process. It includes a set of meetings, tools, and roles that work in harmony to help teams structure and manage their work.The goal of this approach is to timely capture changes in customers' needs, along with any other unpredictable challenges that may occur — for which a sequential approach is not suted. As such, Scrum uses an evidence-based framework that embraces the fact that problems cannot be fully defined upfront. Instead, it focuses on maximising the team's ability to respond to emerging requirements, deliver value quickly, and adapt to new market conditions. 

Why is it important to hold a Scrum certification? Holding a Scrum certification proves the candidate's familiarity with Scrum practices, beyond the mere knowledge of terminology. It shows to employers that the candidate has the potential to be the person they need to cover the Scrum Master role in their teams. Whether the candidate is a Scrum beginner or a seasoned professional, a certification a significant advantage when aiming to motivate and lead teammates.

Program Outline

1

Introduction to Agile Project

Management

1.1 What Is Agile?

1.1.1

Define the term Agile

 

 

1.1.2

Identify key terms used to describe Agile approaches, like predictive;

iterative; incremental; and adaptive

 

1.2 Agile Values and Principles

1.2.1

Define the Agile Manifesto and explain its purpose

 

 

1.2.2

Describe the purpose of the four values of the Agile Manifesto

 

 

1.2.3

Describe the purpose of the 12 principles of the Agile Manifesto

2 Scrum as an Agile Framework

2.1 What Is Scrum?

2.1.1

Define the term Scrum

 

2.1.2

Describe the purpose of Scrum

 

 

 

2.1.3

Describe the benefits of Scrum in

relation to the common challenges faced by IT

 

2.2 The Three Pillars of Scrum

2.2.1

Know that Scrum is founded on empirical process control

 

2.2.2

Define the three pillars of Scrum: inspection; adaptation; and transparency

 

 

2.2.3

Explain the purpose of the three pillars of Scrum

 

2.3 Scrum Values

2.3.1

List the five Scrum values: commitment;    focus;  openness;

respect; and courage

 

 

 

 

 

 

3 The Scrum Framework & Team

 

2.3.2

Identify examples for each of the five Scrum values

 

2.3.3

Explain the purpose of the five Scrum values and their interaction

with the Scrum Team

3.1 The Scrum Framework

3.1.1

List the Scrum main practices: roles, events, artifacts and rules

 

 

 

 

3.1.2

Identify the purpose of the Scrum Practices

 

3.1.3

Define the main Scrum roles:

Product Owner, Development Team, Scrum Master

 

 

3.1.4

Define artifact and the main Scrum artifacts: Product Backlog, Sprint

Backlog, Product Increment

 

 

3.1.5

Define the terms Timeboxing Sprint and the main Scrum events: Sprint Planning, Sprint Execution, Daily Scrum, Sprint Review, Sprint

Retrospective

 

 

3.1.6

List the 13 Scrum rules

 

3.2 Roles

3.2.1

Know that the Scrum Team consists of a Product Owner, the development team, and a Scrum

Master

 

 

3.2.2

Describe the impacts of people performing multiple Scrum roles

3.3 Teams

3.3.1

Define the term self-organizing team

 

 

 

3.3.2

Describe the characteristics of a selforganizing team

 

 

3.3.3

Define the term cross-functional team

 

 

3.3.4

Describe the characteristics of a cross-functional team

 

3.4 The Product Owner Role

3.4.1

Describe the characteristics of an effective Product Owner

 

 

3.4.2

Identify the responsibilities and accountabilities of the Product

Owner within Scrum

3.5 The

Development Team Role

3.5.1

Describe the characteristics of an effective Development Team

 

3.5.2

Identify the   responsibilities   and

accountabilities of the Development Team within Scrum

 

 

3.5.3

Know the ideal Development Team Size

3.6 The Scrum Master Role

3.6.1

Describe the characteristics of an effective Scrum Master

 

 

3.6.2

Identify the responsibilities and accountabilities of the Scrum Master

within Scrum

 

 

3.6.3

Define the term Servant Leadership

 

 

 

 

3.6.4

List the characteristics of a successful servant leader

 

 

3.6.5

List the ways that a Scrum Master serves the Product Owner

 

 

3.6.6

List the ways that a Scrum Master serves the Development team

 

3.6.7

List the ways that a Scrum Master serves the organization

 

3.7 Technical Debt

3.7.1

Define the term technical debt and its impact

 

 

3.7.2

Describe the types, the causes and consequences of Technical Debt

4 Scrum Artifacts

4.1 Product Backlog

4.1.1

Identify the attributes of a product backlog

 

 

4.1.2

Describe the purpose of the product backlog in Scrum and who is responsible for its development and

maintenance

 

 

 

4.1.3

Explain how the product backlog can evolve as the product and

environment evolves

 

4.1.4

Define the terms product backlog item (PBI), requirements statement, acceptance criteria, increment, and

conditions of satisfaction.

 

 

4.1.5

Define the term Product Backlog Grooming

 

 

4.1.6

Define the terms "epic", "feature" "user story", "story points" in relation the PBIs, during product

backlog grooming.

 

4.1.7

Identify the purpose and process steps involved in the product backlog grooming in Scrum including the roles of the Scrum

team

 

4.2 Sprint

Backlog

4.2.1

Describe the purpose of a sprint backlog in Scrum

 

4.2.2

Identify the attributes of a sprint backlog, how it can be altered and which role may perform any

alterations

 

4.3 Product Increment

4.3.1

Define the term product increment

 

 

4.3.2

Define the potentially shippable

product and describe its purpose in Scrum

 

 

4.3.3

Define the terms conditions of

satisfaction, definition of done, and definition of ready

 

 

 

 

4.3.4

Differentiate between the definition of done (DoD) and acceptance

 

 

4.3.5

Define the term "velocity" identify estimation techniques used to

calculate velocity and its purpose

 

 

4.3.6

List practices that will help Scrum teams deliver a high-quality product increment and reduce technical debt.

 

4.4 Artifact Transparency

4.4.1

Explain the importance of artifact transparency

 

4.4.2

Describe the impact of artifacts that are not fully transparent

 

 

 

4.4.3

Identify examples of how transparency must be inspected, adapted and increased at the Scrum

events

5 Scrum Planning

5.1 Multilevel Planning

5.1.1

Define multilevel planning and explain how multilevel planning helps teams

 

 

5.1.2

Describe the concept of the planning onion and list the six planning levels (day, iteration, release, product,

portfolio, strategy)

 

5.2 Release Planning

5.2.1

Define Release backlog, Release Planning and describe its goal

 

 

5.2.2

Identify the timing, participants, and process steps involved in the release

backlog

 

5.2.3

Define "fixed-scope release" and "fixed-date release".

6 Scrum Events

6.1 Sprint Planning

6.1.1

Describe the purpose of the sprint planning event

 

 

6.1.2

Identify the process steps involved in the sprint planning event including the roles and responsibilities of the

Scrum team

 

6.1.3

Identify the correct length of time for a sprint.

 

 

6.1.4

Define the term "capacity" in relation to sprint planning including the various factors that influence a

team's capacity.

 

6.2 Sprint

Execution

6.2.1

Describe the purpose of the sprint execution event

 

 

6.2.2

Identify the process steps involved in the sprint execution event including the roles and responsibilities of the

Scrum team

 

 

 

6.3 Daily Scrum

6.3.1

Describe the purpose of the daily scrum event

 

 

6.3.2

Identify the process steps involved in the daily scrum event including the roles and responsibilities of the

Scrum team

 

 

6.3.3

Identify the attributes of an effective daily Scrum meeting.

 

6.4 Sprint Review

6.4.1

Describe the purpose of the sprint review event

 

 

 

6.4.2

Identify the process steps involved in the sprint review event including the roles and responsibilities of the Scrum

team

 

6.4.3

Describe the outcomes of a Sprint Review

 

6.5 Sprint

Retrospective

6.5.1

Describe the purpose of the sprint retrospective event

 

 

6.5.2

Identify the process steps involved in the sprint retrospective event including the roles and

responsibilities of the Scrum team

7 Information Radiators

7.1 Types of Information Radiators

7.1.1

Define the term "information radiator" explain the purpose, and provide examples of information

radiators

 

7.1.2

List the Types Information Radiators

 

7.2 Purposes of Information Radiators

7.2.1

Define sprint backlog chart, Product Backlog chart, Burn-down/Burnup chart and burnup chart and explain

the purpose of each.

 

 

7.2.2

Describe the purpose of visual management tools in relation to Scrum and identify the attributes of effective visual management tools, including kanban charts and task boards, and explain the benefits of

each

8 Scaled Scrum

8.1 The Purpose of Scaling Scrum

8.1.1

Define the term Scaled Scrum

 

8.1.2

Describe the purpose and goal of scaling Scrum

 

8.2 Roles in Scaling Scrum

8.2.1

Know the roles in Scaled Scrum

 

8.2.2

List the main responsibilities of the Chief Scrum Master in Scaled Scrum

 

8.3. Scaled

Artifacts and Events

8.3.1

Describe how to scale the product backlog

 

 

 

 

8.3.2

Identify the reasons of a consistent definition of done across multiple teams working on the same product

log

 

     

     

    Request More Info

    Seeking details for:

    Myself
    My team/Organization

    SCRUM Master I Certification Benefits

    • Makes you aware of the Best Practices in Agile Project Management
    • Act as Qualification/ Disqualification Criteria for Top Paying Agile Project Management Jobs in the UK and Europe
    • Recognizes your Knowledge, Skills, and Abilities Globally
    • Lead to Career Opportunities and Advancement
    • Increases Chances of Getting Better Jobs at the Mid/Senior Level
    • Contribute towards Enhancing/ Improving organizational Agile project management processes.
    • Shows your commitment to the Agile Project Management profession

    How to become SCRUM Master I Certified?

    • Meet the Qualifying Criteria
    • Undertake training based on Latest SCRUM Master I Manual
    • Attend 3 Days of Training
    • Attempt SCRUM Master I Certification Exam on the 3rd Day

    What Can KnowledgeWoods Do for You?

    • Assess Participant's Profile
    • Provide a Road Map for SCRUM Master I Certification
    • Share Details about Costs associated with the SCRUM Master I Exam.
    • Query Handling Facility over E-mail
    • SCRUM Master I Exam Mock Questions
    • Customer Support over E-mail