Vibe Academy's board-health lesson labels itself 08 on screen and 9 in the audio, and its two-day blocked rule appears in neither the Scrum Guide nor the Kanban Guide

The artifact is a 70.10 second vertical clip at 720x1280 (9:16), delivered in an MP4 container that ffprobe identifies as mov,mp4,m4a,3gp,3g2,mj2. Video is HEVC/H.265, Main profile, hvc1 tag, yuv420p, 30 fps, 2,102 frames, with a stream bitrate of 93,491 bps. Audio is AAC in its HE-AACv2 profile, 44.1 kHz stereo, 64,149 bps, 1,513 frames. Overall container bitrate is 164,377 bps and the file is 1,440,355 bytes, matching the yt-dlp format id bytevc1_720p_164377-1. The post timestamp is 1791410506, which is 2026-10-07T22:01:46Z. The uploader handle is _vibe_academy and the channel nickname is Vibe Academy. The audio track is credited as "original sound" by Vibe Academy, so there is no licensed music attribution. The description runs 222 characters and ends in six hashtags: #ProductOwner #BacklogGrooming #ScrumAI #AgileAI #Scrum #LearnAI. At capture on 2026-10-08T00:02:30Z the post showed 252 views, 2 likes, 0 comments, 0 reposts and 5 saves. I read 11 of the 35 extracted frames (001, 004, 007, 010, 014, 018, 022, 026, 030, 033, 035) because the layout is a single static slide for the full runtime, and I read all 238 words of the transcript. Every frame shows the same cream background card. The top left reads "LESSON 08" and the top right reads "08 / 10". Below that, a red eyebrow label reads "BOARD DIAGNOSTICS", followed by a large serif headline, "A healthy board is" in black with "boring." in red italic. A rule separates three rows, each with a red serif label in a left column and monospace body text in a right column. The labels read "Piles", "Stalls" and "Drift". Their body text reads, in order, "Tickets stuck in-progress → AI flags the pile; you find the blocker." then "Blocked >2 days → AI names the wait; you decide to escalate or descope." then "Tickets past their estimate window → AI surfaces the slip; you explain or re-plan." A second rule sits above the line "The status report writes itself as a side effect." The lower half is a cut-out presenter, a bald man in a dark crew-neck shirt, speaking to camera against the same cream field, with no visible room, desk or set. Rolling word-by-word captions sit beneath him with the active word in red, reading in sequence "A healthy sprint board", "before your daily standup.", "Here's the board", "statuses, assignees, how", "grooming needed summary.", "has been sitting blocked for", "Your job is to confirm", "input, not something", "looks fine" isn't an answer." and "final lesson is about". A footer carries a small green and yellow V mark, the wordmark "vibe.academy", and the gray label "AI FOR PRODUCT OWNERS". No sprint board, Jira screen, prompt window or AI interface is ever shown on screen.

The slide and the voiceover disagree about which lesson this is

The on-screen card says "LESSON 08" and "08 / 10" in every one of the 11 frames I read. The voiceover says "Lesson 9 of 10, AI for Product Owners." Those cannot both be right, and the contradiction lives entirely inside the artifact, so no external source is needed to settle that one is wrong. The audio also closes with "That's what the final lesson is about," which places this clip immediately before the last entry. If the series really ends at 10, the spoken "lesson 9" is the self-consistent reading and the slide is the error. I cannot confirm which is correct from outside the file. The watermark brand is real and the account link checks out: vibe.academy describes itself as "AI education for everyone" with the tagline "Bite sized AI lessons, for normal people," and it links to the TikTok handle @_vibe_academy. The site's public pages did not list an "AI for Product Owners" course when I fetched them, so the series numbering is not independently verifiable there.

"Grooming" was retired from the Scrum Guide in 2013

The video says to "ask AI for a bottleneck or grooming-needed summary," and the description tags the post #BacklogGrooming. The Scrum Guide revision history records the change in the 2011-to-2013 edition in one line: "The Product Backlog is refined rather than groomed." The current November 2020 Scrum Guide uses only the replacement term, defining it as "Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items." The word "grooming" does not appear in the 2020 guide at all. The practice the video describes is real and the rename did not change what it is, so this is a vocabulary problem rather than a method problem. It matters because a Product Owner who prompts an AI with "grooming" is using a term the framework dropped more than a decade ago, and because the hashtag teaches that vocabulary to viewers learning Scrum for the first time.

