Disciplined Agile Scrum Master (DASM)
Course length: 14 hours
Prerequisites: No experience needed
PMI Exam Fee: One Attempt Included
PMI Assigned CEU Claim Code: 4951GTF23M
For endeavors desiring true Business Agility , the Disciplined Agile Scrum Master (DASM) is a Servant Leader for the Organization, Product Owner, and Team. A DASM has a unique Field Manual elaborating hundreds of good practices. Unlike prescriptive players, the DASM leverages the wisdom of teams. The DASM plays a collaborative game, driving Guided Continuous Improvement (GCI) 'with' the team.
Course Benefits
- On-Line Practice Exam
- One Free Certification Exam voucher ($150 USD value) to be taken within 60 days of course completion.
- A copy of Disciplined Agile Choose your WoW Book
- Guerrilla Project Management value added materials: Miro Boards, Power Points, Adaptive Flashcards, On-Line Practice Exam
- Instructor is active lean agile practitioner at scale at one of world's top ten software engineering companies using: SAFe, DA, Dev Ops, Kanban, Scrum
- Earn 14 PDUs, eligible in Technical (7) and Leadership (7) categories.
PMI Continuing Education Units (CEU) and Professional Development Units (PDU)
- Earn: 14 CEU needed for DASM
- Earn: PDUs - Technical (7) and Leadership (7) categories. Apply 7 Technical PDUs to: PMP, PgMP, PfMP, PMI-PBA, PMI-ACP, and/or CAPM
Learning Objectives
Improve Organizational Culture by Apply the Disciplined Agile Mindset
- Inspire and Lead Organizations with the DA Mindset
- Describe what Disciplined Agile is
- Define the principles of DA
- Describe the promises of DA
- Describe the guidelines of DA
- Describe how DA is an agnostic hybrid of approaches that leverages strategies from a variety of sources.
Foster Business Agility in Organizations to Compete and to Improve Customer Value
- Understand the core value proposition of Disciplined Agile
- Define Business Agility
- Identify the full value of Business Agility
Improve Upon and Outperform Other Agile Frameworks
- Define the eight DA principles and how they are core to what sets Disciplined Agile apart from other agile frameworks
- Recognize the importance of making 'Delighted Customers' a priority
- Describe how 'Being Awesome' is important for building a great agile team
- List the 5 levels of awareness (Enterprise Awareness)
- Identify how different contexts require different strategies – teams need to be able to own their own process and to experiment to discover what works in practice for them given the situation that they face. (Choice is Good)
- Identify how DA provides guardrails helping you to make better process choices
- Avoid dogma and strict rules that may not even be applicable given the context that you face. (Pragmatism Over Purism)
- Identify the potential factors to consider regarding the context of a given situation faced by a team. (Context Counts)
- Appropriately use some of the large number of strategies the DA toolkit supports to Optimize Flow.
- Explain the importance of organizing around products/services
Tailor Organization's Best-In-Class Way of Working (Scrum, Kanban, Dev Ops, Scaled Agile)
- Determine to which situation each of the DA life cycles (Agile, Lean, Serial, Continuous, Exploratory, or Program) is best applied
- Describe how DA supports a variety of lifecycles
- Identify the phases of the DAD delivery cycle
- Describe the Agile life cycle and identify when to use
- Describe the Lean life cycle and identify when to use
- Describe the continuous delivery Agile life cycle and identify when to use
- Describe the continuous delivery Lean life cycle and identify when to use
- Describe the exploratory life cycle and identify when to use
- Describe the program life cycle and identify when to use
- Identify who, when, and how to choose a life cycle and who chooses
Create Autonomy, Mastery, and Purpose to Unlock Intrinsic Motivation for Employee Productivity, Growth, and Retention
- Apply the DA Practice of choosing a team's way of working (WoW)
- Execute the 5 steps for choosing your WoW
- Analyze a team’s context using the Disciplined Agile Context Radar Diagram
- List factors impacting context when choosing a team's WoW
- Select best-fit life cycle using the decision tree
- Master the foundations of Agile
- Compare and contrast agile and waterfall benefits and detriments
- Communicate the agile iterative way of working
- Define and deploy the artifacts and ceremonies of agile
- Explain how people are organized into DA teams
- Compare and contrast leaders to managers
- Inspire various roles to be leaders
- Describe potential, primary and secondary roles on DA teams
- Define the primary DA roles and how they each are key to the success of a self-organizing agile team
- Describe the 5 Primary DA roles and their purpose
- Describe the responsibilities of the 5 primary DA roles
- Describe why each of the 5 primary DA roles is important
- Help your team work well together (Lean principle “Respect people”)
- Motivate the team, use effective conflict resolution and communication methods, sense and respond to team emotions, demonstrate how to keep options open during brainstorming sessions, and articulate respect
Respect That It's Fine to Fail Fast, but also Much Better to Succeed Sooner
- Understand the Disciplined Agile body of knowledge
- Use Kaizen loops and PDSA techniques for continuous improvement
- Define the options for cross-team learning: "community of practice" and "center of excellence"
- Use the DA tool kit to tailor your way of working according to context
- Explain The Process Blades' Flow, Goals, Decision Points, Options, and Option Tables
- Describe the process goals of DAD
- Use the 800+ Options in the DAD Process Blade to tailor and optimize team performance
- Explain what it means to be goal driven
- Define process blade and how process blades are used inside DA
- Describe the purpose of a goal diagram
- Describe how to read a goal diagram
- Rank and select process goals according to their relevance to the phase and the team’s context
- Identify key practices for the team try using goal diagrams
Optimize Good Practices to Start, Build, Productionize, and Continuously Improve Organizations Delivering Products and Services
- Define Inception, describe the inception phase and why it is important
- Identify the process goals associated with the Inception phase
- Describe Agile techniques and ceremonies relevant to Inception
- Define user stories
- Describe how to write and estimate a user story using different techniques
- Identify acceptance criteria and the definition of done
- Indicate how to effectively plan iterations
- Define Construction, describe the Construction phase and why it is important.
- Identify process goals associated with the Construction phase
- Describe Agile techniques and ceremonies that take place during Construction
- Describe how to demonstrate an iteration
- Understand how to obtain and receive feedback
- Define Transition, Describe the Transition phase and why it is important.
- Identify process goals associated with the Transition phase
- Define Ongoing phase, describe the Ongoing phase and why it is important.
- Identify process goals associated with the Ongoing phase
- Optimize Organizational Performance with Ongoing Process Goals
- Discuss how to use the DA tool kit to tailor your way of working within all phases according to context
- Identify possibilities, 'the good and bad', of 800+ key practices for the team using goal diagrams
- Use the DA tool kit to tailor your way of working within a select phase according to context by identifying key practices for the team try using goal diagrams
Delight Customers, Reduce Cost, and Increase Value with Lean Thinking
- Explain how to Eliminate Waste and Build Quality In (Lean principles)
- Identify the causes of waste and delays
- Describe how to minimize waste through value stream mapping
- Describe the push and pull methods of moving work
- Describe the Kanban approach to managing work in process
- Explain how to build and validate quality into the delivery process
- Explain how to Deliver Value Quickly (Lean principle)
- Explain cost of delay
- Describe how to realize value
- Explain the importance of delivering incrementally
- Contrast Minimum Business Increment(MBI) with Minimum Viable Product (MVP)
- Explain how to Learn Pragmatically (Lean principle)
- Define “standard work” and its use as a baseline for continuous improvement
- Explain the benefits of explicit workflow
- List and define the principles of Lean
- Become Enterprise Aware beyond the team view with a Lean Systems View
- Contrast Lean aspects of knowledge work with work in the real world, including sources of waste and delay
- Describe aspects of regular work that affect quality and efficiency, including sources of waste and ways to improve
- Recognize the value of resilient Process, People and Technology
- Describe how resiliency supports lean thinking
- Explain when to build workflow according to resiliency outcomes