(Verse 1)
In the heart of the code, where logic unfolds,
There's a team known far and wide.
"The Velocity Raptors", they're called,
In the realm of Scrum, they ride.

With keyboards clicking and screens aglow,
They're a sight to behold, in the tech world's flow.

(Chorus)
Oh, Velocity Raptors, agile and bright,
Coding through the day, debugging at night.
Growing together, in knowledge and might,
Creating value, with every byte.

(Verse 2)
They sprint through tasks, with speed unseen,
In the world of loops and binary.
With every stand-up, they convene,
Turning visions into reality.

In the face of bugs, they never falter,
With every commit, they only alter.

(Chorus)
Oh, Velocity Raptors, strong and keen,
In the world of code, they're the queen and king.
Working hard, in their vibrant scene,
To the sound of success, their hearts sing.

(Bridge)
In the dance of data, they find delight,
In the maze of algorithms, they ignite.
With every challenge, they take flight,
In the canvas of code, they write.

(Chorus)
Oh, Velocity Raptors, bold and bright,
In the tech universe, they're a shining light.
Together they soar, to an incredible height,
In the book of innovation, they write.

(Outro)
So here's to the Raptors, in all their glory,
This is their song, this is their story.
In the annals of Scrum, they're legendary,
The Velocity Raptors, and their victorious trajectory.

The Velocity Raptors Anthem

The Velocity Raptors Anthem [OP Remix]

Ktokolwiek natrafił na swojej drodze na solidny Kanban, ten wie, że nieintuicyjną praktyką jest limitowanie pracy w toku. To jednak budzi duże obawy, lęki zarówno w zespołach, u menedżerów, ale też u tych, którzy proponują takie zmiany. Od czego zacząć? Od zrozumienia, że rodzajów limitów jest kilka i warto zastanowić się, od czego zacząć w naszym kontekście. A jak je ustalić? Jak często zmieniać? Dowiedz się z tego krótkiego, acz treściwego odcinka!

Kanban przy kawie

70. Jak zacząć z limitami pracy w toku?

In this conversation, Dave Prior and Richard Chang discuss the challenges that product owners face when they don't receive the support and direction they need from their leadership. They explore strategies for product owners to navigate these situations, including having open and honest conversations with leadership, running experiments to validate assumptions, and finding mentors or support networks. They also emphasize the importance of understanding the needs and perspectives of stakeholders and users, and the need for product owners to manage their space and hold their ground, even in the face of power dynamics. Overall, the conversation highlights the importance of effective communication, collaboration, and continuous learning in the role of a product owner.

Takeaways
* Product owners often struggle when they don't receive the support and direction they need from their leadership.
* Having open and honest conversations with leadership can help product owners gain clarity and alignment on product strategy and goals.
* Running experiments and validating assumptions can help product owners make informed decisions and mitigate risks.
* Finding mentors or support networks can provide guidance and help product owners navigate challenging situations.
* Understanding the needs and perspectives of stakeholders and users is crucial for product owners to make effective decisions.
* Effective communication, collaboration, and continuous learning are key skills for product owners to succeed in their role.

Chapters

04:55 Introduction and Background
07:12 Challenges of Product Ownership
11:49 Taking Initiative and Creating Strategic Direction
17:39 Validating Assumptions and Removing Bias
27:56 Coping Strategies and Social Engineering
31:01 Conclusion and Plug for Richard's Classes

Contacting Richard

Web: www.agilityprimesolutions.com
Email: richard.cheng@agilityprimesolutions.com
LinkedIn: www.linkedin.com/in/richardcheng/
Twitter: twitter.com/richardkcheng


Contacting Dave

Linktree: https://linktr.ee/mrsungo
LinkedIn: https://www.linkedin.com/in/mrsungo/


Links from Dave's Intro
The Agile Network*
https://theagilenetwork.com/

*If you’d like a discount on an annual membership or want to try a month for free, send an email to dave@theageilnetwork.com and let me know.

Agile 2024 Interviews:
https://drunkenpm.blogspot.com/2024/07/agile-2024-all-interviews.html

The Art of War for Collaboration Course
https://modusinstitute.com/course/art-of-war-collaboration

Guided Personal Kanban (September 2024)
https://modusinstitute.com/course/guided-pk-sep-usa

Public Scrum Training CSM/CSPO/A-CSPO
https://www.scrumalliance.org/courses-events/search?tr=14153&cnty=US

Being a Product Owner with No Direction From Above w Richard Cheng

#Nisha, Dan, and Prateek discuss what the 'Done' column on your board means and how it is not what most people think it is.

Episode 95 - Done Is Not What You Think It Is

Jak uwidocznić pracę zespołu odpowiedzialnego za komunikację wewnętrzną? Jak poradzić sobie ze zmianami w zespole, a nawet nową szefową? W ramach serii "Kanban w Twojej branży" zaprosiłem Anię Kubecką z działu Communication Vattenfall IT, by opowiedziała o motywacji zespołu, w którym pracuje oraz o tym, jak proste praktyki, narzędzia i zdyscyplinowane podejście pomagają podnosić jakość ich usług. Kanban to nie tylko coś dla zespołów IT i każdy może skorzystać ze zwinnych praktyk. Zapraszam do wywiadu! 
Zajrzyj też do wpisu towarzyszącego temu odcinkowi: https://www.kanbanprzykawie.pl/?p=1221

