Hi i am just getting involved with an organisation that rolls out CRM.
Currently they are not using a methodology for the rollout projects and are in a bit of a fix.
Microsoft offer their own methodology called "Sure Step" which we will eventually adopt. But for now i would like to implement a basic "emergency" plan to record the basics required.
So far I have come up with.
a. Business Case (Benefits - measurable)
b. Project Team
c. Risk Register
d. Work Breakdown Structure
e. Schedule (Gannt?)
f. Post-Implementation Review and Lessons Learned
Did I miss anything obvious. Bearing in mind anything is going to be a huge improvement on what we already have Saving Changes...
Sort By:
Taralyn Frasqueri-MolinaSenior Project Manager| Independent ContractorPasadena, Ca, United States
If you want to keep it small:
- After Business Case, I recommend adding in Scope Statement, which will include creating a document that, at the very least, lists deliverables, their requirements and exclusions (things that won't be delivered).
- After WBS, I recommend adding in Contracting/Procurement, unless you guys don't use contractors or you don't buy anything. Saving Changes...
Yvonne ParleEast Victoria Park, Western Australia, Australia
Hi Iain
What fun to be able to make such big improvements for your organisation! I would suggest you put in some kind or change control system to help make the changes you implement "stick" in the short term and to help you migrate to Sure Step when the time arrives.
Thomas OldOwner| Alta Vista ConsultingMeridian, Id, United States
A good start.
I always like to see a tool like a RACI model -- this helps the team understand what they have to do and who does what. Saving Changes...
Peter WrightProgramme Manager| BAE SystemsSouthport, Merseyside, United Kingdom
Iain,
I agree with Taralyn for the scope statement this will ensure you can control the project. A project initiation document can do this so it can expand on the business case but not be as detailed as the WBS.
is your company responsible for generating what the product will do (e.g. from product managers) or do you also obtain requirements from customers/users?
Either way how are you tracking those requirements, converting them to use cases etc and where is all this being recorded. Therefore one item that could be included is Requirements Traceability from cradle to test to user acceptance. this can be implemented as a matrix "*.xls" or wiki.
I would also not have f as just post implementation review/Lessons learned. Have LL continuing to be reviewed throughout the project at your daily stand ups or weekly project reviews with the team.
Also for your risk register I would include a PerformanceTimeCost metric measurement sheet to quantify the risks you are logging in your register. this will assist you in correctly prioritising your risks. I have a RAID log which may assist you in the short term for some of these items. https://www.box.net/shared/3osfk1x7na.
Hi Peter thanks a lot for your input.
The projects are typically 10 - 30 days
I downloaded your spreadsheet.
Initially I thought WOW! this is complex but noticed quite quickly that you had created a nice step by step guide to filling it in. You certainly have put a lot of work into the file Peter.
My thoughts are that I could do with a slimmed down version of your RAID log. I may create something based on your ideas.
Many, many thanks for your input Saving Changes...
Sylvie EdwardsProfessor/Program coordinator| Durham College (DC)Whitby, Ontario, Canada
There are a couple of things that I would add:
1. a quick and dirty stakeholder listing (I do one in an onion skin type diagram with the closest to the project's objectives or center going to the furthest). That will assist you with figuring out requirements and communications needs for the project.
2. I would also try to figure out early two major processes: issue management and change management (what is needed, how will you do it, etc...) That will give you time once documented to focus on what needs to be rather than how to do it. Saving Changes...
