The planning phase of RAMP (Requirements Analysis and Management Process) sets the stage for requirements work. You collect some initial information to help scope the effort, and then you develop a plan for eliciting, specifying, and verifying requirements with project stakeholders. In some companies, all of the requirements work is completed at the beginning of the project and signed off, following a traditional or modified waterfall approach. In other companies, requirements work is performed in a series of feature-driven iterations using lean or agile development methods. You do the same tasks with either approach. The difference is primarily in when you perform your requirements work, not how you perform it. In either case, you still need to do some amount of requirements planning at the beginning of the project.
In this webinar you will learn how to:
• Define the high-level goals and business requirements for the project
• Identify the application end users and other stakeholders for the project
• Identify business processes to be impacted or transformed in the project
• Define the end-user capabilities required for each process identified
• Determine business priorities and order capabilities to be implemented
The Ravenflow RAMP Methodology describes a business-driven, best practices approach to planning, eliciting, specifying, validating and managing requirements for maximum project success. Bringing together proven business process and use case analysis techniques, the methodology enables rapid definition of essential business requirements by modeling and analyzing the processes where the solution will be used. Required capabilities are mapped from their parent business processes, then broken down into increasing levels of detail until the entire project scope has been specified. This not only ensures the requirements fully reflect business needs, but contain the detail necessary for successful implementation by the development team.