71. Kanban w dziale Communication, czyli komunikacji wewnętrznej

Summary

In this episode, Jimi Fosdick joins Dave for a conversation about his journey from traditional project management to agile. They discuss the challenges of applying traditional project management to software development, the importance of understanding the context and problem domain when choosing project management approaches, and the misuse of the term 'agile' in the consulting industry. They also touch on the legacy of Frederick Taylor and the need for a people-centered approach in project management. The conversation explores the challenges of traditional project management and the need for a more empirical and agile approach. They discuss the problems with big upfront planning, the importance of shorter cycle times, and the fear of failure. The conversation also touches on the need for more humane workspaces and the changing nature of work. The principal themes include the limitations of traditional project management, the benefits of an empirical approach, and the evolving workforce and work environment.


Takeaways
	•	Traditional project management is effective for problems that can be solved on paper upfront, but may not work well for software development.
	•	Agile approaches, such as Scrum, are better suited for software development and other complex, empirical problems.
	•	The term 'agile' has become an overloaded and misused brand in the consulting industry.
	•	Hybrid approaches that combine traditional project management and agile practices can be problematic and may not fully embrace the values and principles of agile.
	•	A people-centered approach is essential in project management, and the focus should be on collaboration, respect, and solving the right problems. Traditional project management relies on upfront planning, which can lead to longer cycle times and higher failure rates.
	•	An empirical approach, such as Agile, allows for shorter cycle times and the ability to adapt and change as needed.
	•	The fear of failure often hinders organizations from embracing more agile and iterative approaches.
	•	There is a growing emphasis on creating more humane workspaces and allowing for more flexibility and creativity in the workplace.
	•	The nature of work is changing, and organizations need to adapt to the expectations and needs of the new generation of workers.

Chapters

02:20 Introduction and Background
05:52 The Challenges of Traditional Project Management in Software Development
08:33 Differentiating Scrum from Traditional Project Management
12:13 The Misuse of the Term 'Agile'
14:38 The Problem with Hybrid Approaches
22:17 Legacy Code in Our Heads: Shifting the Project Management Paradigm
26:21 The Benefits of an Empirical Approach
28:46 Overcoming the Fear of Failure
33:18 Creating More Humane Workspaces
39:03 The Changing Nature of Work


Contacting Jimi
 - Web: https://fearlessagility.com/
 - X: https://x.com/FearlessAgility
 - Facebook: https://www.facebook.com/FearlessAgility/
 - Instagram: https://www.instagram.com/realFearlessAgility/
 - Courses on the Scrum Alliance site: https://tinyurl.com/yjc2rtmf



Links from Dave's Intro
 - The Art of War for Collaboration Course http://modusinstitute.com/course/art-of-war-collaboration

- Guided Personal Kanban (September 2024)
http://modusinstitute.com/course/guided-pk-sep-usa

The Agile Network*
https://go.theagilenetwork.com/l/web-dprior
	Use the discount codes below to get either 20% or 2 months of free access
	2 Free Months - DRUNKENPM10CM
	20% off Annual - DRUNKENPM10C20

Contacting Dave
Linktree: https://linktr.ee/mrsungo

An interview with Jimi Fosdick of Fearless Agility

Agile methodology follows an iterative and incremental path for software development. As a subset of Agile, Scrum focuses on delivering small, functional builds every two to three weeks. Delve deeper into the distinctions between Agile vs Scrum. https://www.clickittech.com/it-management/agile-vs-scrum/?utm_source=referal&utm_medium=backlinks&utm_campaign=rk

Agile Vs Scrum Differences

This article explores the challenges of balancing team ownership with individual recognition within Agile software development. While Agile emphasizes teamwork and collective achievement, it can be difficult to motivate top developers who desire individual recognition for their contributions. The article argues that a balance is crucial to avoid losing talented individuals while maintaining a collaborative team environment. It proposes strategies such as tailored recognition programs, opportunities for visibility, peer recognition, and leadership roles as solutions to this challenge, highlighting the critical role of leadership in fostering a culture that values both individual and team success.

Balancing Team Ownership with Individual Recognition in Agile

The Importance of Ideation Sessions in an Agile

Czym jest i jakie cechy opisują tzw. "zobowiązanie" (po angielsku słowo “committment”)? Jak ma się znaczenie tego słowa w języku Kanbanu do historii i obecnego użycia w Scrumie? Czy powinniśmy podejmować zobowiązanie “od tak”, czy może skrupulatnie przyglądać się, czemu i kiedy mówimy: “tak”? A co z konsekwencjami tych decyzji? Posłużymy się odnośnikami do książki “Noise” Daniela Kahnemanna oraz rozmowy Adama Granta i Tima Harforda. Przeczytaj wpis towarzyszący temu odcinkowi na: https://www.kanbanprzykawie.pl/index.php/2024/10/08/odcinek-72-trudne-slowo-zobowiazanie-czyli-commitment-w-kanbanie/

72. Trudne słowo: zobowiązanie

Overwhelmed by Black Friday prep? In this episode, we share simple time management strategies like Scrum and time-blocking to help you get organized and stress-free. Learn how the Black Friday Promo Kit can make planning easier, even if you're short on time, and discover tips to spark creativity while running your business. Don't let procrastination hold you back—start prepping today!

From Procrastination to Productivity: How to Manage Your Time and Launch a Black Friday Promotion

Retrospectives can be a powerful tool to help your team identify weaknesses, celebrate successes, and continually improve. They can also quickly become repetitive slogs that serve no real purpose apart from complaining about everything that has gone wrong recently. Join us as we discuss how to make the most of your retrospectives. 

Retrospectives

Le Product Owner a un rôle crucial, au cœur des approches de gestion de projet agiles. Dans cette vidéo, découvrez pourquoi le Product Owner ne rédige pas de Spécifications Fonctionnelles Générales (SFG) et comment il maximise la valeur en gérant le Product Backlog.

Téléchargez mon livre blanc (GRATUIT) ⤵️
https://bestofbusinessanalyst.fr/introduction-a-la-business-analyse/

Ce que vous allez apprendre :
•        Rôle du Product Owner : Comment agit-il en tant que gardien de la vision produit, en remplaçant la rédaction des spécifications traditionnelles par une gestion proactive du Product Backlog.
•        Limites des SFG en Agile : Pourquoi les Spécifications Fonctionnelles Générales, bien que cruciales en méthodes traditionnelles, n'ont pas de place dans un cadre agile tel que Scrum.
•        Puissance du Story Mapping : Découvrez comment le story mapping contribue à la conception fonctionnelle générale en vous aidant à prioriser ce qui compte vraiment pour l'utilisateur.

00:00 Introduction
02:09 Rôle du Product Owner
07:07 Les SFG et les méthodes agiles
10:48 La valeur du story mapping
14:13 Conclusion

Le Product Owner rédige-t-il les SFG (les Spécifications Fonctionnelles Générales en agile)?

Coraz więcej organizacji widzi korzyści z wizualizacji procesów przygotowawczych pracy za pomocą tzw. Upstream Kanbanu. Jak pracować z takim systemem, tablicą pod kątem spotkań? Czy w ogóle są potrzebne, a jeśli tak, to czy jedno, czy więcej? Oto kilka praktycznych porad dotyczących przechodzenia przez taką tablicę w jednym formacie - Service Request Review albo dwóch niezależnych kadencjach. Wysłuchaj, odnieś to do swojego kontekstu, a może będziesz w stanie lepiej zarządzić przepływem, komunikacją do klientów i zespołów? Przeczytaj również artykuł towarzyszący podcastowi:  https://www.tinyurl.com/464z73kk

74. Jak pracować z upstreamem - Service Request Review

A podcast about Agile and Project Management

Retro music is where it's at! Making chip-tunes for the world to enjoy.

Dan Vacanti and Prateek Singh drink whisk(e)y and discuss various facets of agile software development. From scotch to bourbon and from metrics to human behaviour, we cover it all.

Podcast poświęcony wszystkiemu co związane z Kanbanem w pracy intelektualnej, twórczej, IT. Prowadzi Radek Orszewski - praktyk, coach i trener Metody Kanban.

“Incompris, livrés à eux-mêmes, mais pas incompétents!”

Rien n’existe pour aider les Business Analysts à asseoir leur rôle. Forcés d’être autodidactes, ils perdent confiance en eux alors qu’ils sont simplement plongés dans un environnement économique qui n’est pas encore vraiment prêt pour eux, car peu ou pas mature en ce qui concerne la compréhension de la Business Analyse. 

Pourquoi attendre que les organismes officiels de formation prennent enfin en considération notre pratique opérationnelle sur le terrain?

Nous, les Business Analysts en devenir ou expérimentés, avons le pouvoir de faire reconnaître notre rôle et de l’incarner avec assurance.

C’est la raison d’être de Best Of Business Analyst, l’écosystème complet pour se former au métier, reprendre les rênes de sa carrière et enfin s’épanouir dans sa vie (car tout est lié!).


Retrouvez toute l'actu, les bonnes pratiques, techniques, méthodes, les formations et les coachings de Best Of Business Analyst sur le 1er site internet 100% dédié aux Business Analysts francophones, sur la chaîne YouTube éponyme et sur LinkedIn

Helping online entrepreneurs build their businesses and still have a life.  Get started here: https://linktr.ee/thescrumshop

Join Expero's team of tech experts as they discuss best practices and lessons learned from the battlefield of consulting. Hosts and guests draw from a deep well of experience working with custom software products, supply chain optimization systems, biotech manufacturing workflows, financial service modernization efforts, and everything in between.

New tracks tagged #scrum