This 3 day Instructor led class covers everything you’d find in a certified Scrum Master course but takes a deeper dive and allows even more hands on lab time.  After a one day overview of Scrum, students will have an opportunity to practice what they’ve learned with two days of intensive lab work.

Training Outline

Day One

• Agile Overview
  • The Agile Potential
  • The Agile Manifesto
  • Agile alone is NOT enough
  • Can Agile fail?
  • THE Best Agile
• SCRUM Overview
  • Stories -Making It Manageable
    • Stories
    • Why Object Oriented Principles Are Critical To Agile
    • Sprint Planning Meeting
    • Just Enough…and no more
    • Controlling Chaos
  • Sprint
    • Creating a Sense Of Urgency
    • Driving Your Project
    • Conducting the Daily Scrum
    • Chickens and Pigs
    • Life Is …Daily!
    • Doing Iterative Development
    • Design
    • Test
    • Code
    • Refactor
    • Sprint Review Meeting
• LAB – Scrum Practices
  • Deliverable will be poster/presentation (group may or may not be called on) that communicated key elements of Scrum
• Product Owner: Roles and Responsibilities
  • Requirements and the Product Backlog
    • Building a Product Backlog
    • User Roles and Personas
    • Acceptance Criteria
    • Story Workshops
    • Story Aggregation and Decomposition
    • Spikes and Special Stories
    • LAB Identify and Define User Roles &: User Story Writing
• Prioritization
  • Value Assessment
  • Risk-Based Prioritization
  • LAB: Risk-Value Prioritization
• Estimation
  • Approaches to Estimation
  • Analogous Sizing
  • Planning Poker
  • LAB: Estimating with Planning Poker
• Planning
  • Product Roadmap
  • Velocity-Driven Release Planning
  • Fixed-Schedule Planning
  • LAB: Release Planning Exercise

• Lean Software Development
  • Lean Principles
    • Minimizing Waste
    • Maximizing Learning
    • Just in Time Delivery
    • Empowering The Team
    • Telling The Whole Truth

Day Two

• Lean Practices specific to software projects
  • Value Stream Mapping
  • Set Management – Backlog, Throughput, Expenses
  • Kanbans and Queues
  • Goals and Measurements
• LAB – Leveraging Lean Principles in Scrum
  • Deliverable will be collective ideas from each group and ROLE regarding when/how a lean principle could be used to support/replace a Scrum practice. NOTE: Criteria is that it must be real and practical for your job. We’re looking for implementation not theory.
• Using Scrum in a Big Way
• LAB – Big Scrum
  • PROJECT – Introduce Project that will be used for the remainder of course
  • Board meeting minutes provided to students
  • This is the big vision for the next 2 years
  • Event Management
  • Corporate Events
  • Sporting Events
  • Hotel Reservations
  • Car Reservations
  • Coordinated local events and shopping
  • Providing meals
  • Air Reservations
  • Shuttle Transportation
  • Accounts Payable (to pay vendors)
  • Online registration
  • Credit Card processing
  • Group Registrations
  • Accounts Payable System Rewrite
  • Currently on mainframe & we are losing the lease
  • Rewrite for Linux
    • Deliverable – Nothing at this time. Q&A and warm up time for students to start to absorb magnitude of project
• The RoadMap – overview
• LAB – RoadMap
• LAB – RoadMapDeliverable – Two year RoadMap. Students MUST ask questions or they will not be able to come to the right conclusions. The customer wants to be able to offer Online Registration, handle hotel and car rentals. High level stories/epics, estimates and prioritization are important here too.
• Release Planning
• Requirements Overview
• Use Cases
• User experience (sprint 0 – before UI development begins)
• User research
• Task analysis
• Storyboards and wireframes
• Apply visual design
• UX Lab
• Giving Up Hope/Change Happens
• Architectural changes
• Impact across components and product/project teams
• Very high level design discussion (for general team audience)
• Integration testing
• When and How
• LAB – Release Planning Part 1
  • Set up Giant Task Board for Product Release Planning (releases quarterly with 3 sprints per release)
• Deliverable – Task board set up and team able to
  explain how it will be used LAB – Release Planning Part 2
• Review

Day Three

• Layout stories/epics for next 12 months.
• Discuss strategies for handling inaccuracy / disagreement
• Deliverable – Task board with all stories in place
• Epics – Just Enough Planning and no more
• LAB – Release Planning Part 3
• Review Task board and make revisions where
  appropriate
• Are their epics/stories you missed
• Do you have the right amount of detail
• Deliverable – Product Backlog
• Practicing Scrum – Sprint Planning Meeting
• LAB – Sprint Planning Meeting
• Work with Product Owner
• Deliverable – Team goal for Sprint, Sprint
  Backlog, Sprint Review Date
• LAB – Daily Scrum
• Each team picks a facilitator who will play
  different roles as she/he reports at Daily Scrum.
• Deliverable – The rest of the team play the role of Scrum Master and has to note how they would handle each response.
• LAB – Sprint, Developing the Product
• Deliverable – Team will do high level class diagrams and other UML as needed to provide evidence that they understand and could build this software
• LAB – Sprint Review
• Deliverable – Team will present their COMPLETED
  work to the group
• Emphasis here is heavily on what “done” means!
• LAB – Sprint Retrospective
• Deliverable – Team will DOCUMENT the critical
  things they need to improve on.
• Turn in document to a company represent the top 3-5 five things your team thinks is most critical to the successful implementation of Agile in your workplace.
• Metrics and Measuring Progress
• Planning as you go Information Radiators – reviewed
• Velocity and Measuring progress – metrics
• SCRUM metrics
• LEAN metrics
• Even easier metrics
• Metrics Lab
• Watching The Horizon
• Final Review

To Hire an Agile Projects with Scrum / Lean Subject Matter Expert and Instructor who also teaches this class, call us today at 800-798-3901!