The deliverable of the Discover phase is a Project Vision/Scope document. The milestone will be achieved when Azavar team members and your team finalize this document's content and the document is put under version control. The Vision/Scope document is a conceptual expression of your requirements, presented as usage scenarios, functions and business objects in the application's conceptual architecture. As the analysis and design activities proceed, explicit milestones to review and assess against project scope will trigger revision and reassessment of the project plan and schedule.

The following lead to meeting the vision/scope approved milestone:

1. Define Goals and Objectives
   The first step is to define a set of Webability™ objectives. This involves identifying the purpose of the Web application and creating a clear statement of objectives that should be accomplished. Because the Web is constantly evolving to meet business demands, both short-term and long-term goals should be included. Once these objectives are laid out, they should be prioritized into primary, secondary and tertiary levels of importance. 
   
   
2. Determine Necessary Components
   The next step is to determine what elements will be included in the Web application. This involves analyzing the objectives of the application and then breaking down the end product into individual pieces, or components, which will be used to generate a complete solution. These components are based on actual tasks the Web application must support in order for users to accomplish their goals. 
   
   At this stage, the functionality of each individual component is detailed. This creates a clear picture of how users are going to interact with the Web application without getting into the details of how the desired functionality is going to be achieved. That part is our next step.
   
   
3. Select/Finalize Technology
   Once the various components of a project have been defined, a model can be created that outlines user interactions of each component. This model is called a user interaction model. It demonstrates how users will accomplish a particular task within the application, detailing each step they will have to take. From the interaction model the appropriate technology can be selected to implement the desired functionality. 
   
   For each component, there may be several technical solutions.  Based on factors such as the Web application’s objectives and the target audience, the appropriate technology can be selected.
   
   Azavar has the expertise to provide and implement the appropriate technology. Therefore we can properly evaluate the benefits and limitations of each technology solution. Azavar’s forward thinking approach keeps our clients on the cutting-edge of technology, while taking into consideration the limitations of their users. The technology used to implement a project should be compatible — able to be accessed by the target audience, scalable — capable of growing with the client and extensible — able to change quickly in response to the client’s needs.
   
   
4. Outline Content
   Projects that have database driven components require an upfront data assessment. The condition of the data is a major factor in determining the scope of the project. The assessment looks at a number of key aspects to determine the extent of the data formatting that is necessary:
   
   
   1. Where will the data come from?
   2. What format will it be in?
   3. Will it have all the required information?
   4. Will the data need to be cleansed?
   
   

   Getting good data to work with is a process which is often overlooked. It is important to take this into consideration when estimating the scope of a project.

5. Define Project Scope
   After the analysis process is completed, the project scope can be defined. The scope takes into consideration the depth of information, the necessary components and the technical requirements of the Web application, along with practical matters such as time frame. Once the scope is defined, the project begins to materialize and a cost proposal is presented to the client.
   
   Before a project is set into motion, the Azavar™ Team will work with the client to plan and schedule the stages of a successful implementation. The Azavar™ Project Plan will outline how the projects requirements will be met and the Web application’s goals achieved. Our Project Managers coordinate the multiple components of a project to set schedules, evaluate progress, offer solutions to problems that arise and review product quality.  Careful planning ensures the creation, delivery and implementation of projects occur on time and within budget. 
   
   
6. Research
   This step is about asking questions and gathering information to insure the success of the project. Since a Web application is generally an extension of a client’s business strategy, it is important to learn as much as possible about the client. The goal of the research phase is to understand your needs to successfully bring Webability to your business. 
   
   
7. Establish Measurable Goals
   After the specific objectives of a Web application are determined, then we can establish measurable goals to determine the application’s success. There are quantitative and qualitative means to determining success, such as tracking client usage, tracking costs or evaluating client satisfaction. Regardless of the method used, it is important to develop the application with the client’s goals in mind.
   
   Defining the application’s goals upfront will prevent the project from wandering off course and becoming something that is beyond the scope of the proposal.
   
   
8. Identify Milestones
   To ensure the Project Plan stays on course, it is necessary to outline a set of milestones that will be reached during the development phase. These milestones are deliverable components of the project.  Azavar’s milestone-based process methodology is discussed further below. They may be small steps in development or they may be a complete phase of an ongoing project. Creating milestones allows the development to be broken up into parts; sections or groups can be addressed individually through the design process. This allows the client to track the progress of the project through fixed deliverables. 
   
   
9. Organize Content
   For planning purposes, it is important to identify all of the content information and graphics resources that will need to be collected to achieve the goals of the application. In most cases, content means information, but it could also be high quality graphics, streaming media, online presentations or other interactive components. The Project Plan will be greatly affected by when content is received and in what format the content is received.  Therefore, it must be clear what information is going to be included within the application, and how that information will be collected. For example, what images are needed? On what media will they be stored? What will be the file format?
   
   
10. Identify Risks
    Once the project’s milestones are established, the risks associated with the product must be identified. The risks are anything that will negatively affect the project. The result may be missed milestones, poor data quality or an incomplete project.
    
    Proper risk management identifies risks before they occur and ensures the Project Plan allows flexibility to deal with the risks during the project. It also helps to create contingency plans that meet the client’s needs.
    
    
11. Create Project Plan
    The Project Plan is a schedule of the activities necessary to successfully complete the project. Among other things, it specifies what activities will take place and when deliverable components will be completed. Understanding what is due and when it is due keeps a project moving forward. The Project Plan should contain enough information and detail to accurately describe the project to both the client and the development team.

Included in the Project Plan is a creative brief. The creative brief is used to establish high-level visual and conceptual goals. It generally restates our grasp of the project as a whole – the target audience, the user experience, the Web application’s goals and communication strategy. This is designed to bridge the gap between client expectations and creative direction.

The Project Plan also includes a technical brief that documents the project’s requirements. The technical brief outlines the technology to be used and how it will be applied to the application. It conveys our understanding of the project from a technical level. What are the user’s requirements for browser, platform and connection speeds? Are there technologies that may pose potential problems down the road?

There are four major factors that affect a project: Scope, Timeline, Cost and Quality. Scope is the aggregate of all the elements required to complete a project.  Timeline is scheduled restraints within which the project must be developed. Cost is the expense budgeted for the project's development. Quality is the value a client finds in the execution of a project. The Project Plan balances these factors within the constraints of each area and the client's priorities to create a plan of action for the project's development.

Next Step: Design >

1. Discover
2. Design
3. Develop
4. Deploy
5. Manage