This is amazing, actually a massive pain point today is to understand the end to end narrative of business/ products in financial services and define new ones on top of that. Have you thought about adding a step to encapsulate the problem/ opportunity space details to start with. This will serve as a summary for senior management to understand what is going on in the multiple initiatives that are funded, perhaps a very custom scenario for large financial institutions. This is a great solution to the jira challenges that are out there, the key will also lie in how simple this is to use, sometimes companies think that something like this is a silver bullet to solve all their problems.
@narrative-tech
4 ай бұрын
Thank you. We have thought about it. The latest version allows you to put detailed descriptions on Narrative Scripts, and we'll be expanding this data capability to add a lot more details like KPIs, and then the ability to roll up KPIs upwards to create aggregate reports. So much more to come
@PetrSzturc
6 ай бұрын
I like the idea but cant imagine this being used for big projects. It might get overwhelming same way as tickets. 🤷
@narrative-tech
5 ай бұрын
Thanks. We have a ton of ways planned to ensure things stay tidy. Come join our community slack and take part in the discussion of how it should be.
@theherk
6 ай бұрын
“Agile no longer feels fit for modern software development” because people seem to think it is about sprints, standups, and jira. It isn’t. So tell me, which of the twelve principals of actual agile does this buck? My assumption is none. In which case this is at best another workflow that can be used in conjunction with agile or not, and at worst a contrived simplification of workflow overlaid on a timeline with some AI to sound magical and new.
@SamHatoum-rh7xh
6 ай бұрын
100%, we're in agreement. Key thing there is that it no longer "feels" fit and I agree with your statement that it's because people think it's about sprints, standups, and JIRA. You won't find any disagreements from me. I built a career, consultancy, and now a startup from my architecture + agile coaching roots, and I'm very fond of the 12 agile principles. The reality is that the majority of Agile projects are run with sprints, standups and JIRA, and they are run as ticket factories. I see this day-in day-out in my work with clients. As for it being a workflow tool / contrived simplification - there's more than meets the eye here. Narrative-Driven has of Story Mapping, Business Process Modeling, Information Architecture, Event Storming, BDD, DDD, and more. Doing all of these practices in tandem is very hard. We did this in my consulting company for years and produced incredible results and now want to make them accessible to everyone. Narrative-Driven provides a standard set of structures and constructs that get you doing these combined practices without having to ever know about them, and helps you fall in to the pit of success. Ultimately it's a sort of schema - but I digress!
@narrative-tech
5 ай бұрын
Vaughn Vernon says it better than anyone: kalele.io/what-you-need-from-agile/
@nonnnth
6 ай бұрын
So it’s like the blueprint of the project 🤔 that’s neat.
@SamHatoum-rh7xh
6 ай бұрын
That's the idea indeed. Thanks!
@-dubu
6 ай бұрын
This makes a lot of sense, would have saved some big headaches. Excited to see where it goes
@narrative-tech
6 ай бұрын
Thank you!
@rakeshbhat5102
6 ай бұрын
Interesting to see how it is different from BDD
@SamHatoum-rh7xh
6 ай бұрын
Similar to BDD, Narrative-Driven Development focuses on using natural language to specify software systems. However NDD also combines user flows with technical architecture into a cohesive whole. This approach creates a clear and comprehensive timeline, avoiding the complexity of traditional methods. It provides a framework for detailed specifications and high-level concepts, making it accessible to both technical and non-technical stakeholders.
Пікірлер