PROVEN PROCESS – ROADMAP TO SUCCESS
Here at BIT, we understand that every company is unique, has specific goals, messages, and business positions that cannot be addressed with "cookie cutter" solutions.
Our process, although clearly defined, is flexible enough to meet the needs of a wide range of projects and customers. Because the overall process is cyclic (or iterative), it can have several cycles of phases. Phases can sometimes overlap.
By following the key steps in these seven phases, we are able to mitigate common risks, achieve your business goals, and meet the needs of each and every user.
Phase 1: Introduction
|
|
Before anything great can begin, we must first understand the current environment, situation and needs of our client. At BIT, during this first phase we sit down with our clients and get to know them, listening, asking questions and taking notes. From this first phase we are able to produce a Statement of Work with some initial recommendations.
|
Activities
|
Deliverables
|
|
|
-
Statement of Work
-
High Level Strategy
|
Phase 2: Discovery |
|
During the Discovery phase, we work closely together with you to establish the business case for the project, clarify your goals and objectives, assess your audience needs, build a strategy for positioning your company for the online environment and outline the project scope.
|
Activities |
Deliverables |
- Create a business case
- Capture requirements
- Competitor Review
- Scope the system
- Identify critical risks
- Project Cost Estimation
|
- Proposal
- Detailed Requirements
- Use Cases
|
Phase 3: Analysis |
|
We take all gathered information and analyze our findings in order to formulate the best site design strategy, including high-level site architecture, creative, production, and technical considerations and recommendations.
These assessments and recommendations are housed in a Strategic Site Design Recommendation Document. All subsequent design and development decisions are based upon the direction established in this document.
|
Activities |
Deliverables |
- High level Architecture
- Create Project Plan
|
- Architecture Document
- Project Plan
|
Phase 4: Design |
|
Once we have agreed upon an overall strategy and direction, we work to establish the framework for the site from a functional, creative, and technical perspective. This framework will serve as the roadmap for all design, technical, and production efforts during the development phase.
During this phase, BIT produces documentation and preliminary designs, specifying all content, functionality, navigation, and overall look/feel.
|
Activities |
Deliverables |
- Preliminary Design Creation
- Information Architecture
- Functionality Outline
- Navigational Structure
- User Interface Design
- Prototype Development
|
- Preliminary Design Mockups
- Information Architecture Doc
- Functional Specifications
- Navigational Structure Spec
- User Interface Design
- Prototype
|
Phase 5: Development |
|
Once the framework has been established, we build your system/site.
This is when it all comes together. When documents are translated into actual live pages. All functionality is built but QA testing is not finished.
|
Activities |
Deliverables |
|
|
|
Phase 6: Testing |
|
In order to build systems/sites that work, you must put them through the wringer. During this phase, our Dedicated Quality Assurance department confirms that everything works as specified and gives it the Common Sense test as well.
A project that has undergone a thorough QA test cycle has a much higher success ration than a project without appropriate QA. A focused QA initiative results in a much more positive experience for the end-user.
|
Activities |
Deliverables |
|
|
|
Phase 7: Deployment |
|
Many people think System or Site Deployment is just a flip of a switch. Turn it on and Bingo, it’s all done. At BIT, Deployment is a phase. We don't walk away the day your project goes live. We continue testing and monitoring efforts and make sure it all runs smoothly.
|
Activities |
Deliverables |
|
|
- An Efficient System/Site
- Peace of Mind
|
Phase 8: Maintenance, Hosting & Support |
|
Work doesn't stop on a Web Application after Deployment. With every hosting package that BIT offers, there are built in monthly support hours to ensure that your system or site is up to date, tuned and working hard for our clients.
During this time, BIT is constantly monitoring the production environment for optimal performance. And our Web Analytics offerings leverage the Web's valuable ability to preserve site visitors' footprints, allowing the client to make informed decisions about future site enhancements.
|
Activities |
Deliverables |
- Hosting
- Support
- Maintenance
|
- Systems/Sites that Work
- System/Site Reliance
- Analytics
|
Project Environment
When necessary, BIT sets up a CVS or MS VSS system to coordinate project artifacts. When necessary, BIT sets up remote access to enable demonstrations or testing of the software in the customer’s environment.
Customer communication/ Project tracking
- Daily emails/chats/phone calls to discuss technical issues (requirements, architecture, etc).
- Weekly emails/chats/calls to discuss the current project status.
- Monthly or on demand emails/phone calls to discuss the partnership, oversee the past month and make decisions on the development process, project configuration, etc.
- Submit periodical or on demand project updates (time spent reports, update of the project plan, weekly status reports).
Quality Assurance
Quality control activities are performed continually throughout all project phases to verify that project management and project deliverables are of the highest quality.
At BIT, we use:
-
Templates & Guidelines
Standardized templates are used for all types of project documents. Using templates allows creating comprehensive easy-to-read documents. Guidelines are used in the development process to assist in creating quality project deliverables. Guidelines can be cross-industry and corporate.
-
Formal Testing & Acceptance
To ensure high quality of deliverables, testing and acceptance criteria for every deliverable and project phase are established. Acceptance criteria must comply with industry and corporate guidelines.
-
Peer Reviews
In a peer review, colleagues of the creator of a particular software work product examine the product to identify defects and correct possible flaws.
All interim and final development work products are candidates for review, including requirements specifications, architecture design, or source code.
-
Change & Configuration Management
Configuration Management is a supporting process whose purpose is to identify, define, and baseline items; control modifications and releases of those items; report and record status of the items and modification requests; ensure completeness, consistency, and correctness of the items; control storage, handling, and delivery of the items. By implementing Change and Configuration Management practices, quality of the deliverables is controlled.
|  |
|
