Management

NeedBeyond focuses on key solutions based on a Business Model approach, to help brands achieve their vision. All projects are implemented using an iterative, milestone-driven process, based upon a series of versioned releases conforming to the 4-implementation phases that we have defined. This time tested framework for developing Intranets and other applications would ensure timely implementation of a system, which meets its objectives.

The advantages of taking this approach are many:
- Project delivery is streamlined
- User acceptance is high as they get used to using the system gradually
- Ability to incorporate changes with minimum efforts
The following are the four critical phases and milestones that are fundamental to the approach.

Fancying
The purpose of the Fancying Phase is to build a shared vision of the project among all the key stakeholders. By creating a broad but intuitive view of the project's goals and constraints, the Fancying Phase begins to define the scope of the project, and sets the stage for the more formal and detailed planning effort that will come later, in the Planning Phase. The fancying phase culminates in the Vision Approved Milestone. The deliverables of this milestone are:
- Vision Document
- Master Risk Assessment Document
- Project Structure Document

Planning
The application's architecture is defined during the Planning Phase. The application architecture is based on the Conceptual, Logical, and Physical Design Models. This phase culminates in the Project Plan Approved milestone the deliverables of which are:
- The Functional Specification.
- The Master Project Plan.
- The Master Project Schedule.
- An updated Master Risk Assessment Document.

Developing
The goal of the Developing Phase is to deliver an application that meets all stated expectations and is ready for external testing. This phase culminates in the Scope Complete milestone the deliverables of which are:
- A revised and completed Functional Specification.
- An updated Master Project Plan and Master Project Schedule.
- An updated Master Risk Assessment Document.
- Source code and executables.
- Initial performance support elements.
- A Test Specification and test cases.

Bracing
During this phase, all known issues are resolved before delivery, and any tasks needed for support and ongoing maintenance of the product are completed. This phase seeks to tie up the loose ends. Documentation, release notes, final "bug fixing" and project deployment are all part of this phase. A significant aspect of this phase is that the customer and users begin significant testing of the system.
This phase culminates in the Release milestone the deliverables of which are
- Release notes.
- Performance support elements.
- Test results and testing tools.
- Source code and executables.
- Project documents.