When Mary and Eileen came to us, they thought their previous developer had gotten the site maybe eighty percent there. There were missing images, missing content, some layout and navigational issues, and came with a fairly lengthy list of change requests. It needed to integrate with a payment processor and events plugin and had been developed on WordPress. We knew we could help.
First, we got all of the change requests set up in our project management tool, Teamwork, so we could all see and track exactly what was to be done, how long it was taking, and what was left to do. This transparency allowed Mary and Eileen to decide where to allocate resources and kept Team BlueChanel organized. The biggest challenge inheriting a project from someone else is the organization of all the assets, requests, credentials, etc. and determining what the priorities are for launch. Once we had everything in Teamwork, things began to smooth out. We don’t let things slip through the cracks.
We moved the development site over to our servers and began ticking off the tasks from the list. For this project, we didn’t draw the clients’ attention to incremental launches, but instead allowed them to peruse the site as we developed so they could see holes in content, placeholder images, play with navigation, etc. As they noticed issues or elements they wanted changed, they communicated to us via phone or email and we added new tasks to Teamwork.
Because we use Teamwork and time spent is logged, we were able to let Mary and Eileen know every step of the way where they stood against their budget.