The challenge
I-COM handled multiple customer website projects, each with its own goals, scope and delivery expectations. Keeping those projects moving required clear agreements before development and consistent control once implementation started. Time and budget boundaries mattered, but so did the quality of the finished website and its fit with what the customer had originally asked to achieve.
A combined role
David worked as both project manager and web developer. He guided projects from early definition to final completion and remained directly involved in the websites being built. Combining those responsibilities created a short line between a customer decision and its technical consequences. It also meant delivery planning was informed by practical knowledge of the work rather than being managed at a distance.
Defining scope and objectives
At the start of each project, customer needs were translated into a clear scope and a set of concrete objectives. That included establishing the required functionality, identifying the resources involved and creating a realistic delivery path. Expectations had to be specific enough to guide development and visible enough to support later conversations about progress or change.
When new requests appeared, they could be considered against the agreed objectives, timing and budget instead of being added without understanding their impact.
Staying close to implementation
The websites used the web technologies of the period, including Classic ASP, SQL and jQuery. David contributed directly to that implementation while coordinating the wider project. Hands-on involvement made technical progress and constraints immediately visible and allowed questions to be resolved with the developers and customer context in the same conversation.
This connection also supported quality: delivered behaviour could be checked against the requirement that had motivated it rather than only against an isolated task description.
Coordinating delivery
Progress was followed against the planned milestones, scope and available budget. Communication kept customers aware of where a project stood and gave the implementation work a clear priority order. The aim was not to make planning rigid, but to ensure that changes were deliberate and that the work required for completion remained understood by everyone involved.
One line of responsibility reduced the chance that project coordination and technical execution would drift apart.
Result
I-COM’s web projects were managed through a connected process from definition to implementation and completion. Customers had an accountable contact who understood both their objectives and the technical work, while development stayed tied to agreed scope, timing and budget. The experience established an approach in which project leadership and practical delivery reinforced each other rather than operating as separate disciplines.