Case Study 1: Affiliate Project

« « Planning - Write It Down | Case Study 1: Affiliate Project: Initiation » »

Saturday, February 9th, 2008 Subscribe To Our Feed

I’ve been thinking long and hard about how I can best help you to understand the importance of using project management techniques in your internet marketing projects. Well, I think the best way possible for me to show you how to use these techniques is to actually show you how I am using these techniques to run my own internet marketing projects.

And that’s exactly what I have decided to do. I’ve decided that it’s time to unveil exactly how I go about implementing, planing, executing, monitoring and controlling and then closing my projects. And the best part for you is that I will make all of the documents and information available to you. The one thing I will not do (at least at this point) is reveal the niche in which I am working. I don’t think this detail will be relevant, but I guess we will see as we move along.

So, the first thing I do, when determining a project is to determine which projects I have on the table to pick from. I always have a list of projects I keep to ensure that when I finish one I am ready to move into the next project, and as I think of new projects I add them to this list.

OK, I’ve decided among the projects I have on my list, and the one I determined I am calling my affiliate project. Now, this is not the first project I’ve done with this title. And it won’t be the last. But the title of the project is almost irrelevant. The most important thing is that the title lets you know what it is your project is intended to do. And that’s what this title does for me. The project is intended to find profitable affiliate products, and promote them through some proven methods.

The first document that I will be posting for this project is the work breakdown structure (WBS). The WBS is a document that takes the tasks involved in a project and breaks them down into specific work units. Essentially breaking them down into the smallest piece that can be tracked. This is essentially the task list for the project, although it can often be more than that. Because this is the fist time I am running through an actual project, this WBS will be essentially a task list. In the future I will endeavor to show you what more this can be.

Before I post the documents for this project, I think I should go over the process I use to initiate a project. I will post some information about that process tomorrow, detailing how I look through my project list and make a determination about which will go next.

Then I will post the WBS for this project. That should be on Monday. After that is posted, I will be posting a project schedule document, and some of my other planning documents. I’ll also include a post or two about how I develop my planning documents. Then we will be ready to begin execution.

At that point, I will go through what I am doing to execute the project, and of course monitoring and controlling will play a major role as we go through this portion. I’ll finally show you what I do for a closure process, especially since it is likely that at least some portion of this will require ongoing support. Therefore closure will occur by moving project management into operations.

I guess that’s enough for today. I’ll be back tomorrow with information about this project’s initiation process.

Chris

Get Social, Bookmark Us!!:These icons link to social bookmarking sites where readers can share and discover new web pages.