Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  When user stories should not be used?
Previous Previous
 
Next Next
New Post 9/18/2014 5:44 PM
User is offline sureshbrady
11 posts
10th Level Poster


Re: When user stories should not be used? 

User stories are great for describing product features as well as the smaller components that make up that feature. The objective described in the story can be used to prioritise easily.

Modelling the more detailed user/system conversations will require different tools (acceptance criteria, acceptance tests). User stories are text so I would expect visual models to be used in addition to describe various interactions (Activity diagrams etc).   

 
New Post 3/6/2015 8:13 PM
User is offline April Bridges
1 posts
No Ranking


Re: When user stories should not be used? 

Your user stories should be laid out using epics an themes.  These would help in creating a high-level overview of how the user stories tie together.  Also, I was recently charged with creating a template for an Agile Functional Specification Design Document.  This, of course, isn't traditional, but the operational side of the company I work for requires a document to sign-off when it comes to requirements.  I created the document to be reminiscent of the waterfall doc, with the project overview and project scope, but I also have a section where each Sprint and the user stories that were completed in the Sprint are documented.  This allows for a formal sign-off from the stakeholder, which is the only part of the waterfall methodology that I liked, along with the full team approach you get from agile/SCRUM.

 
New Post 3/8/2015 6:49 AM
User is offline alex32
1 posts
No Ranking


Re: When user stories should not be used? 
Modified By Modern Analyst  on 3/8/2015 4:42:35 PM)

In my experience US are an easy way to describe functional requirements in an Agile process, and if you've a functional requirement to describe that's the best way to do it. Possibly you should NOT use US if you're using a non-Agile process (waterfall) because in that case I'd probably use a more formal approach with Use Cases. Both tools are similar but in Use Cases you've diagrams which are not used in Agile processes (like Scrum) because not an Agile priority.

If you're interested to Agile development for BPM, pls have a look at this special offer for an Udemy course on IBM Blueworks. (offer expires next Mar22).

thanks 

 
New Post 5/11/2015 1:53 PM
User is offline Matt Adams (Business Analyst)
6 posts
10th Level Poster


Re: When user stories should not be used? 

I'm currently working on a project where we are just getting going with user stories.

These are ein the form of As a user I want to...

The acceptance criteria is where we are capturing the NF req's. These are written in GHERKIN form.

GIVEN the user has done something

WHEN something happens

THEN this should happen within ??? 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  When user stories should not be used?

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC