Splitting user stories into smaller stories
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 all they achieve is facilitating the next step in the process and not delivering the application’s main benefit to the user.
How to deal with user interface design and respective feature support in Agile development?
In an Agile development process usually the main focus is on User stories, but sometimes a single requirement may span several user stories.
User stories are too high level and conceptual, management expects developers to fill in the blanks
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 things are considered too RUP to be discussed.
How to word user stories which have been split from a larger epic
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 follows;
Requirement gathering in an agile methodology
In the great book User Stories Applied the author specified the following process for trawling requirements in the form of user stories:
Where to put details about the acceptance criteria of a user story?
In this blog post about acceptance criteria the author explains that good acceptance criteria should:
Agile User Stories and acceptance criteria
I am writing some agile user stories and acceptance stories for the first time, and was hoping for some feedback from an experienced product manager or developer.
Task-based authorization for user stories
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 created task-based authorization where roles are still used to lump tasks into groups (see for example rhino security . At least that’s my understanding.
Task-based authorization for user stories
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 created task-based authorization where roles are still used to lump tasks into groups (see for example rhino security . At least that’s my understanding.
Task-based authorization for user stories
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 created task-based authorization where roles are still used to lump tasks into groups (see for example rhino security . At least that’s my understanding.