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 to get good design when using agile methods?
I have been using an agile methodology (SCRUM) for about three years now and I see certain advantages to it, especially in the short-term feedback at many levels (from customers having early access to implemented features, from testers that can test features as soon as they are implemented, from other developers that can provide very early feedback on new code through review, etc).
Cannot understand a certain point in Agile Manifesto Principles
I was reading Agile Manifesto Principles. Everything seems clear and reasonable except for one point:
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.
Product owners with more than one product?
Is it normal and still proper (in agile/SCRUM-based software development) for a product owner to be in charge of more than one product?
Documentation degrading – how to deal with it?
Important: we have no issues whatsoever with source code documentation. This belongs to regular code audit and is kept up to date. Our problem is with developers documentation (or, “external” if you like), little blog-like tips from programmers to programmers which tend to be once written, often left behind.
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.
Software design by pseudocoding?
Do you know a good way to design (i.e. write down) software with a method based on pseudocode?