🎉New Writing North’s Film4-backed Genre Feature Lab has selected three debut feature projects for its inaugural edition: The Lost, written by Jackie Okwera; Scrum, written by Bethan Moore; and You Can Leave Whenever You Want, written by Emilie Robson.
🎬The Genre Feature Lab aims to identify and nurture writing talent from the North of England and it is the organisation’s latest collaboration with Film4’s parent organisation Channel 4, after the Northern Talent Network and Channel 4 Writing for Television Awards.
🎥“The genre lab gives us a focused approach to developing relationships with storytellers from the region.” - Amy O’Hara, development and production executive at Film4.
It's been said by many that there's no such thing as an original thought or idea.
Mark Twain one of America's greatest writers of all time said ‘There is no such thing as a new idea, it is impossible…’
So how did Einstein come up with the theory of relativity? Or how about something closer to home, how about the Agile Manifesto how did they come up with that?
Well, they drew upon shared experiences with others, experimentation and past observation, combining knowledge and techniques and any socialising they did outside of their normal circles, gaining knowledge they otherwise wouldn't have had.
This is how all great original ideas and thoughts start.
Now there's a well-known quote by Diogenes famously turned into graffiti art by Banksy in New York, ‘one original thought is worth a thousand mindless quotings’ meaning one original thought is worth a thousand that are not but which is itself another quote.
Well, Diogenes was a famous cynic and did live nearly 2500 years ago.
Agile values and principles advocate collaboration, interactions, communication and group reflection so we can adapt together. It's part of the journey to being agile rather than just doing it.
But knowing the Agile Manifesto by heart or being able to quote the Scrum Guide word for word is not going to lead us to new and better ways of working. It won't lead us to anything original for the context we’re working in.
There's no magic recipe, Scrum, Kanban or any of the other frameworks are not silver bullets.
The reality is that in life, excellence and innovation don't come from memorisation and regurgitation or from consistent execution of well-known activities.
In order to move the bar, in order to create something new, in order to push the boundaries there has to be original thought. The ability to connect the dots in new ways.
Yes, you need the basics but you can connect the values and principles to all the others finding how they interact and amplify each other drawing conclusions and theories from study and lived experience.
Connecting the dots is what it's all about.
So you're never going to actually be agile, achieve agility, by simply following a manifesto, a guide or a ‘playbook’.
Einstein didn't come up with his theories by reading one physics book or sticking to established theories at the time.
They didn’t miraculously create the Agile Manifesto when they met back in 2001. It was from their experience over many years, through inspection and adaptation and their shared experiences on what works and what doesn’t.
Ideas don't go anywhere it's about the execution of the idea.
So actively create the time and space for the next great original thought or idea by being open to new, and old, thinking through collaboration and communication by building relationships, by learning.
https://lnkd.in/ezn2kZC9#Scrum#scrummaster#Agile
For more content check my agile YouTube channel: https://lnkd.in/eKP9TjCa
Senior Data Focused Engineering Lead | AI & Data Architect | GenAI, Big Data, Cloud & ML | Driving Scalable Data Solutions | Generative AI Innovator | Agile Leader
Writing perfect code in tests is easy; getting it to survive in production is where the real fun begins! 🤣🎢. Have you also faced this situation ??? some where i read - Writing code is like preparing for a date; it looks great in your head, but the reality? Well, let's just say it can get awkward! 😅💔
#ProductionReady#CodeQuality#Agile
🕷️ What If #SpiderMan 2 Taught #SAFe? 🕸️
Imagine Peter Parker and Miles Morales running a SAFe® Transformation in New York City. Turns out, Spider-Man 2 isn’t just a game—it’s a web of Agile lessons! Let’s break it down:
1️⃣ "Release Train" Engineer... Literally! 🚂🕷️
The Spider-Men manage an actual train during chaos in the city. Coincidence? I think not. The train symbolizes the Agile Release Train (ART)—and they’re all about keeping it on track, even when Doc Ock throws curveballs (or tentacles)!
2️⃣ Lean Flow = Web Swinging 🏙️
Spider-Man doesn’t wait for traffic lights; he swings through obstacles with efficiency. Lean flow in SAFe is just that—removing bottlenecks so value swings directly to customers, faster than the Green Goblin can cackle.
3️⃣ PI Planning with Villains and Heroes 🤝🦹
What if Spider-Man held a (PI) Planning session with villains like Venom? "OK, Doc Ock, you get Q1 for city domination, but Q2 belongs to friendly neighborhood Spidey initiatives!" Alignment is key—even in chaos.
4️⃣ Visualize Work in Progress: The Villain Kanban Board 📝
Spider-Men clearly track who’s causing trouble in NYC. Kingpin? In progress. Sandman? Blocked by Spider-webs. A Kanban board keeps the crime-fighting backlog visible, so they prioritize effectively!
5️⃣ Relentless Improvement = New Gadgets ⚙️
Spider-Man 2 introduces upgraded suits, gadgets, and combat skills—proof that even superheroes practice relentless improvement. SAFe teaches the same: iterate, innovate, and adapt. Because standing still? That’s not Agile (or Spider-Man-approved).
✨ Agile Truth: Whether you’re swinging between skyscrapers or leading a SAFe implementation, the principles are the same: teamwork, alignment, and constant improvement.
#SpiderMan2#SAFeTransformation#AgileWithHumor#ScalingAgility#SpiderSAFe
Demo Generator validates whether the project is a supported type, Agile, Scrum, or Basic, and that all of the contents can be read. At the end of th
Read More At: https://lnkd.in/diKURa72#hellolinkedin
Do you struggle with taking projects to completion?
As an indie-hacker, I have multiple personal projects that I find myself intrigued by. With a demanding day-job, finishing these personal projects becomes daunting.
Starting a new project is always exciting, but sustaining the same enthusiasm to lead the project to completion is a real challenge. If you're in a similar boat, this article on how to finish projects might help.
https://lnkd.in/dYU_t7r2
Feature Driven Development (FDD):
FDD developed by Jeff De Luca and Peter Coad. FDD does not cover whole development life cycle but rather focuses on design and building phases. In Develop an Overall Model phase a team consists of development team members and experts are formed to build an overall model of the domain, in order to establish the scope of the system and provide a common understanding the domain. In Build a Features List phase The team then identifies a comprehensive list of features and features are grouped together into feature sets, and then major feature sets. In Plan by Feature phase Collected feature list is then prioritized and a development plan is establishes that includes the order in which feature sets will be realized. In Design by Feature and Build by Feature phase the team launches into a series of Design by Feature and Build by Feature iterations where they break into Feature Teams and design, build, and test features in two-week time boxes. Repeat this step until no more features exist.
