Dr. Roger’s Agile Video Select

Agile is easy to learn but hard to master. There are still blind spots that remain irrespective of how long you have been learning agility. Therefore, when I started working on CSM co-training with CST in 2019, I took on the challenge of translating Agile videos of different depths.

Original aspiration of translation

Agile is easy to learn but hard to master. There are still blind spots that remain irrespective of how long you have been learning agility. Therefore, when I started working on CSM co-training with CST in 2019, I took on the challenge of translating Agile videos of different depths.

The Agile videos I’ve selected usually hit the Agilist’s blind spots right off the bat, and often I’m enlightened after I finish the final translation. This is the way to practice Agile, and if the practice can also benefit many Agile learners in Taiwan, why not?

Reminder: Chinese subtitles will be automatically displayed on this webpage on both PCs and mobile phones; if not, please open the Chinese subtitles option at the bottom right corner.

Henrik Kniberg Video Series

1. Agile Product Ownership in a Nutshell 

  • his 15-minute animated video by Henrik Kniberg, CST, presents an in-depth introduction to the concept of Product Ownership in Agile development.
  • It provides a deep understanding of the responsibilities, details, and collaboration mechanisms of Agile members. The English version attracted over 2 million hits, making it one of the top ten Scrum classics
 

2. How Misconceptions About the Product Owner Role Harm Your Organization and What To Do About It 

  • This 15-minute animated video by Henrik Kniberg, the CST, presents an in-depth introduction to the concept of Product Ownership in Agile development.
  • It provides a deep understanding of the responsibilities, details, and collaboration mechanisms of Agile members. The English version attracted over 2 million hits, making it one of the top ten Scrum classics.


Lyssa Adkins Video Series

1. 5 min with Lyssa – Explaining Scrum to Managers

  • In this short 5-minute video, Lyssa Adkins describes how to explain “Why Scrum” to executives by answering the question in the inaugural issue of Agile Vox and uses Michael Spayd’s Integral Agile to demonstrate that it’s important to think about something not just from one perspective, but from four perspectives: It, I, It’s, and We, and to find the answer.

2. 5 minutes with Lyssa: Resistance to the agile coach

  • Lyssa Adkins answers some common questions from Agile practitioners by responding to a consulting letter from Eastern Europe, for example: Can an Agile coach or Scrum Masters be involved in the selection of team members?
  • What to do if an organization’s senior management doesn’t care for Agile? How to get the team to embrace Agile? With this short seven-minute video, Lyssa gives a quick overview of how to drive Agile.

3. How can I justify 2 roles for a Scrum Master & an Agile Coach?

  • Lyssa Adkins offers an open-ended conclusion on “How can I justify two roles for a Scrum Master & an Agile Coach”. Instead of providing answers, Lyssa offers us a direction.
  • She hopes that we can think about this question without being limited to various titles or roles, such as Agile Coach, Scrum Master, Program level manager, or multi-team. Rather, we need to clarify and map out what functions the people in these different titles or roles are responsible for and what the organization’s needs are to figure out what roles and functions we need truly.

4. How do I help a new agile team get started on the right foot?

  • By replying to Lesley Artyn Nolan’s question, Lyssa Adkins shows how to get your team working together well early on. Lyssa mentions some important ideas in the video. For example: when starting up a team, if they didn’t have a good start, it’s okay, you can always reset them
  • second, we need to focus on tasks ahead, rather than making people like or trust each other; third, the Scrum Master needs to know when to step into the team and when to step back.

5. The High Performance Tree

  • Lyssa Adkins illustrates how to build an Agile high-performance team using the metaphor of the high-performance tree. Lyssa begins the video with a metaphor that the five values of Scrum are the foundation of a high-performance team and that only when the foundation is firmly established can a team thrive.
  • In addition, she also mentions the characteristics of a high-performance team, such as self-organizing, motivated by trust, decision making, consensus-driven, and putting the team’s success above the success of the individual. These are the characteristics that agile practitioners can use to build their own high-performance teams.

6. The Scrum Framework

  • Lyssa is one of the world’s best Scrum trainers and a master at guiding and inspiring. In this video, Lyssa demonstrates how to teach a complete Scrum framework in just 10 minutes, covering Scrum roles, Sprint planning, review and retrospective, and some very practical concepts such as vision setting, prioritization, and continuous improvement.

7. The Wedding Cake

  • In this video, Lyssa Adkins, who excels at Agile teaching through metaphor, illustrates the differences between traditional Waterfall projects and Agile projects in terms of product production and value delivery using the “different ways to eat a wedding cake”.
  • She also mentions two important concepts of the Agile approach: 1. Prioritize the highest business value slices before proceeding, and 2. Identify when we’ve already gotten the value we need from the product. These concepts can also be used to improve the organization’s competitiveness.


Mark Shead Video Series

1.Agile And Remote Work

  • Agile says that the best way to communicate is face-to-face; however, working remotely (distributed work teams) (or as in the recent epidemic) makes face-to-face communication difficult to execute.
  • Based on his practical experience, the author shares how to achieve the effect of face-to-face communication in a second-best way through the use of video conferencing and instant messaging software.

2.Agile In Name Only

  • Through an interesting case of a one-hour dry cleaner, the author illustrates the misconceptions caused by having a name but no reality, having a name that does not live up to the truth or sailing under false colors.
  • At the end of the video, the author concludes with a sentence: No matter how great your name is, it is the execution that matters. It is hoped that everyone can be a veritable Agile practitioner.

3.Agile Transformation – Is that how you become Agile?

  • What are the elements of Agile transformations? How can you make your team become an Agile team? Check out this video that briefly introduces you to a few basic Agile principles and values and how to implement them.

4. Agile User Stories

  • User stories are the most common form of Agile considering the requirements from the customer’s perspective. Each user story can present a complete feature for independent use by the customer, which presents Who, What, and Why.
  • A good user story can effectively deliver value to customers on each Sprint. This video teaches you how to write a good user story.

5. Because Amazon – Making Agile Decisions (Cartoon)

  • Modeling of excellence has always been a shortcut to success for many people. With this video, we can rethink how to imitate intelligently and achieve success instead of imitating and copying comprehensively, regardless of the facts.

6. Splitting User Stories – Agile Practices

  • This video illustrates graphically how different the imaginary needs of users are from the development logic of programmers. Many Agile beginners always find it difficult to split user stories effectively.
  • Mark uses the musician’s compositions to explain the principle of Agile splitting-the 80/20 Rule, and uses website shopping to demonstrate how to split user stories.

7. Standup Meetings – What’s the Goal in Agile Teams?

  • What you don’t know is that in addition to the three standard questions in Agile daily standup meetings (What did you do yesterday? What will you do today?
  • Are there any impediments in your way?), teams can also set their own three questions to discuss each day (Scrum Guide 2017). So how to set them up? This video gives you a good answer.

8. Talk To Users – Agile Principle of Face-to-face Communication

  • Agile principles place great emphasis on communication. Smooth two-way communication between users and the development team is essential to successful Agile development.
  • This video gives us an insight into the disruptions caused by misunderstandings in communication.

9.What is Agile?

  • This animated video provides an accurate explanation of Agile development. The author shows what Agile is and is not in a lively way.
  • Through easy-to-understand examples, he introduces 4 Agile values and 12 Agile principles that shape the decisions of development teams to make better software development approaches during the software development process.

10.What is Agile Development Methodology? (hint Agile isn’t a methodology)

  • Agile is a collection of values and criteria that enable you to work more efficiently. The Agile development methodology is a system that makes the Agile mindset more concrete. If Agile is the root of the tree, the methodology is the branch.
  • To pursue perfection in methodology at the expense of the Agile spirit is actually to attend to trifles and neglect the essentials, a phenomenon that this video amusingly mocks

