Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  How to uapture use cases in Agile projects (using JIRA)
Previous Previous
 
Next Next
New Post 3/11/2018 9:17 PM
User is offline gh05
18 posts
9th Level Poster


How to uapture use cases in Agile projects (using JIRA) 

Hello, 

I have a few questions if some experienced BA's would be kind enough to help:

1) Can someone tell me how use cases are recorded in JIRA? I am viewing a job description which mentions recording use cases in JIRA but previously my experience has been with Team foundation server (TFS) and I captured requirements in the form of user stories. 

Would the use cases be attached to the user stories somehow or is this company expecting that use cases would be used instead of user stories?

2) If a BA is also expected to work as a project manager, organising the work of an agile team and has multiple clients/projects on the go at the same time, would these separate projects go within the same development sprint (if there was time)? For example, the development team work in 3 week sprints and one client wants a new web form created and another client wants changes made to a system....would requirements for both these projects go into the same development sprint (again, if there were time) and be discussed in daily scrums or should they be organised differently? 

I hope this question made some sense.  Quick replies would be much appreciated.


Thank you in advance.

 
New Post 3/25/2018 3:48 AM
User is offline Patrick Schmöllerl
5 posts
10th Level Poster


Re: How to uapture use cases in Agile projects (using JIRA) 
Modified By Chris Adams  on 3/26/2018 11:07:02 AM)

Hi, 

1) If you are worried about working with Jira, because you don't know the tool, don't be! The basics of Jira are really easy to understand. Even if you have never worked with it, it's almost as easy to work with as with your mail client. I'd personally disencourage you from adding a word document to the Jira Story, but using Jira's built in features. If you are lacking a field, you can always add a custom field.

If you are unsure why they use Use Cases instead of User Stories. Probably no-one outside that company will be able to truely answer that question. Every company choses their own approach or set of methods and I have never seen a client that strictly sticks to the textbook. Maybe in your case they are not an agile project and have traditionally used Use Cases. Maybe they value the more wholistic view of the Use Cases since in general Use Cases go further into details. Maybe they want the Use Case for documentation purpose. 

2) If I understand your explaination well, you are talking about a software development company that works for different clients and by different clients you are talking about different legal entities and not different business units of the same corporation. Right?

If you haven't reached the critical size to seperate teams for each client, you'll have to prioritize the demands of the different clients against each other. If possible, you want to avoid working for different clients in the same sprint (set-up costs, programmers have to get their minds focused on a different technology stack every day, you constantly have to reiterate business rules of different clients, etc.). It's easier when the switch happens on a fixed date.  In my experience that will give you the higher output in the long run. Sometimes you will encounter necessities that make this suggestion impossible (production defects, high-priority demands that "can't be delayed", contractual obligations considering reaction time, clients asking for demands that are too small to fill a sprint, delays from previous sprints, dependencies to external partners that don't work in your 3 weeks sprints, etc.) . Plenty of reasons why you can't keep working for one client the whole sprint.

 

Maybe you have been at an interview already and share your experience?


 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  How to uapture use cases in Agile projects (using JIRA)

Community Blog - Latest Posts

Pjbussol
Pjbussol
  TRUST IN CONFLICT - THE HEALTHY WAY TO PICK A FIGHT!     Perched on top of the Royal Liver Building in Liverpool, the city I grew up in, is a very special couple; married for over 100 years and standing 18ft tall the legendary Liver Birds, Bella and Bertie have unflinchingly protected the city and her people since 1911. Bel...
0 Responses
Arash
Arash
Let me start by saying that a business rule is far more granular than a business decision, and that the two should never be confused. Today, it is an unfortunate fact that some vendors would have potential clients believe that there is synergy between business rules and business decisions. Perhaps this is because in an effort to differentiate one b...
0 Responses
LN Mishra, CBAP
LN Mishra, CBAP
Traceability is one of the lesser understood aspects of business analysis. It is indeed quite hard to maintain good traceability unless automated. This is why BABoK® warns us being theoretical about traceability. In this article, I would like to explain traceability concepts with help of an example. BABoK® definition of traceability: ...
4 Responses




Latest Articles

Business jargon….in a nutshell
Jul 15, 2018
2 Comments
With this article, I’ve done the heavy lifting for you, by mentioning some of these jargon-based pearls of wisdom here. You ...
Featured Digital Library Resources 
Copyright 2006-2018 by Modern Analyst Media LLC