Suppose I have a user story of size 20 that can be split in other 2 user stories, making the original story an epic. Should the sum of these user stories add up to 20? What's the best practice in this ...

If I understand Scrum correctly, this is how I determine the work my team can take on in the next sprint:
I average the number of completed points for the past several sprints.
This quantity is our ...

How do you handle a user story when it depends on horizontal integrations in an application?
An example would be a user story such as, "I would like to have audio help on the start screen." Let's say ...

I'm trying to better organize my application architecture, so I've been doing some reading, but I keep running into references to "Business Logic" and "Business Rules". I've never really understood ...

How can I put in the design constraint into a user story?
The system to be developed will generate a invoice when a payment is made, and will send the invoice to xMail (an emailing tool) which will ...

I am trying to understand how to create user stories and tasks. I have read articles stating that you should create small user stories and they should be a "vertical slice" of functionality instead of ...

I have bought Jira for my hobby project and I am currently creating epics, user stories and tasks. I have a question regarding organization and registration of tasks.
1)
I have a user story that is: ...

We've just deployed a new system for our users. The product owner asked us to check the log files every day in the next iteration for error messages and exceptions. We have written the following user ...

I'm trying to learn about Agile methodologies through the Head First Software Development book and after reading about it, I've tried to apply the concept of User Stories to a recent mini-project (set ...

I have started using Pivotal tracker for a project I'm working on. Conceptually, this seems really cool and I'm interested in using the agile model. However, I have one problem with everything talked ...

I'm taking an Introduction to Agile Software Development course, The instructor was discussing an example about online store and asked us to write the User Stories and the Conditions of satisfactions ...

Let's say we have a backlog of User Stories, each with an estimated number of Story Points, and now we're doing the Sprint Planning.
Now, the Stories should be broken down into tasks and many Scrum ...

In my project we assign 4 hours for 1 story point and estimate based on story point. So in this case one ideal day of work will be done in 2 elapsed days. From an agile standpoint are we doing story ...

I have read that story point estimation is not intended to actually tie with number of hours , but is used to identify the relative capacity. I have a java application which has a adapter layer , a ...

User Story captures what the user wants to do with the system at a high level. I understand that the user story would further drive a number low level requirements. Is user story same as high level ...

I am about to start User story sessions in my team. It's quite new for them and I am also wrestling with certain things. For the current project we have some well worked out wireframes.
I read a lot ...

We are using JIRA to manage the scrum process. What I'm curious about is whether the User Story issue type should be assigned to a team member, the PO, or remain unassigned. My gut tells me it should ...

I am writing a user story and have a simple questions.
Consider, I am writing it for login module which calls internally a web service to authenticate the user and returns the data. How this can be ...

Lest's say I have user stories about using product catalog in shop:
As an administrator I can add/modify/delete catalog items (one or more user story, doesn't matter here)
As a customer I can search ...

My understanding is that the first step of defining user stories is to define roles. The problem with role-based systems is that this form of authorization is often too coarse-grained. Hence, people ...

In this blog post about acceptance criteria the author explains that good acceptance criteria should:
State an intent not a solution (e.g. “The user can choose an account”
rather than “The user can ...

I want to start using BDD in our company. The best place to keep stories from my point of view is the Atlassian Wiki pages. Obviously I expected some existing techniques for retrieving stories from ...

I have an epic which involves creating a mobile application which retrieves a user's data they have previously created in a web application and act on it locally. It seems logical to split the epic as ...

I am employed in a very brilliant company with a true intention of doing XP. Communication is good and management is open to constructive discussion but due to pressing time constraints, some certain ...

In an Agile development process usually the main focus is on User stories, but sometimes a single requirement may span several user stories.
For example, the client may request a search page for all ...

I've been reading various techniques for splitting large user stories in helpful ways, such as by user workflow through the system etc. What I'm struggling with is how to word these smaller stories if ...

I'm a programmer currently working in rounds of meetings along with BAs and PM to gather/describe modules and functionality of our case management system; after a few meetings I saw that using 'use ...

Recently my Scrum team has received several requests for optimizing certain parts of our code. Looking at the software with a profiler found some spots where the code could be improved.
We agreed to ...