11. What is Agile Methodology? 

  • Agile has explicitly pointed out to avoid prescribing any particular method or procedure, but why does the term methodology still appear? Scrum, XP, and Kanban, for example, all use methods to follow Agile principles and values.
  • But if your team wants to be truly Agile, the methods you use should grow and evolve with the times, just like Spotify finally develops its own approach.

12. What is Behavior Driven Development?

  • With simple examples to demonstrate how to express requirements in natural language, the author Mark Shead illustrates the differences between BDD and TDD.
  • At the end of the video, he highlights the quick and cost-effective case of the BDD development approach.

13. What is DevOps?

  • DevOps is a recently popular approach to Agile development and automation that can raise the overall working speed.
  • DevOps works when everyone shares responsibility for the software delivery process, and DevOps focuses on integrating software development teams with operations teams to deliver applications and services quickly.

14. Why Have A Daily Standup – Agile Practices

  • Agile stand-up meetings are the hallmark of Agile, but why stand up? Using Agile principles, the author illustrates that we can know how and know why by understanding the principles behind the operation.
  • It turns out that Agile has never called for standing up. The key point is face-to-face communication.


Michael James Video Series

1. LeSS Complete Picture, 3-minute introduction to Large Scale Scrum

  • LeSS is Scrum. It’s the official three-minute introduction of LeSS to a large Agile framework that unleashes the most potential from a team with the least flows, roles, and management.
  • LeSS is structured with “streamlined and empirical flow control with a focus on overall product development”, and contains a minimalist set of simple rules for teams in sizes of 2 to 8. LeSS Huge is suitable for teams of 8 or more, or even for large products with up to several thousand people.

2. How Misconceptions About The Product Owner Role Harm Your Organization, And What To Do About It

  • How does your large organization understand the role of Product Owner? How does misunderstanding the Product Owner role delay customer response?
  • How should the Product Owner role play out? How does a real Product Owner provide the highest business value? While improving the team’s self-organizing and cross-functionality, is it necessary to create new PO extension roles, such as Chief Product Manager and Operations Owner?


Mike Cohn Video Series

1. Scrum Repair Guide: Welcome

  • This video features Mike Cohn explaining the inspiration for this series of Scrum Repair Guide (derived from Volkswagen Beetle) and introduces some practical Scrum problems explored in this video series.

2. Scrum Repair Guide: Sprint Planning – Save Time in Scrum’s Longest Meeting

  • Mike Cohn’s collection of Agile heavyweight experts. At the beginning of every Sprint, there is a Sprint meeting held, and often it becomes a marathon due to the lack of preparation and the desire for perfect planning.
  • For inadequate preparation, a backlog grooming meeting can be held to refine the functional characteristics effectively. It is necessary to remove the perfectionism mindset to produce an ideal Sprint backlog.

3. Scrum Repair Guide: Selecting the Right Scrum Sprint Length

  • Mike Cohn’s video select. Determining the Sprint length is a big challenge for new Agile teams, and it can be done by checking and adjusting the three pillars of Agile to find the optimal length. There are correct metrics to evaluate and observe the lengths that are too long or too short.
  • This video will show you in detail how to observe them, and once you find the right length, you should maintain it until the end of the project.

4. What are Story Points?

  • Mike Cohn is an Agile heavyweight expert who specializes in Agile estimation and user stories. The seemingly simple story points are confusing to many people.
  • Through the master’s professional explanation, you will have a complete picture of the story points.

5. Scrum Repair Guide: Grooming the Product Backlog

  • There is a lot to learn for grooming the product backlog. It is not a necessary meeting for Scrum, yet our Scrum projects would not run smoothly without it.
  • It can prioritize the backlog and split user stories into smaller pieces to be developed in the next cycle, make sure that functional acceptance specifications are clear, and clean up user stories that are no longer needed.

