Speak to an advisor602-266-6630

Scrum Master and Agile Training

Scrum is the most popular Agile framework. It is an adaptive, iterative, fast, flexible, and effective methodology designed to deliver significant value quickly and throughout a project.

Scrum ensures transparency in communication and creates an environment of collective accountability and continuous progress. The Scrum framework, as defined in the SBOK™ Guide, is structured in such a way that it supports product and service development in all types of industries and in any type of project, irrespective of its complexity.

Available delivery through our “Live Remote” platform!

speak to an advisor
Add To Cart

About this Course

Students will acquire the knowledge to pass the ScrumStudy national certifications exams in both Scrum Master and Agile.  Students will study from training material developed through ScrumStudy, and learn to facilitate a product development team using Agile software development.  Completion requirements:  48 hours of training, completing weekly assignments, weekly quizzes, and passing your final exam with an 80% or better.

Course Syllabus

Scrum Master with Agile

Week 1

Intro to Agile

    1. What is Agile – Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.
    2. Methodologies (list)
      • SCRUM, Feature Driven Development, Extreme Programing, Dynamic Systems Development Method
      • Core Values, Features & Roles of each
    3. Why Use Agile
      • Revenue
      • Speed to market
      • Quality
      • Visibility
      • Risk Management
      • Flexibility
      • Cost Control
    1. Agile Manifesto
  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan
    1. Agile Principles
  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  • Business people and developers must work together daily throughout the project.
  • Build projects around motivated individuals.
    Give them the environment and support they need, and trust them to get the job done.
  • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  • Working software is the primary measure of progress.
  • Agile processes promote sustainable development.  The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  • Continuous attention to technical excellence and good design enhances agility.
  • Simplicity–the art of maximizing the amount of work not done–is essential.
  • The best architectures, requirements, and designs emerge from self-organizing teams.
  • At regular intervals, the team reflects on how  to become more effective, then tunes and adjusts its behavior accordingly

Day 2

  1. Breakdown of the different Methodologies & how they compare or contrast to each other
      • Comparing Agile to Waterfall
      • Lean
      • Kanban
      • XP -(Xtreme Programming)
      • DSDM – Dynamic systems development method
      • SCRUM – Term from Rugby

Day 3

  1. Continue Breakdown of the different Methodologies & how they compare or contrast to each other
      • FDD – (Feature Driven Development)
      • Crystal
  2. Agile Tools
      • Burn-down Chart
      • Burn-up chart
      • Return on investment (ROI)
  3. Review
  4. Quiz on Agile

WEEK 2

Day 1

SCRUM

  1. Intro to Scrum
    • What is Scrum
    • Why is it called Scrum
    • Waterfall vs Scrum
    • Applicable for:
      • Developing cutting-edge products, Frequently changing requirements, Volatile & hypercompetitive markets
  2. Scrum Advantages:
      • Adaptability, Transparency, Continuous Feedback, Continuous improvement, Continuous Delivery of value, Sustainable Pace, Early Delivery of High Value, Efficient Development Process, Faster resolution of problems, Customer Centric, Collective ownership, High Velocity
  3. Scrum Principles
    • Empirical Process Control, Self-organization, Collaboration, Value-based Prioritization, Time-boxed, Iterative Development
  4. Scrum Aspects
    • Organization, Business Justification, Quality, Change, Risk

Day 2

  1. Scrum Project phases
    • Initiate, Plan & Estimate, Implement, Review & Retrospect, Release
  2. Scrum 5 Phases and 19 Processes
    • Initiate Processes: Create Project Vision, Identify Scrum Master & Stakeholders, Form Scrum Team, Develop Epics, Create Prioritized Product Backlog, Conduct Release Planning
    • Plan & Estimating:  Create User Stories, Approve, Estimate & Commit User Stories, Create tasks, Estimate tasks, Create Sprint backlog
    • Implement: Create Deliverables, Conduct Daily Standup, Groom Prioritized Product Backlog
    • Review & Retrospect: Convene Scrum of Scrums, Demonstrate & Validate Sprint, Retrospect Sprint
    • Release: Ship Deliverables, Retrospect Project

Have the Veteran or eligible person recreate the 5 Phases, and the 19 processes on a blank sheet ( very important that they know the  5 phases and 19 processes.

Day 3

  1. What is happening during each of these 19 processes
    • Go in-depth as to what is happening during each of these processes
  2. Scrum Roles in depth
    • Core Role: Product Owner, Scrum Master, Scrum Team
    • Non-core Roles

WEEK 3

Day 1

  1. Important Definitions and their meanings:
    • Sprint – An iteration of work during which an increment of product functionality is implemented. By the book, an iteration lasts 30 days
    • Prioritized Product Backlog – is the requirements for a system, expressed as a prioritized list of product backlog Items
    • Sprint Planning Meeting – backlog items are moved from the product backlog into a sprint, based on the product owner’s priorities.
    • Daily Scrums – A fifteen-minute daily meeting for each team member to answer three questions:
  2. “What have I done since the last Scrum meeting? (i.e. yesterday)”
  3. “What will I do before the next Scrum meeting? (i.e. today)”
  4. “What prevents me from performing my work as efficiently as possible?”

The Scrum Master ensures that participants call sidebar meetings for any discussions that go too far outside these constraints.

The Scrum literature recommends that this meeting take place first thing in the morning, as soon as all team members arrive.

    • Sprint Backlog – Defines the work for a sprint, represented by the set of tasks that must be completed to realize the sprint’s goals, and selected set of product backlog items
    • Time-boxing – Time is treated as a limiting constraint, and Time-boxing is used as the rhythm to which all stakeholders work and contribute
    • Velocity – measure of efficiency in terms of how much work they can complete  over a certain period of time
  1. Quiz

Day 2

  1. Scrum Stages:
      • Vision, Product Roadmap, Release Planning, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospect
  2. Initiation Phase
    • Create Project Vision, Identify Scrum Master & Stakeholders, Form Scrum Team, Develop Epics, Create Prioritized Product Backlog, Conduct Release Planning
  3. Plan & Estimate Phase
    • Create User Stories, Approve, Estimate & Commit User Stories, Create tasks, Estimate tasks, Create Sprint backlog

Day 3

  1. Implementation & Estimate Phase
    • Create Deliverables, Conduct Daily Standup, Groom Prioritized Product Backlog
  2. Review & Retrospect Phase
    • Convene Scrum of Scrums, Demonstrate & Validate Sprint, Retrospect Sprint
  3. Release Phase
    • Ship Deliverables, Retrospect Project

Outline of a walk thru a Scrum process from beginning to end how will be responsible for what in our next class and what we are trying to accomplish.

  1. Quiz

Week 4

Day 1

  1. Complete walk through of the Scrum process with veteran or eligible person going through the motions of Scrum Process from start to finish.
  2. Review what we learned and go over any questions
  3. Start of Scrum Project

Day 2

  1. Finish Scrum Project
  2. Case Study

Day 3

Answer any course material questions, questions about the exam or any other questions.

  1. Follow-up & Review the material from the beginning and leave plenty of time for the classes final exam
  2. Final Exam