user stories
 |
What’s the Problem with User Stories? Agile projects focus on very lightweight, simple requirements embodied in user stories. However, there are some problems with relying solely on user stories. They often don't contain enough accuracy for development, testing, or industry regulations. There's a better way to write detailed requirements that are still agile. |
|
 |
Use Continuous Backlog Grooming to Refine Agile Requirements Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help. |
|
 |
Think Small: Break Down User Stories for Agile Success The entire agile team needs to be involved in a continuous process of identifying ways to simplify work, right up until a story is complete. Smaller stories ensure that development work is rapid and trackable. Mitch Goldstein details how to focus on breaking stories down into a more estimable, “digestible” size. |
|
 |
Changing the Narrative: Using Storytelling in Software Testing Stories change how we think and how we perceive our surroundings. This applies at work, too. What narrative did we tell ourselves during that project? Do we tell ourselves we are worthy of succeeding, or does our story tell us to fail again? Here are some ways testers can use stories to their advantage. |
|
 |
To Deliver Value in Your IT Projects, Understand Context First Starting a project without understanding can lead to a mess from a usability perspective. Too often, we build what we can without taking the time to question whom we are building it for and why. A user story is a simple but effective tool to determine how much we understand about the context of a problem. |
|
 |
The Three Pillars of Agile Quality and Testing: Crosscutting Concerns The Three Pillars is a framework for establishing a balanced strategic plan for effective quality and testing. But beyond the individual pillars themselves, the real value resides in crosscutting concerns. It requires a balance across all three pillars to implement any one of the practices properly. |
|
 |
Capture the Magic of Pixar in Your Next Software Project Recently Pixar was kind enough to publish the twenty-two rules of storytelling that its teams follow with every film it releases. And lucky for software developers, it appears that many of these rules can be applied to software development to enrich the storytelling experience for users. |
|
 |
Never Forget to Tell Your Software’s Story It's not enough anymore to simply try to create an app or piece of software that's better than the rest. There's simply too much competition. However, learning how to tell a story with your software, and even a story about the creation of that story, creates something truly special—beauty. |