6. Scrum Repair Guide: Leaving Time for Testing – How to Spread Work Evenly Across the Sprint

  • Scrum overcomes the student syndrome using the Timebox principle, but in a Sprint of less than a month, the development team often drags their feet until the last minute to complete the Product Backlog Item.
  • For example, the program developer only leaves the last two days for the sounding board. What can the sounding board do during this period? It may also cause the WIP to be unfinished and unable to Demo. Mike Cohn proposes three solutions in this video.


Productivity Game Video Series

1. SCRUM: Twice the Work, Half the Time

  • Why can’t the project meet the target on time and in quality? This video shows you how “cognitive bias” leads to fallacies in planning and sticking to the status quo.
  • The book proposes the seven steps of Scrum, which can be broken down into pieces so that projects can be improved step by step. It also presents the three cores of the Scrum technique, explaining how to get twice the result with half the effort and significantly increase productivity towards success.

Roman Pichler Video Series

1.The Product Vision Board: Introduction

  • Roman Pichler is a contemporary icon of Agile PO, and his PO tools have spread to many Agile communities, most notably the Product Vision Board.
  • In this video, he introduces a complete Product Vision Board presentation, including tips on the use of each column and the tool to find appealing product vision and effective product strategies.

2. Building a Product Users Want

  • In this video, Roman Pichler, a world-renowned PO guru, introduces the product vision and creates a product strategy through the Product Vision Board.
  • He identifies the risks encountered in the initial product development and the responses by reviewing the product strategy and illustrates how to use product vision and product strategy to develop products that users want.

3. Agile Product Roadmaps

  • Roman Pichler, known as a PO guru, was invited to Munich, Germany, to deliver a speech on Agile product roadmaps, including defining a product roadmap and its use and providing a tabular approach to its creation.
  • He also introduced the approach of product roadmap derived from product strategy, the stakeholder analysis using Johari Window, and the review cycle of product roadmap defined by using Johari Window.

4. Introduction to the Product Vision Board

  • Roman Pichler, known as a PO guru, gives an introduction to the use of the Product Vision Board form tool to separate product vision and product strategy. This video provides insightful examples to illustrate the three attributes of an effective product vision (common, simple, and grand). It explains the four elements of product strategy (target group, demand, product, and business objectives).
  • In the end, it is reminded that in forming a product strategy, it is important to check whether there are any assumptions or risks in the product strategy that need to be verified to ensure a successful product launch.


Scrum Inc. Video Series

1. What is Timeboxing? | Scrum Methodology

  • Scrum Inc provides this short 2-minute video. In this video, you will learn what Timeboxing is, why it is needed, how to include open-ended tasks into Scrum, and the importance of Timeboxing in Scrum, etc.

2. Intro to the Scrum Framework

  • This video is part of the e-learning course of Scrum Inc. It introduces the key elements of Scrum in a simple mnemonic way of 3, 5, 3, namely the 3 roles, the 5 Events, and the 3 Artifacts of Scrum.
  • There is also a simple animation to help learners easily understand the interrelationship between these key elements and how they work.

3. The 5 Scrum Values

  • This video features Jeff Sutherland, author of Scrum Guide, explaining the five values of Scrum. Scrum Guide has included five values of Openness, Courage, Respect, Focus, and Commitment since 2017. However, many Agile learners don’t know the whys and wherefores.
  • In fact, Robert Dilts, founder of NLP University, has proposed a pyramid of six logical levels where values drive behavior. Therefore, value-driven Agile is consistent with this logic.


Development That Pays Video Series

1. Fibonacci Series = Accurate Agile Estimates? + FREE Cheat Sheet

  • Many Agilists use planning poker to estimate the size of User Story with the numbers of 1,2,3,5,8 …., which is the Fibonacci series. There is no clearer animated explanation of the principle of the series than this video.

Scrum vs Kanban – What’s the Difference?

  • Agile learners often get confused with Scrum and Kanban, thinking that the stand-up meeting stands on the Kanban.
  • There is a big difference between the two, and through seeing this animation, you will find the subtleties. This is a great teaching animation that is worth recommending.