Do you estimate all user stories in iteration zero?
After our product backlog is created and prioritized, are we meant to briefly estimate all the stories in the product backlog? I assume they have to be in order to create a product burndown chart, however if you have a lot of stories this could take a long time initially.
How to prevent intentional over-estimation in user stories?
I am asking this from a purely hypothetical standpoint.
User stories as a contract definition?
I am often asked to write a requirements document for a new piece of work. I write requirements using user stories. The list of requirements is then used as a contract with the client denoting the functionality that will be delivered. The temptation them becomes to add more and more detail and more and more stories in an attempt to define a water-tight specification that rules out any expensive mistakes.
User Stories with design elements in Scrum
We’re implementing a Scrum workflow and I’m trying to wrap my head around user stories, when they’re completed, iterations, etc. One thing we often do is work on a story during an early iteration, get it fully working but “ugly”. We use plain buttons, no images, just the text to show that it’s working the way they should. We show our customer, make sure they are happy with how it’s working, then we usually use images they provide to finish up the design of the feature and complete it.
How to edit existing user stories
I’m quite new to working in Agile and with user stories and scenarios in the BDD tool Cucumber and ideally I’ll need to go on a course of all of this. I have a set of user stories that need to be edited for an upcoming release.
Story points for bug fixing tasks: Is it suitable for Scrum?
I’m just wondering if we should assign story points to bug fixing tasks or not. JIRA, our issues-tracking software, does not have story point field for Bug type issues (it’s only for Storys and Epics).
Is it a good practice to have Epics under User Stories?
In my current team there is a practice of putting Epics under User Stories and sometimes even User Stories or Epics under Tasks! When questioned, the usual reply is: “if it is not a good practice then the project management tool would not have allowed doing so!” (IBM Rational Team Concert, for one does not prevent such practice.)
Do story points have a direct relation with task estimates?
In my current team, where we run multiple scrums, the Story points are usually based on the effort required to complete the User Story. For example if an User Story has 2 tasks, both needing 5 days each, they the Story is assigned 10 points. So 1 day of effort is considered to be one Story point.
Scrum – real life example? [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
Native mobile app development – how do I structure my user stories?
I’m about to start on a project which will involve developing prototype native mobile apps (iOS and Android initially) as well as a web-based admin interface and an API for these apps to communicate with. We’ve got a list of stories already drafted up, however a lot of them are in the format: