Ever wondered how successful projects are born? With an elaborate ecommerce website development project plan.
Project management has five phases, and project definition & planning is probably one of the most important ones. After the discovery and initiation phase is done and your website specification document is all ready, it’s time to prepare the ecommerce website scope of work and a general project roadmap for your team to follow.
At Elogic, we know that well planned is half done, so we get very scrupulous when it comes to this second phase of project management. Having put on a planner’s hat, we develop the timeline, budget, and work breakdown structure for ecommerce websites. We even try to foresee the plans that are not in plans just yet.
Read this article on our approach to website project planning and learn how to estimate and implement a lasting ecommerce project.
Terminology can be confusing. And before we get down to a planning process, it’s important to distinguish between three absolutely different project documents: project plan, project scope, and project roadmap.
Ecommerce website development project plan includes all working documentation required to fulfill a project. Divided in sections, it lists the stakeholders’ roles and names, the schedule and duration of the project, the budget allocated for each step, project risks and assumptions, change request management, and more. It basically encompasses all the other documents established for the project and should be your reference point during the execution of a project.
Ecommerce website scope of work defines the project purpose, deliverables, and major known risks and constraints. It lays out the basic information to start an ecommerce business and is less detailed than a project plan. A project scope may be a stand-alone document to start the planning phase or form a part of a project charter filled and signed at the initiation phase of project management.
Ecommerce website roadmap provides a strategic overview of the project execution, with its major milestones and the time for realization. It is usually structured as a diagram and keeps a merchant informed on the project’s progress.
If these definitions sound new for you, why not share them with your project manager? Click below to share the article on social media.
In one of it’s whitepapers, the Project Management Institute (PMI) reports that Intel has “90 percent of projects hit their release dates or went over by just a few days, and the IT department is delivering more projects per year on roughly the same budget as before”.
Intel’s case basically summarizes all the implied benefits of the planning process. Apart from creating the essential project documentation (like the one listed above), this phase is important for several reasons:
Ironing out the project details before you actually begin it will help you make ecommerce development — be it replatforming, integration, or any other development service — as painless as possible.
Once we have the brief filled in and the discovery phase finished, we start planning the project. Ecommerce website development project plan involves five steps on the way to project estimation and implementation. We add a bonus step upon our clients’ request following PMI best practices. Read on!
A scope statement is the first general outline of the project that gives rise to the rest of the working documentation. It can be changed along the project but is initially created by a project manager and all involved stakeholders.
Ecommerce website scope of work typically consists of the following sections:
Project Purpose / Business Justification — a brief description of the project and reasons for its implementation.
Objectives — a breakdown of the expected outcomes of a project. It’s important to be specific at this point, so businesses are advised to take advantage of a SMART or a CLEAR model to articulate the goals. Both are acronyms and, depending on your business focus, allow you to set attainable, measurable goals that will keep your project and employees right on track.
Deliverables — all the assets that a development team is committed to deliver throughout the project. This part includes all the project-related documentation to be delivered as well as services to be provided (e.g., website development from scratch, ecommerce replatforming, third-party integration, etc.).
Scope — a list of high-level units and tasks to be executed throughout the project. It’s basically a predecessor of a WBS to be completed in the next step of planning.
Project milestones — the important tasks and achievements that mark a certain stage of the project completion. They are predecessors of a project timeline and represent a clear sequence of events showing how the project advances.
Major known risks — external conditions that may adversely affect a project’s progress. The likelihood of each risk occurring and the severity of its risk should be estimated at this point.
Constraints — restrictions defining a project’s limits (e.g., budget, schedule, dependency on third-party software releases, etc.). These may also include the external dependencies — activities and tasks outside the team’s control — that may affect the project implementation.
A work breakdown structure (WBS) for an ecommerce website is a visual, hierarchical deconstruction of a project. It is built based on our clients’ requirements in three simple steps:
This way, a WBS breaks a large project down into smaller, chewable chunks of work to be done.
Take a look at the example of a work breakdown structure for an ecommerce website: the final deliverables stay on top of the tree diagram, while all subdivisions refer to manageable tasks to be assigned to a single person.
Why use a WBS? For starters, because it’s physically impossible for a single project manager to consider all the tasks to be done, especially on large projects. A WBS keeps the work organized and doesn’t let any tasks escape one’s attention.
A WBS also acts as an ecommerce website roadmap. It helps a team to keep up with the project deadlines and mitigate the potential risks of cost overrun and scope creep.
Now, as your project has been broken down into smaller pieces, you can go ahead and create an ecommerce website roadmap, a to-do list for each work package. But here’s the thing that slips the mind of many inexperienced project managers: dependencies.
Project dependencies refer to the logical relationships between the tasks in which one task or activity depends on the completion or initiation of another.
Indeed, some tasks will be completed at the same time, whilst others won’t start until another ends. A project manager should recognize the order in which the tasks specified in a WBS should be done and write them down into a dependency log.
Studying project dependencies has a number of important implications:
Once your project deliverables have been mapped out and dependencies established, you can set your project timeline. At Elogic, we build and present a project timeline using a Gantt chart.
A Gantt chart puts the dependencies and resources identified in the previous steps of the planning journey in a single bar chart. It presents a visually clear view of the time you allocated to each task as well as their dependencies.
The vertical axis of the chart stands for the tasks to be completed, whereas the horizontal axis — for the time allocated. The chart also shows the start and finish date of the project, the duration of each task, and the way in which tasks group together, overlap, and link with one another. We also further subdivide the tasks into periods called sprints that end with each achieved milestone.
Most ecommerce website roadmaps are created in Excel or using project scheduling software (teamgantt is our personal favorite at Elogic). In fact, the latter have become so popular for their shareable and collaborative features, like real-time comments, task updates, and task assignment to a team member, among others.
Whatever approach to creating a timeline you choose, remember to stay specific and don’t be afraid to customize it as per your project requirements!
The last issue to resolve before your project goes into the implementation phase is the budget. At Elogic, we understand the value of your money and prepare two budget estimation documents based on a work breakdown structure for an ecommerce website and a timeline.
First, we specify the cost of each increment in WBS. All the tasks are written out in a spreadsheet along with the time allocated to complete them and the cost per task. In this raw estimate, we also indicate the hidden costs of module development and after-launch support. Non-essential tasks are also marked, so that our client can adjust the budget by adding or eliminating the requirements.
Second, we prepare the calendar of payments as per the project timeline. As per Agile project implementation model, we organize all tasks into sprints at the end of which we report to the customer the completed milestones and results. As such, our client pays for what they receive within a set period of time.
Creating two types of estimate documents will allow a client to get a clear picture of the costs involved in project implementation as well as twist and tweak the tasks and timeframes to adjust the budget.
Good news for those who choose Elogic! Upon our clients’ request, we form a full project plan following PMI best practices.
Here are the practices we follow to ensure the project planning phase ends in a tip-top manner:
By the end of the project planning phase, our client receives a full, detailed ecommerce website development project plan specifying what, when, and how our work will be delivered.