Capturing correct level of detail in a user story
I have written various user stories that describe functionality at a pretty high-level. For example:
What standard superseded 830-1998?
I have been looking into how to document software projects more formally, and I have learned about IEEE 830-1998: Recommended Practice for Software Requirements Specifications. However, as you can see from that link, it has been superseded.
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.
What kind of metrics, if any, can be collected from requirements development?
We elicit requirements from our product stakeholders by creating and refining user stories in monthly sprint planning meetings. This includes defining use cases, acceptance criteria, and identifying constraints, and the final result is a sprint backlog of user stories. The high-level customer requirements are refined into lower-level product requirements through design reviews among the development team throughout the sprint. The design reviews result in UML diagrams, software interfaces, and, in general, a human language description of various software requirements.
How do I break down and plan a personal programming project? [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 12 years ago. I’ve just started a programming job where I’m […]
How can a non-technical person learn to write a spec for small projects?
How can a non-technical person learn to write specs for small projects?
Ambiguous program requirements
it seems that most of the programming exercises that I am currently doing, are a little bit ambiguous when it comes to specifying what should I do.
What are some general guidelines for setting up an iOS project I will want to personally publish but sell in the future? [closed]
Closed 10 years ago.
Are costs part of the requirements?
I am new to requirements analysis and have a simple questions: Would you include the budget in the requirements, if e. g. the departments budget for running costs is 10k a year.
How to handle this unfortunately non hypothetical situation with end-users?
I work in a medium sized company but with a very small IT force.