I've never been a project manager and now I've been given a project to manage, YIKES! I'm responsible for the implementation of a packaged software system in an R&D environment. I've been asking everyone I know what I should be doing and I've been referred to books dealing with software/information systems project management. These are good books but they focus more on managing the development of systems. The system I'm working on is already developed, I'm supposed to manage its implementation.
Does anyone have any books/articles/references/guidance/words of wisdom that will guide me (a novice!) through this process? HELP! Saving Changes...
I have MANY references that could help (even for R&D PM). Send me an email, and I will supply you with electronic copies, or references.
P.S, this is the best way to learn (also that Project Management does not apply very well to the R&D environment) - A Project, be definition has
1. A defined scope, 2. A defined budget (money, resources, etc) to deliver the scope defined in 1. 3. A specific time frame to complete 1., using 2. Saving Changes...
Sorry, I missed the point of your post a bit: You will be managing an implementation, not R&D. The point I was trying to make was that PM is hard to implement in the classical manner in R&D, because of the definition that I re-stated (These constraints are not always practical in R&D).
Software implementation is a bit easier, as it is mainly a 'mechanical' process.
The factor that complicates the 'roll-out' type of project is People. You will be changing the manner in which they (the recipients, or users) work, and the developers are not always too sensitive about what the users actually needed in the first place - this gives rise to resistance in most cases.
My best advice is to engage a consultant or a contract project manager that has experience in this area, as an assistant (if you want to learn) or to run the project. This is particulariy effective if you are able to set up a 'Project Review Board', with yourself chairing it, if possible (theoreticaly, the organisational sponsor of the project should chair this board though). Saving Changes...
Anonymous
I have experience in software implementation and currently a Project Manager for Deployment. Email me for more detailed information [email protected] I would be glad to help out. Saving Changes...
Anonymous
Hi All,
I would like your thoughts on the interrelationship between a project's WBS and the Requirements documents of a typical software development project. I'm unsure of where one ends and the other one takes over.
The obvious answer is that there must be some entity in the WBS that assures the delivery of the requirements required.
The problem I see with the execution of traditional hierarchical WBSs is that there is no assurance of identifying dependencies across the legs of the hierarchy. In the critical chain world, we prefer to build our WBS coincident with building a dependency network, by starting with the key objectives, deliverables, and success criteria, and working back through what is needed to deliver them and their predecessors, and their predecesors, and their predecessors, . . .
If you want to deliver a requirement, you need a task or more likely a chain of tasks, or even more likely, a network of tasks that guides you in building it.
Saving Changes...
Anonymous
I project manage implementations for a software/services vendor. Give me an email ([email protected]), I can share some insight and tricks. Communication is the key! Saving Changes...
I do exactly what you are going to do, manage software implementations, re-engineering, change & all other aspects of implementation. E-mail me at [email protected], maybe I can help. Saving Changes...
I too am new at implementation projects. A Sr. Architect where I work gave me a great book on implementing projects - it is: RAPID DEVELOPMENT - Taming Wild Software Schedules written by Steve McConnell on Microsoft Press. He got it at Borders for around $35.00. It's well worth a look. It lists everything you should take into consideration when you're doing rapid development projects. Probably all won't apply to your specific project, but the basic concepts are sound. Also, it's in a very easy to read format. If you want to e-mail me to discuss further, please contact me at [email protected] Saving Changes...
Anonymous
I have been given the responsibility of managing a software package implementation project. Do you have a 'project management template for package imlementation, resources on conducting gap analysis etc?? Saving Changes...
