Considerations as Projects are Scoped pre-sales-considerations

A typical stakeholder for this activity is a Marketing/Business Strategist.

This stage includes all pre-sales and discovery efforts required to define the project scope fully. The work done during Day Zero sets the tone for the rest of the project and influences the overall success of the application being built.
At this stage, key vendors are identified and brought together to help formulate the project plan. It is important during this stage that buy-in is also established with key project stakeholders within the client company. These stakeholders include sales executives, marketing managers, and IT teams. These people all have an important part to play in the development of the application and its continued maintenance.

Key Deliverables key-deliverables

Key deliverables at this stage include:

  • Approved project plan (including scope of work, project schedule, and budget) with buy-in from key stakeholders.
  • Defined teams with clear roles and responsibilities.
  • Defined content strategy with short- and mid-term goals and a long-term vision.
  • List of reporting needs and key performance indicators (KPIs).
  • Draft deployment schedule and plan.
Identify the data that is needed for the application, and where it is coming from, as soon as possible. Deeper exploration happens during implementation. However, be sure you take time during Day Zero to find out what data the client intends to use. Find out where that data is stored currently, and how the application being built can access it. Notifying the development team before challenges arise helps to make an implementation go more smoothly.

Watch the video Considerations as Projects are Scoped.