Using Completed User Stories to Estimate Future User Stories
In Scrum/Agile, the complexity of a user story can be estimated in story points. After completing some user stories, a programmer or team of programmers can use those experiences to better estimate how much time it might take to complete a future user story.
Validating User Stories: How much change is too much?
While the core of requirements development and acceptance criteria would ideally take place during the planning meeting in order to create a better estimate, Scrum encourages continuous interaction with the product owner throughout the sprint to validate and refine user stories.
How do you keep track of a requirements document on an agile team?
I understand that User Stories dominate the agile world, but how are these artifacts stored, so that new developers who join the team can come up to speed with the requirements?
Link between tests and user stories
I have not see these links explicitly stated in the Agile literature I have read. So, I was wondering if this approach was correct: Let a story be defined as “In order to [RESULT], [ROLE] needs to [ACTION]” then
Does the use of personas in Agile have any value during implementation?
This is about the use of personas, primarily in the agile development realm.
Why do we use story points instead of man days when estimating user stories?
In agile methodologies (e.g. SCRUM), the complexity/effort needed for user stories are measured in Story points. Story points are used to calculate how many user stories a team can take in an iteration.
Is using unit tests to tell a story a good idea?
So, I have an authentication module I wrote some time ago. Now I’m seeing the errors of my way and writing unit tests for it. While writing unit tests, I have a hard time coming up with good names and good areas to test. For instance, I have things like
When should user stories be combined and separated? [closed]
Closed 11 years ago.
How can I plan optimization tasks in Scrum?
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.
What can be used in lieu of use cases to gather requirements?
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 cases’ would be a very very good fit to document many of the things and functions discuessed and/or proposed for the new system. When I suggested we needed to create ‘use cases’ so that we don’t forget what we said/concluded and also to have programers know what they should code, the leading BA mentioned don’t like ‘use cases’.