The Daily Scrum is a Developers' event, and the guide treats it as the opposite of a status report

The video builds toward a single payoff: "The status report writes itself as a side effect" and "AI's summary is the stand-up input, not something you draft separately." The 2020 Scrum Guide scopes that event narrowly. It states that "The Daily Scrum is a 15-minute event for the Developers of the Scrum Team," and that "If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers." A Product Owner who is not working Sprint Backlog items is not a required attendee. The guide also gives the event a purpose that runs against the status framing: "The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary," and "Daily Scrums improve communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings." The video's framing has a Product Owner arriving with a pre-generated diagnosis of other people's work. That is a legitimate thing to do, and it may well help, but it is not what the Scrum Guide calls the Daily Scrum, and the clip presents it as though it were. The guide also assigns impediment removal elsewhere, listing the Scrum Master as accountable for "Causing the removal of impediments to the Scrum Team's progress."

The two-day blocked threshold is the creator's heuristic, not a published standard

The slide states "Blocked >2 days" and the voiceover repeats "stalled work that has been sitting blocked for more than two days." I checked both governing documents and neither contains it. The 2020 Scrum Guide has no work-in-progress limits, no blocked-item tracking and no day-based thresholds anywhere in its text. The Kanban Guide, version 2025.5 published 1 May 2025 by John Coleman, Daniel Vacanti, Colleen Johnson, Prateek Singh, Julia Wester and others, defines the relevant metric without any constant attached: Work Item Age is "The elapsed time between when a work item started and the current date," and Cycle Time is "The elapsed time between when a work item started and when a work item finished." Both are measured against a team's own observed distribution, which is the point of tracking them, because two days is a crisis for a one-day cycle time and unremarkable for a three-week one. Treat the number as a starting value to tune against your own history rather than a rule you inherited.

The "piles" and "drift" signals are Kanban flow concepts presented under a Scrum label

Three of the video's hashtags are #ScrumAI, #AgileAI and #Scrum, and the footer reads "AI FOR PRODUCT OWNERS," which is a Scrum accountability. The three diagnostics it names come from Kanban. "Pile-ups in your in-progress column" is work in progress, which the Kanban Guide defines as "The number of work items started but not finished" and governs with an explicit practice: "Kanban system members must explicitly control the number of work items in a workflow from started to finished." Tickets "past their estimate window" is Work Item Age under a different name. Mixing the two frameworks is common and defensible in practice, and the Kanban Guide is designed to overlay other methods. The gap worth naming is that a viewer following this lesson will go looking for WIP limits and aging rules in the Scrum Guide and find nothing, because the source is a separate document the video never cites. One detail cuts against the Product Owner framing specifically: the Scrum Guide assigns estimation to the people doing the work, stating that "The Developers who will be doing the work are responsible for the sizing. The Product Owner may influence the Developers by helping them understand and select trade-offs." A Product Owner flagging estimate slip is interpreting data the Developers own.

Jira already computes time-in-column and flags widening columns without a paste step

The workflow the video prescribes is manual data entry. It asks you to "paste a snapshot of your board with ticket titles, statuses, assignees, how many days each ticket has been in its current column." Assembling that last field by hand is the expensive part, and the two most common board tools already derive it. Atlassian's documentation for the Jira control chart states that it "takes the time spent by each work item in a particular status (or statuses), and maps it over a specified period of time." The cumulative flow diagram covers the pile-up case directly: "If your chart contains an area that is widening vertically over time, the column that equates to the widening area will generally be a bottleneck." The video never mentions either report, and it never shows a board or a chat window, so a viewer has no way to know the native tooling exists. The honest version of this lesson is that AI adds a readable narrative summary on top of numbers Jira already produces, which is a smaller claim than the one the clip makes. One practical caution the video also skips: a board snapshot contains ticket titles and named assignees, so pasting it into a consumer AI tool moves internal project and staffing detail into a third party's system. Check your employer's policy and your vendor's data-retention settings before making it a daily habit.

Twelve lines of the stored transcript are transcription noise, not anything the presenter said

