Tevékenység
-
"Fail fast" is not a viable approach to software construction. There's no benefit in constant failure. What we want to do is succeed fast. Do that…
"Fail fast" is not a viable approach to software construction. There's no benefit in constant failure. What we want to do is succeed fast. Do that…
Kedvelte: Balázs Kövecses
-
(ex) tesztmenedzserként is, tanácsadóként is szívügyem a minőségi szoftver
(ex) tesztmenedzserként is, tanácsadóként is szívügyem a minőségi szoftver
Kedvelte: Balázs Kövecses
-
Now imagine what would happen if good enough prototypes could be generated from a few prompts... The real productivity improvement doesn't come…
Now imagine what would happen if good enough prototypes could be generated from a few prompts... The real productivity improvement doesn't come…
Kedvelte: Balázs Kövecses
Szakmai tapasztalat
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Tanulmányok
More activity by Balázs
-
Claude Code is starting to feel like a mid-level engineer on my team. Most of what I do now is guide architecture decisions. Why? Because I built a…
Claude Code is starting to feel like a mid-level engineer on my team. Most of what I do now is guide architecture decisions. Why? Because I built a…
Kedvelte: Balázs Kövecses
-
🔬 Yesterday at the TUM Quantum Lab in Garching A fascinating half-day diving deep into the foundations of quantum computation. We had the…
🔬 Yesterday at the TUM Quantum Lab in Garching A fascinating half-day diving deep into the foundations of quantum computation. We had the…
Kedvelte: Balázs Kövecses
-
I'm happy to change my mind on topics when I learn something new. While I continue to be critical of the AI hype train - and especially the term…
I'm happy to change my mind on topics when I learn something new. While I continue to be critical of the AI hype train - and especially the term…
Kedvelte: Balázs Kövecses
-
Attention is all you need? AI startups certainly think so! There is just too much noise! We don’t need an update on every marginal improvement. And…
Attention is all you need? AI startups certainly think so! There is just too much noise! We don’t need an update on every marginal improvement. And…
Kedvelte: Balázs Kövecses
További hasonló profilok
További bejegyzések felfedezése
-
Prashant S V
Why AI Needs Scrum Masters, Project Managers & Program Managers More Than Ever ? AI is evolving faster than organizations can manage. Every week, there’s: ▪️ A new model ▪️ A new tool ▪️ A new big promise But here’s the truth → AI success isn’t about algorithms alone. It’s about people, processes, and decisions that shape the future. And that’s where roles like Scrum Masters, Technical Project Managers, and Program Managers step in: ▪️ Ensuring the right data flows into the right models ▪️ Aligning researchers, engineers, and business leaders (who often speak different “languages”) ▪️ Spotting risks that won’t show up in any Jira board ▪️ Asking the hard questions: - Should we build this? - What’s the impact if this fails? - Do we have the right guardrails in place? Without us → AI projects turn into silos of smart people running in different directions. With us → AI becomes strategic, ethical, and scalable innovation. In a world where speed without direction is chaos, we make sure AI actually lands where it needs to go—safely, purposefully, and with impact. The future isn’t just AI. It’s AI + Scrum Masters + TPMs + PMs who know how to guide it. What’s the one skill you think will define these roles in the AI era? Checkout the AI toolkit here - https://lnkd.in/gpS_qQ8r
26 hozzászólás -
Michael Lloyd
4 Questions an effective Scrum Master should Ask themselves every day: 1️⃣ What can I do today that will maximize the likelihood that the team achieves the sprint goal? 2️⃣ What can I do today that will encourage the team to become more Self-Managing? 3️⃣ What can I do today to support the team to become more cross-functional? 4️⃣ Is there anything happening that is undermining Empiricism and what can I do about it? Each of these questions, reflected on daily, will generally lead a Scrum Master to the right course of action. Each of these has a bunch of 'sub questions' worth thinking about too, so read on if you want to explore some more detail; 1️⃣ What can I do today that will maximize the likelihood that the team achieves the sprint goal? Are there any impediments that might prevent the goal from being achieved? Will the impediment get resolved if I do nothing? If not, what is the smallest action I can take to make the last statement true? Is there anything I can contribute towards that will make delivering an increment happen sooner? Is there anything I can do to shorten the feedback loop on the work of the sprint? 2️⃣ What can I do today that will encourage the team to become more Self-Managing? Is there something I have previously done *for* the team that I could stop doing? Is there anything the team is not doing that I can support to try? Is there any work happening outside the team that I could help bring closer to the team? 3️⃣ What can I do today to support the team to become more cross-functional? Is there any work in progress that could be paired on? Is there any 'waiting' between stages of work? How might I encourage eliminating it? What skills delta's exist in the team, and what training or facilitation could I offer to close these? 4️⃣ Is there anything happening that is undermining Empiricism and what can I do about it? Is anyone asking for status reports or project plans that I could bring closer to the teams work? Are there teams we depend on who are struggling to align their work, and how can we work more closely? Is the wider organization practicing proper Scrum/Agile ways of working, if not, what can I contribute to show what good looks like? I created these as a guide for a new, inexperienced Scrum Master on how to think about the right things day to day. I might even turn this into some sort of graphic aid. What do you think, have I missed anything?
12 hozzászólás