We are a small team of 3 developers (2 experienced but new to this particular business sector) developing a functionally complex product. We're using Scrum and have a demo at the end of each sprint. Its clear that the functional team have plenty of ideas but these are not well communicated to the development team and the demo poses mo...
How do you go about the requirements gathering phase? Does anyone have a good set of guidelines or tips to follow? What are some good questions to ask the stakeholders? I am currently working on a new project and there are a lot of unknowns. I am in the process of coming up with a list of questions to ask the stakeholders. However I ca...
I'm looking for a wiki that I can use to track requirements for a project, but we would like to be able to export the wiki (with formatting) to Microsoft Word. Does anyone know of a wiki that does this? ...
Why is it when I'm documenting requirements, it always has to be phrased as "It SHALL do this..." vs. "It WILL do this...". I know this is a odd question, but one I've never been able to find an answer to. It's always just been, "that's the way you write them". I know it's a silly question, but one that's always puzzled me. ...
I am looking for input on where developers find value in requirements. I understand there are times and situations where requirements make a mess, but let's presume the person writing the requirements understands the business and what they need. Maybe requirements are needed for governance, or testing, or even because none of the coder...
We have a large backlog of things we should do in our software, in a lot of different categories, for example: New problem areas for our products to solve New functionality supporting existing problem areas New functionality requested by our existing users Usability and "look" enhancements Architectural upgrades to the back-end Bug fi...
We attempt to do agile development at my current job and we succeed for the most part. The main problem seems to be that the developers on the project are always waiting for requirements at the beginning of the sprint and rushing to get get things down by the end. The business analysts who are delivering the requirements are always worki...
I'm a s/w developer in a small internal IT department within a financial firm and have worked on a number of small-medium sized projects that have had little or no project management throughout. This seems to always result in scope creep and therefore not meeting deadlines and having to sacrifice good design/code to satisfy users/manage...
How can our team gather requirements from our "Product Owner" in as low friction yet useable of a way as possible? Now here's the guidelines- No posts that it can't be done or that the business needs to make a decision that it cares about quality, yada yada. The product I work for is a small group that has been successful for years. I j...
Let's say I am modelling a process that involves a conversation or exchnage between two actors. For this example, I'll use something easily understandable:- Supplier creates a price list, Buyer chooses some items to buy and sends a Purchase Order, Supplier receives the purchase order and sends the goods. Supplier sends an invoice Buye...
Have you had any good/bad experiences with Case Complete? Are there Use Case creation products like it that you would recommend? Thank you ...
I am looking for free and/or open source requirements management tools. Does anyone have any experience with these tools and can recommend one or two? Thanks. ...
I'm interested in data/information/knowledge management, so I am building an application for this purpose in an effort to understand the concepts better. However, since I'm building this for myself (and perhaps for others in the future), I have to play the role of customer/client as well as requirements analyst (in addition to software e...
Suppose you're working on an enterprise project in which you have to get management signoff in order for you to develop a new feature set. Usually your management has no problem signing off on some bright shiny new UI feature. Unfortunately they have a hard time appreciating some behind-the-scenes issues that are crucial to the applicati...
I was wondering if anyone could provide me some information on what they put in a requirements document, how do you structure it? I'm the lead for the first time ever and I want to make sure I provide good documents so the project will succeed. Any templates/examples would be great. ...
Developing software solutions which already exist and are available for re-use (either commercial or open-source). AKA "re-inventing the wheel". Same as above, but your solution being broken. AKA "re-inventing the square wheel". Developing solutions for problems which do not exist. Again, I'm interested in a more formal approach, e.g....
How flexible should a programmer be if a client requests requirements that is not in the project scope? ...
When you need to refine requirements from your customer or customer representative, what techniques have worked best for you? By best, I mean what techniques have ultimately resulted in delivering the right product and keeping the relationship positive. ---Background--- Our customer representative group elicits requirements from our sys...
An initial draft of requirements specification has been completed and now it is time to take stock of requirements, review the specification. Part of this process is to make sure that there are no sizeable gaps in the specification. Needless to say that the gaps lead to highly inaccurate estimates, inevitable scope creep later in the pro...
There are many tools out there for writing and managing requirements, but are there any good ones out there for reviewing them? I'm not talking about managing reviews, but automation tools that look for common requirement blunders (such as using negative requirements, or ones that are worded in a way to make testing difficult). More ...