The ability to effectively split user stories can make or break your agile implementation. When faced with a massive user story that spans multiple sprints, teams often struggle to deliver incremental value and maintain momentum. The good news? There are proven techniques to break down even the most complex requirements into manageable, valuable chunks of
SPIDR: Five Simple but Powerful Ways to Split User Stories - Mountain Goat Software
Online and in-person training to help you succeed with agile
MATT THOMPSON
As part of my EngD project, I am creating ways for story authors to easily write narratives with multiple branches, along the lines of the Choose Your Own Adventure stories from the 1990s. Typically, this kind of story authoring is hard, as the number of material that needs to be written increases exponentially with the number of decision points.
Bloom’s Taxonomy – Agile Learning
Twelve Emerging Best practices for Adding UX Work to Agile Development
How experienced UX practitioners have adapted to work happily in Agile environments
How Small Stories Solve Big Problems with Ellie Snowden | Ep. #021
User Story: a Placeholder for a Conversation
User stories are meant to be a placeholder for a conversation. This article dives into the differences between user stories and tickets, where stories came from and how recent trends are moving us away from conversations. It shows the impact this is having on product development and easy ways to improve collaboration through conversation and writing better stories.
Integrating Narrative into Game Design: A Portal Post-Mortem
How I draft stories
I discovered that trying to write one big blob does not work for me. I can get as far as 2000 words before the volume overwhelms. As with many things in life, breaking it down into pieces helps a lot! This is where most outlining writers suggest a big bulleted
Learn about Lore: next-generation open source version control
Maintained by Epic Games, Lore is designed for unprecedented scalability of both data and teams. It’s optimized for projects that combine code with large binary assets.
4-Layers, A Narrative Design Approach
Introduction This blog post will be about a new way to approach narrative design in games - the 4 Layers Approach. It is based on a GDC ...
Storyteller.fit | Blog your own cycling, running and sport stories. Powered by Strava
Create beautiful stories based on the activities you recorded on Strava. From single activities to entire seasons collect the adventures and achievements of your active life.
How To Validate Product Ideas Before (And After) Building Them
People spend too much time writing software relative to speaking to potential customers, prior to launching and after it. Reversing that is a win.
Logial Thinking Process (LTP) / Issue Tree App and Exploration - Issue Trees & Logical Thinking Process
Collaboration of Rufus Pollock with David Joseph to build tooling for structured thinking — specifically a Logical Thinking Process (LTP) / Issue Tree app. Both David and Rufus share a long-standing desire to improve public discourse and improve collaboration: aligning efforts to goals, making claims or hypotheses and their logical structure clearer (claim-trees), allowing debate to accumulate, mapping evidence clearly to specific sub-claims.
Specification by example
Specification by example (SBE) is a collaborative approach to defining requirements and business-oriented functional tests for software products based on capturing and illustrating requirements using realistic examples instead of abstract statements. It is applied in the context of agile software development methods, in particular behavior-driven development. This approach is particularly successful for managing requirements and functional tests on large-scale projects of significant domain and organisational complexity.[1]
Weaving Narratives into Procedural Worlds
Examining the value, characteristics, and methods of integrating static narratives into otherwise procedurally generated environments.
not to get too ahead of some other stuff i'm working on but i think every news org should be able to build experiences like this that they own via atproto. once permissioned data lands you can tie in business models really well. "substack on atproto" is too narrow, we can do better.
nilay patel
Was just scrolling our homepage revchron feed and caught the same vibe as when I was myself a hardcore Engadget reader in 2006ish. So happy with this, so much more to come
