Skip to content

Planning and Delivery

Overview

This section outlines a proposed timeline and approach for delivering Conference Expo Portal v2.0. The plan is indicative only and will be finalised after the specification phase is complete. All durations are given in weeks, as the actual start date is to be confirmed. The overall process is expected to take 4–6 months, including specification, development, testing, and rollout.

Proposed Timeline (Example)

Phase Activities Duration (weeks)
Specification Finalise requirements, technical design, UI/UX, planning 4
Development: Core Build core features (user management, events, stands, artwork) 8
Development: Extras Integrations, reporting, admin tools, polish 4
Testing & QA Automated/manual testing, bug fixing, UAT 4
Rollout & Training Production setup, migration, training, go-live support 2
Total 18–26
  • Some phases may overlap (e.g. testing can begin before all development is complete).
  • Weekly review calls will be held to monitor progress and adjust plans as needed.
  • The timeline will be updated and finalised after the specification phase.

Milestones

  • Requirements and specification sign-off
  • Core feature completion
  • Integrations and reporting complete
  • User acceptance testing (UAT) complete
  • Production go-live

Resource Requirements

  • Backend developer
  • Frontend developer
  • Project management and QA responsibilities will be shared between the development team
  • Stakeholder representatives (for feedback and UAT)

Risk Assessment

  • Timeline is indicative and may change based on requirements or feedback
  • Resource availability and external dependencies may impact delivery
  • Early and regular feedback will help mitigate risks

Success Metrics

  • On-time delivery of agreed features
  • User acceptance and positive feedback
  • System stability and performance targets met
  • Smooth rollout and adoption

Budget Estimate

The proposed budget for the delivery of Conference Expo Portal v2.0 is £30,000 (excluding VAT and third-party costs). This is based on:

  • A two-person team (backend and frontend developer)
  • A total of approximately 416 hours at a blended rate of £72 per hour

The allocation of effort will vary throughout the project, with more focus on backend/API development in the early phases, increased frontend integration later, and periods of reduced activity during client acceptance testing or feedback cycles. The budget is expected to be sufficient for the delivery of the agreed scope, given the team's prior experience with the v1 portal and established domain knowledge. The budget will be reviewed and adjusted if the scope changes significantly during the specification phase.

This plan is a starting point and will be refined as the project progresses.