How do I treat application aspects with regard to features and user stories?
When drawing up a backlog, I have several requirements that apply to a great many user stories, i.e. aspects of the application like error handling and feedback. How do I include these (without using an #include directive in each user story )? Should I treat error presentation as a feature, then have user stories for this feature like “system catches exception, and shows info to user”?
How do I draft user stories as a developer?
I am writing a system where both the system owner and myself are developers, and we are currently the only source of ‘requests’ or requirements for the system, which I would like to capture in user stories tied to features{1}. My urgent priority now is to get a managaeble backlog captured. How should I go about capturing the level of technical spec I am used to to working with in users stories, which aren’t supposed to be too technical.
Can testers peer review the developers’ design and code?
I am a junior developer for a small business using scrum / agile development. A long-term goal of ours is to be appraised at CMMI lvl 2. We have a team of 3 senior developers who implement user stories and a handful of junior developers for support.
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.
Is it appropriate to make a User Story for removing small pieces of existing functionality?
For an area of an application that has been developed, the request has come in to remove an item from a menu.
How to stop / avoid Over Time on a Scrum Team?
Actually, I’m helping a small software shop on their Scrum Implementation. Recently the Scrum Master reported me that he has a problem because the Team is working Over Time to achieve the Scope (Committed Backlog). So they have an Unreal Velocity.
Should Agile teams deliver new features daily?
My company is in the midst of a transition from waterfall-style development to Agile/Scrum. Among other things, we’re told that the expectation is for us to have new working, testable (by QA) features at the end of each day.
Is it common for business analysts (or other non-development team members) to have stories tracked alongside developers?
We’re using JIRA with Greenhopper, and currently our business analyst has tasks for their analysis which will eventually lead to new stories placed in the backlog, running alongside the stories for the current sprint, and it feels kind of messy – especially because they don’t overlap the workflow for the development stories.
How to prevent intentional over-estimation in user stories?
I am asking this from a purely hypothetical standpoint.
How to document and peer review design in scrum? [closed]
Closed 8 years ago.