Your Development Team offers many capabilities to assist in thee requirements analysis phase of a development. In many cases, we can offer domain expertise in addition to requirements analysis itself. We consider this to be the most critical phase of the development cycle, because this is the point where a team can be sent off to develop the “wrong product”.

• Requirement gathering – identifying various types of requirements from various sources including project documentation, business process documentation, and stakeholder interviews. While domain expertise is required for these activities, a fresh, outside perspective substantially improves the result.
• Requirement analysis – determining whether the stated requirements are clear, complete, consistent and unambiguous, and resolving any apparent conflicts. It is crucial to have at least one team member who has not been inoculated with the “everybody knows that” syndrom
• Requirements recording – requirements are documented in various forms, usually including a summary list and may include natural language documents, use cases, user stories, or process specifications.
• Requirement management – requirement management may take various forms depending on the product’s scope and purpose, ranging from peer collaboration and review of requirements documents, and archival in a version control system, to full product life cycle traceability. We also offer our own light weight, highly efficient requirements maintenance and traceability infrastructure if you do not already have your own in place.

Of course, we are capable of joining a project at any development phase, however, in any event, developing and / or assessing requirements is a crucial first step.