One of the reasons often given for the failure of an IT system is the lack of, or misunderstanding of the underlying requirements from which the IT system was developed.
Requirements are the foundation of any successful IT project and how an organization elicits, manages and monitors your requirements will be crucial to the success of your IT projects.
Requirements are sometimes difficult to pinpoint because of the fragmented nature of large organizations. With expertise in a variety of requirements captures methodologies( For example, use case based, scenario based, or stories based), Xanadu provides the outside-the-box perspective, as well as the proper facilitation and advice on running requirements gathering exercises, to extract ideas pertinent to business solutions.
In many organizations, business analysts play the role of understanding and expressing business requirements for applications and systems. These requirements overlap with what architects need in order to undertake the architecting process effectively.
We help business analysts and product requirements teams understand enough about architecture and the architecting process to be effective partners with architects in establishing architectural requirements. We also provide techniques for requirements capture that equip business analysts to collect requirements in a format that is most useful for architects.
In addition, we elicit forward-thinking ideas so that those solutions are in position to solve future business problems.
We create a Software Requirements Specification (SRS) for your project as a blueprint for developers. Depending on the project objectives, the SRS could include any combination of robust User Cases, Integrated Functional Requirements, Wireframe Diagrams, Site Maps, Data Models, Data Flow Diagrams, State Diagrams, Process Flows, Financial Models, Requirements Traceability Matrices and Technical Specifications.
Taking a collaborative, inclusive approach where the sponsor (business), the developer (IT) and user (customer) ideally are totally involved in the process, we put business value against each of the requirements such that priorities can be determined for the ongoing development of the systems.
Keeping the user in mind throughout the entire process, we ensure the final system is what they truly need according to your business goals.
We put processes in place to manage any changes in requirements, new requirements or obsolete with the understanding that this process must always be driven by business value.
We will help you implement a formal process to handle and control changes to requirements components throughout the lifecycle. This will enable users to submit, review and approve requirements changes, track the reasons for change and handle conflict notification. This will simplify collaboration between team members, ensure that each team member knows about changes made by another and ensure changes are managed proactively.
The ultimate objective for this work is that the sponsor can feel confident that at any point in time
Known requirements are captured, well defined and under change control.
The developer has understanding of what is required in a suitable format.
The user is certain that what is being delivered will be suitable for them.
While final deliverables vary from project-to-project, our overall requirements methodology for requirements gathering is consistent throughout all our projects.
Define the Business Goals.
We work with business leaders to clearly define the outcomes they set for their project. During this phase, we discuss how your current objectives develop your future vision for your company. These goals set the direction for all the granular requirements and offer a way to measure the eventual success of the project.
Document the User Requirements.
During this phase, we investigate and document all user needs for your system. Our user requirements methodology is heavily fueled with User Cases for most projects. We use fun facilitation activities to gather the “breadth” of user requirements up front and catch the usually ‘missing’ ones and then breakdown big requirements into small manageable ones(stories) and dive into the details later and finally effectively prioritize (not just with business value!) and build effective release plans that show you quick ROI.
Specify the Requirements.
Once we have a comprehensive picture of your business and user needs, we begin specifying the functional requirements that provide detailed information for developers building your system. Functional requirements explain scenarios such as what should be shown on a given screen and which actions should trigger errors. Key deliverables in this phase include creating site maps and wireframes for websites showing specific elements that should appear on each screen.
Finally we speak on The Non-Functional/Technical Requirements and Acceptance Tests (UPFRONT).
Test Case Creation.
Whether you choose to test your new system or site in-house or out-source the QA, we can write test cases allowing any tester to easily look for holes in the system. Test cases are an important tool to ensure your system QA is well-planned and thorough. If Xanadu writes your software requirements, we can easily write test cases for your system because we will already be experts on the inner workings of your site or software