I was wondering if anyone would be able to share a recent eBusiness project plan in Microsoft Project file format?
I am currently beginning implementation planning for building a commerce site and would like to see what most plans look like. I am most interested in e-commerce technologies such as a personalization system, content management system, and more... Saving Changes...
Sort By:
Anonymous
Would somebody please share the workbreakdown structure for a BroadVision, ATG, Interwoven, or Vignette project?
My understanding of WBS--a deliverables-oriented graphic of the project scope. WBS is not a project schedule, that comes later. Anyway, there's more required than a WBS. IT is a different animal, much more risk, less control, etc. Check out the books on the PMI website--www.pmi.org. You will need a book for background info and terminology. You will also need a methodology. It doesn't sound like you have anyone else around you with experience in this, so you will have to find one that works for you. Make sure it includes 'walkthroughs' (work product reviews) and sign-offs. The biggest problem with IT is that the Requirements are not well-defined up front. So you will need a document containing explicit, measurable and testable descriptions of what the system or application is supposed to do, what it should look like, who will use it, how it connects to other applications, etc. After that you must document the proposed design for the system--what platform it will run on, which functions will be housed in which software modules or programs, what language it will be created in. Again, the design must show how it will meet the requirements. The next 'deliverable' is the code itself, unit-tested modules. Again, the walkthrough must demonstrate how the code will meet the requirements. After the code is approved and signed off, the various methodologies part company. Most require proof of further testing to ensure the software continues to meet the requirements. User testing, in the environment most like the expected production environment as possible, is an absolute must. Testing (and changes to the code) continue until the ultimate customers (users) agree that the software meets the requirements, usually by viewing print-outs, input files, output files, reports, etc. that show this. Those print-outs, or formal test results documents, are considered a deliverable also.
Build your MS PRoject schedule from these deliverables and you will be on your way. Sorry for the long response. Good luck! Saving Changes...
I've got a number of Internet application MS Project files I could share, including an assessment phase that we have been using quite successfully. It would help me to help out if I had a better feel for what is needed, though. Saving Changes...
