Telegram RegisterThe public register of Telegram

Channel

Scrum Mastery Club

@scrum_mastery

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,080subscribers

+2 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001608979977
TypeChannel
Username@scrum_mastery
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/scrum_mastery

Growth

1,0781,0811,079.56 August 2026 — 1,078 subscribers6 August 2026 — 1,078 subscribers9 August 2026 — 1,081 subscribers12 August 2026 — 1,080 subscribers1,0806 August 202612 August 2026
4 measurements spanning 6 days, net +2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,078–1,081 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 02:521,080-1
9 Aug 2026, 02:211,081+3
6 Aug 2026, 12:341,078no change
6 Aug 2026, 05:521,078first reading

Engagement

20 posts held, back to 19 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.6%
avg views ÷ 1,080 subscribers
Avg views / post
276
5 posts measured
Reaction rate
1.26%
reactions ÷ views · ER floor
Posts in window
6
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held20 (19 June 20263 August 2026)
Views total1,381
Reactions total14
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 12:34 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

32 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 37.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1237.5%
👍1134.4%
🔥618.8%
👏13.13%
💯13.13%
🤣13.13%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 13 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 32reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 19 June 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

3 Aug 2026, 05:47 UTC109 views4 reactionsread 6 August 2026
Photo

Если у вас нет стратегии продукта - ваш беклог, скорее всего, бесполезен Да, звучит жестко. Но в последнее я раз за разом вижу одну и ту же картину. Команды часами обсуждают приоритеты задач, спорят о порядке реализации, оценивают в человеко-часах (Story Points), ведут огромные беклоги… и почти никто не начинает с главного вопроса: А какая стратегия продукта? Получается парадокс. Владелец продукта знает, что де

👍2💯1🔥1

1 Aug 2026, 08:27 UTC82 viewsread 6 August 2026
Photo

📍 Пора начинать подготовку! Уже 10 августа стартует тренинг программы «Карта гипотез. Уровень практик 1». Публикуем подробную программу первого практикума. Что будем делать? 🎯 Формулировать цели и метрики - как отличить цель от метрики; - как сформулировать качественную цель; - зачем нужны балансирующие метрики и как они помогают принимать решения. 👤 Определять субъекта - кто такой субъект и почему именно вокр

31 Jul 2026, 03:37 UTC734 views8 reactionsread 6 August 2026
Photo

📚Книги для агентов изменений Участвую сейчас в одном из проектов организационной трансформации и поймал себя на мысли: а какие книги действительно лежат у меня на рабочем столе и к которым я регулярно возвращаюсь? Для меня это всего две книги. И символично, что обе написаны людьми, которых я знаю уже много лет и глубоко уважаю как практиков. 📘 Первая - книга моего друга Ильи Павличенко «Дизайн Agile-организации».

🔥4👍3👏1

29 Jul 2026, 05:42 UTC185 viewsread 6 August 2026
Photo

🌙 Новый формат тренингов в августе: В августе запускаем новый формат обучения по Карте гипотез: ✅ Вечерние занятия - после рабочего дня, без ущерба для основной деятельности ✅ Перерывы между сессиями - чтобы успеть осмыслить, попробовать, задать вопросы 📅 Расписание ▶️ Карта гипотез — Уровень Практик 1 Старт: 10 августа 2026 Дни: понедельник, среда, пятница Время: 16:00–19:00 (МСК) → Для тех, кто делает первые ша

17 Jul 2026, 04:38 UTC271 views2 reactionsread 6 August 2026
Photo

🔥 Last call на ближайшее обучение! ➡ Карта гипотез — Уровень Практик (Ступень 2) 🗓 23 июля | онлайн 🔍 Что будет на тренинге? ✔️ Глубокая проработка каждого элемента карты ✔️ Работа с типовыми ошибками ✔️ Продвинутые топологии ✔️ Секреты создания личной стратегии ✔️ Переход от стратегии к реализации 👑 По итогам обучения вы можете получить возможность сдать экзамен и получить сертификат. Ну и двигаться дальше,

2

8 Jul 2026, 09:35 UTC228 views2 reactionsread 6 August 2026
Photo

📄 Сотрудничество человека и ИИ Друзья, нашел интересную статью про взаимодействия человека и ИИ: Human–AI Collaboration: A New Strange Loop Сотрудничество человека и ИИ: новый «Странный цикл» Дуглас Хофштадтер, американский ученый-когнитивист, специалист по информатике и автор, наиболее известный своей книгой «Gödel, Escher, Bach: An Eternal Golden Braid», удостоенной Пулитцеровской премии, ввел понятие «странного

👍2

6 Jul 2026, 06:40 UTC189 views1 reactionsread 6 August 2026

Ребята, всем привет! 👋 Немного скорректировали расписание - стартуем завтра, во вторник. Приходите :) 🗓 Расписание на июль - уточнение: 🤖 07.07 | Групповой разбор стратегии ИИ-трансформации Как внедрять ИИ не ради хайпа, а для реального ускорения доставки ценности? Разберем кейсы, риски и точки входа. 🛠 14.07 | Мастер-класс по инструментарию Практический обзор инструментов, которые уже сейчас меняют работу команд

1

3 Jul 2026, 13:34 UTC170 views1 reactionsread 6 August 2026
Photo

🗺️ Карта Гипотез: Практикум. Уровень 1 Фундамент для сертификации: Фасилитатор Карты Гипотез Коллеги, 9 июля запускаем первую ступень официальной сертификации по технологии Карты Гипотез. Это обязательный базовый уровень: без глубокого понимания архитектуры технологии невозможно стать сертифицированным специалистом. Наша цель - дать вам четкое, инженерное понимание технологии. Мы уходим от интуитивного «угадывания»

1

3 Jul 2026, 05:48 UTC144 views1 reactionsread 6 August 2026
Photo

🚀 Стартуем июль: «Бизнес нового времени: Продукты, Команды и ИИ» Друзья, всем привет! 👋 Сегодня, 3 июля, начинаем новый месяц в клубе. Тема горячая и важная: как меняться бизнесу, продуктам и командам в эпоху искусственного интеллекта. Мы будем разбирать реальные кейсы, инструменты и стратегии, которые работают прямо сейчас. 🤖 Первое занятие: групповой разбор стратегии ИИ-трансформации Тема: Как внедрять ИИ не ра

1

1 Jul 2026, 06:17 UTC139 views2 reactionsread 6 August 2026
Photo

🧠 Влияние без полномочий: от тактик к системным гипотезам Друзья, вчера провели финальную встречу месяца в формате группового брейншторма на тему «Влияние без полномочий». Делюсь интересным инсайтом. Начали работу с вопроса: «Где вам не хватает влияния?». Ответы попали в самую точку: саботаж «старой гвардии», политические игры, иллюзия согласия руководства и страх потери контроля в командах. Когда нет администрати

2

29 Jun 2026, 05:48 UTC205 viewsread 6 August 2026
Photo

Летнее расписание для тех, кто хочет получить новую квалификацию по Карте Гипотез. 🤫 Расписание на июль- август 2026 🗓Карта гипотез — Уровень Практик 1 09 июля 2026 | онлайн ➡️Записаться 🗓 Карта гипотез — Уровень Практик 2 23 июля 2026 | онлайн ➡️Записаться 🗓 Карта гипотез — Уровень Фасилитатор 28-29 августа 2026 | очно, Москва ➡️ Записаться Все программы проводит тренер Алексей Пикулев 👉

Showing the 12 most recent of 20 posts we hold for @scrum_mastery. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 150,788 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Scrum Mastery Club” (@scrum_mastery), 1,080 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/scrum_mastery.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.