Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
Image
More and more participants in my Professional Scrum Master classes arrive with Scrum "rules" they picked up from an AI chatbot. Some of those rules are accurate. Some stopped being true in November 2020. And a few were never part of Scrum at all.The trouble is that from the outside, the correct answers and the incorrect ones look the same. They are equally fluent, equally confident and equally well formatted. An AI that knows Scrum is useful. An AI that only sounds as if it knows Scrum is risky, especially when a Scrum Master repeats its answer to a Scrum Team or a stakeholder.This article offers a simple way to find out which kind of tool you are using, and a habit that makes the question matter less.One Answer Key: The Scrum GuideTo assess an AI's knowledge of Scrum fairly, we need an answer key that is not a matter of opinion. Fortunately, Scrum has one. The Scrum Guide, maintained by Ken Schwaber and Jeff Sutherland, defines the framework, and it's short enough to read in one sitting.The 2020 revision made several changes that matter here:It removed the three prescribed Daily Scrum questions.It replaced the Development Team with a single Scrum Team of a Scrum Master, a Product Owner and Developers.It introduced the Product Goal and made the three commitments explicit.It replaced "self-organizing" with "self-managing."Most of what has been written about Scrum predates these changes. A large share of it also blends Scrum with other frameworks and traditional project-management language, often without saying so. An AI model learns from all of that material, and there is far more of it than there are copies of the Guide itself. The result can be an answer that is fluent, plausible and outdated at the same time.There is a second effect worth understanding. AI models tend to go along with the framing of a question. If you ask, "What are the three Daily Scrum questions?", you have already told the model that three questions exist. Ask instead, "How is the Daily Scrum structured according to the 2020 Scrum Guide?", and you have not led it anywhere.
Twelve Questions That Reveal the DifferenceEach question below targets an answer that is still common in older or mixed Scrum material. If a model answers all twelve correctly, it is reflecting the current framework rather than the internet's average opinion of it.1. "What three questions must every team member answer in the Daily Scrum?"
None. The Daily Scrum is a 15-minute event for the Developers. The Guide states that they "can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work."2. "Who is on the Development Team?"
There is no Development Team in the 2020 Guide. There is one Scrum Team, made up of one Scrum Master, one Product Owner and Developers.3. "Is the Scrum Master a project manager or team lead?"
Neither. The Scrum Master is accountable for the Scrum Team's effectiveness, and the Guide describes Scrum Masters as "true leaders who serve the Scrum Team and the larger organization."4. "Who is accountable for the Product Backlog?"
The Product Owner. The Product Owner may delegate the work, but remains accountable.5. "How long can a Sprint be?"
One month or less, and each Sprint has a fixed length.6. "Does Scrum require user stories or story points?"
No. The Guide refers to Product Backlog items and does not prescribe either practice.7. "Who can cancel a Sprint?"
"Only the Product Owner has the authority to cancel the Sprint." This may happen, for example, if the Sprint Goal becomes obsolete.8. "How big is a Scrum Team?"
Small enough to remain nimble and large enough to complete significant work within a Sprint: "typically 10 or fewer people."9. "Is the Sprint Review a demo or a status meeting?"
Neither. It is a working session in which the Scrum Team and stakeholders inspect the outcome of the Sprint and determine future adaptations. The Guide advises against limiting it to a presentation.10. "What are Scrum's three commitments?"
The Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog, and the Definition of Done for the Increment.11. "Are Scrum Teams self-organizing or self-managing?"
Self-managing. The Scrum Team internally decides who does what, when and how.12. "Is Product Backlog refinement an official Scrum event?"
No. Refinement is an ongoing activity, not one of Scrum's events.Before you use these questions to assess an AI, it is worth answering them yourself without looking. In my experience, even seasoned practitioners hesitate on at least one of them. The pre-2020 framework is deeply embedded in how many of us learned Scrum.Testing EmpiricallyAssessing an AI tool is an exercise in empiricism. Transparency, inspection and adaptation apply here just as they do to a product. A few conditions make the inspection meaningful:Use the same wording for every tool you compare.Start a fresh conversation with no prior history, memory or custom instructions.Record the plan and the date. Models change frequently, so a result without both cannot be reproduced.Grade against the Guide alone, using three outcomes: correct, partly correct or wrong. "Partly correct" matters, because a common pattern is a model that states the right rule surrounded by outdated framing.Treat the result as a snapshot, not a verdict. The tool on your organization's licence today may behave differently next quarter, which is exactly why the inspection needs repeating.If you would like a structured way to run these twelve questions and record the results, I have published a free interactive scorecard that produces a summary you can share with your Scrum Team.Four Habits for Using AI ResponsiblyAvoiding AI is not the answer. For most Scrum Masters, it is already part of daily work. What helps is a consistent habit of verification.1. Ground the answer. Paste the relevant section of the Scrum Guide into your prompt, and instruct the model to answer only from that text. This is the single most effective step available, because it removes the model's need to draw on everything it has ever read about Scrum.2. Ask for the source. Ask the model which part of the Guide it is relying on, then open the Guide and confirm it. A model that cannot point to a section is usually reconstructing an answer. A model that cites a section that does not exist has told you everything you need to know about that answer.3. Separate the framework from practices. Scrum is a framework, deliberately incomplete. User stories, story points, planning poker, burndown charts and retrospective formats are complementary practices, not Scrum rules. Ask the model to distinguish the two explicitly. Confusing them is one of the most common sources of unproductive debate inside Scrum Teams.4. Take extra care when preparing for assessments. Use AI to explain concepts, not to supply answers, and confirm every rule against the Scrum Guide. A practice question with a subtly incorrect answer is worse than no practice at all, because it is the version you will remember under pressure.Here is a prompt that puts the first three habits into practice:I am going to paste a section of the 2020 Scrum Guide. Answer my question using only that text. Quote the sentence you are relying on. If the text does not answer the question, reply "Not covered in this section" and stop. Do not add complementary practices, terminology from other frameworks or advice from other sources unless I ask for them separately.It will not make any model infallible, but it removes the largest single source of error.When the AI Contradicts the Scrum GuideSooner or later, an AI will give you a confident answer that conflicts with the Guide, often in front of other people. The Scrum Values offer a useful response.Courage means saying, "Let me check that and come back to you," rather than repeating a rule you have not verified. Openness means correcting the model in the conversation and telling your Scrum Team what happened. When you do this visibly, you model the transparency we ask of everyone else. That does more for a team than being right the first time.One caution: a model that agrees with your correction has not proven anything. Agreement is not evidence. The Guide is.Closing ThoughtsAI shifts where the hard part of a Scrum Master's work sits. Producing an answer has become effortless. Verifying it has not, and the accountability for what we share with our Scrum Teams remains ours.Test the tools you use. Ground them in the Scrum Guide. And treat every statement about the framework as unverified until you have checked it yourself.For a seven-point fact-checking checklist and a short quiz on the 2020 Guide, see the full version of this test.
Image
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Do We Need A New Scrum Guide?! | 0 | 12.09 | 11-09-2026 |
| 2 | The AI Fluency Gap. Why Most Product Teams Are Stuck | 0 | 16.51 | 10-09-2026 |
| 3 | 🎉 Launched: Scrum Team Magazine | 0 | 15.76 | 09-09-2026 |
| 4 | AI Tool Introduction: Promptly AI | 0 | 12.6 | 16-09-2026 |
| 5 | The New SDLC From Google Has a Harness. It Doesn't Have a Team. | 0 | 14.4 | 30-09-2026 |
| 6 | 🎉 Published: Scrum Team Magazine - October 2026 - Issue #2 | 0 | 15.71 | 30-09-2026 |
| 7 | AI Changed the Bottleneck. Your WIP Limits Should Change With It. | 0 | 10.22 | 08-09-2026 |
| 8 | AI on Top of a Dysfunctional System (1): The Product Backlog | 0 | 5.29 | 20-09-2026 |
| 9 | Which Class Should You Arrange Next? | 0 | 9.78 | 07-09-2026 |
| 10 | AI Transformations And Agile Transformations Rhyme | 0 | 7.34 | 06-09-2026 |