The transcript file in this directory runs 238 words, and 64 of them are machine error. Real speech ends at 69.0 seconds with "That's what the final lesson is about." Everything after that is garbled, including "Your school样 станeth on FDA in the start" and "How many česums can predict between air locking up." The proof is in the timestamps rather than the nonsense: audio.mp3 is 70.138776 seconds long, and the transcriber emitted segments running to 98.0 seconds, including a block from 85.6 to 98.0 seconds that sits roughly 28 seconds past the end of the media. Whisper produced those words from the music outro and from nothing at all. Only the first 18 lines, 174 words, correspond to audible speech. I am flagging this because the raw transcript is stored alongside this post, and anyone quoting from it could easily attribute invented sentences to the creator.

Key Takeaways

Verified: The brand is genuine. vibe.academy publishes the tagline "Bite sized AI lessons, for normal people" and links to @_vibe_academy, matching the "vibe.academy | AI FOR PRODUCT OWNERS" watermark on every frame.
Correction: The clip contradicts itself on its own episode number. The slide reads "LESSON 08" and "08 / 10" while the voiceover says "Lesson 9 of 10." The spoken number is the one consistent with the closing line about a final lesson.
Correction: "Grooming" has not been Scrum terminology since the 2011-to-2013 revision, which states "The Product Backlog is refined rather than groomed." The 2020 Scrum Guide uses "Product Backlog refinement" and never uses the older word.
Correction: The "Blocked >2 days" threshold has no published basis. It appears in neither the 2020 Scrum Guide nor Kanban Guide 2025.5. The Kanban Guide's Work Item Age carries no fixed constant and is read against a team's own distribution.
Partial correction: Positioning an AI board summary as "the stand-up input" conflicts with the Scrum Guide, which defines the Daily Scrum as "a 15-minute event for the Developers of the Scrum Team" whose purpose is "to inspect progress toward the Sprint Goal," not to produce a status report.
Clarification: The three diagnostics are Kanban flow concepts, not Scrum ones, despite the #Scrum and #ScrumAI tags. WIP and Work Item Age are defined in the Kanban Guide, a document the video never names.
Clarification: The Scrum Guide assigns sizing to Developers, stating "The Developers who will be doing the work are responsible for the sizing," which puts estimate-slip interpretation outside the Product Owner's listed accountabilities.
Context: Jira already computes the hardest input the video asks you to type by hand. Its control chart maps "the time spent by each work item in a particular status," and its cumulative flow diagram identifies a widening column as "generally a bottleneck."
Context: A board snapshot carries ticket titles and named assignees. Confirm your data-handling policy before pasting one into a consumer AI tool as a daily routine.
Unverified: The existence and numbering of the other nine lessons in the "AI for Product Owners" series could not be confirmed. The vibe.academy pages I fetched list no course by that name.
Context: The stored transcript.txt in this directory contains 64 words of hallucinated output. The audio file is 70.138776 seconds long and the transcriber emitted segments out to 98.0 seconds. Only the first 174 words are real.

Resources

A healthy sprint board is boring. An unhealthy one has tells 👀 Paste ... establishes the source post, its 2026-10-07T22:01:46Z publication, and the 222-character description carrying the #BacklogGrooming and #Scrum tags.
The Scrum Guide, November 2020 establishes that the Daily Scrum is "a 15-minute event for the Developers of the Scrum Team," that sizing belongs to the Developers, that impediment removal is the Scrum Master's accountability, and that the guide contains no WIP limits or day-based thresholds.
Scrum Guide revision history establishes that the 2011-to-2013 edition replaced "grooming" with "refinement" in the line "The Product Backlog is refined rather than groomed."
Kanban Guide, version 2025.5, 1 May 2025 establishes the definitions of Work Item Age, Cycle Time and Work In Progress, and establishes that none of them carries a fixed two-day threshold.
Jira control chart documentation establishes that Jira already calculates time spent by each work item in a given status, which is the field the video asks viewers to assemble manually.
Jira cumulative flow diagram documentation establishes that a widening column on the chart indicates a bottleneck, covering the video's "piles" diagnostic natively.
vibe.academy establishes the brand behind the on-screen watermark, its "Bite sized AI lessons, for normal people" tagline, and its link to the @_vibe_academy TikTok account.