Webb Consulting’s Project Methodology
Webb Consulting recognizes that in order to produce the best results for a project, the right tools need to be in place. Webb Consulting fully utilizes and endorses tools such as Microsoft Office and Project. In addition, Webb Consulting has developed their own internal project tracking applications that are visible and can be updated over the web. This database is easily customized to meet each client needs.
Webb Consulting recognizes the need to meet both our internal and external quality requirements and we have the following view on quality control.
Quality is a responsibility shared by everyone involved in the project.
During the analysis and design process all shortcomings are highlighted and corrective action is taken. The process continues throughout the life of the project. In order to maintain the standard of quality defined by both our clients and Webb Consulting, documentation is an integral aspect of our development methodology.
At each phase outlined within our methodology various deliverables are defined that ensure the development team has information it needs to successfully meet milestones defined by the project plan. Included in the documentation deliverables promoting quality assurance are:
- Business Requirements
- Functional Specifications
- User Interface Design Specifications
- Technical Design Specifications
- Project Plan
- Application Test Plan
- Application Documentation
To ensure successful project completion and complete client satisfaction, Webb Consulting recognizes that quality assurance needs to be present and put in place as soon as the project is initiated. This is cornerstone to our Methodology.
Project Planning Methodology
Stage 1: Identify the work breakdown structure
- Develop list of all identified tasks within the different project phases
- Identify and list all task dependencies
- Attach effort in man-days of each week
- Associate the milestones to each task
Stage 2: Building Project Model
- Identify the type and number of resources needed
- Assign already defined tasks to each of the resources
- Identify the projects critical path(s)
Stage 3: Develop Contingencies
Assess each task with respect to functionality, delivery date, effort, and quality and build in contingencies to the plan.
Stage 4: Assessing Project Scope
- Identify the achievable scope by analyzing all the tasks? functionality, delivery dates, and quality with respect to the business? requirements
- Refine contingency for tasks
- Refine project critical paths
- Create project base line
- Extract major milestones defining the project plan
Stage 5: Project Development
- Daily Management
- Check schedules to ensure development team and clients meet deadlines
- Check progress of application(s)
Stage 6: Weekly Management
- Confirm tasks and deadlines with teams and client
- Send meeting agendas to client for their additions
- Brief team on project developments in weekly meetings
- Cross review and confirm individual roles, tasks and schedules
- Ensure tasks are delivered to standards and methodology