Hi everyone! I've been chosen as project manager for an IT implementation project, expected to last about one year. I'm new to more formal project management and so I hope to draw from you peoples' great body of experience.
In short, the IT-system is pretty much done, so my job will be centered about the implementation of the system, rather than the development. Productivity gains are expected and my job is to ensure they happen.
To get me started, can you recommend a suitable project life cycle for an IT-implementation project of this type?
Thanks a bunch and best regards,
Christian Saving Changes...
Sort By:
Ed Tsyitee JrConsultant | Consultant Tucson, Az, United States
I'd use the PDCA-Plan Do Check Act cycle. For example-
Plan-how long will each phase of the actual implementation take compared to the suggested time
Do-implement within the timeline
Check-did it work? Are there any bugs? How can the next phase be improved
Act-act on any opportunities to improve, mitigate any risks, and repeat.
I'd try to keep the life cycle as simple as possible.
I'd use the PDCA-Plan Do Check Act cycle. For example-
Plan-how long will each phase of the actual implementation take compared to the suggested time
Do-implement within the timeline
Check-did it work? Are there any bugs? How can the next phase be improved
Act-act on any opportunities to improve, mitigate any risks, and repeat.
I'd try to keep the life cycle as simple as possible.
Thanks Ed, I'll definitely read up on that! Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First of all, you are using the word "system" and it is critical success factor that "system" is not the software system. System is the set of components and relations. So, the first thing to take into account is what part of the system are you in charge to implement. Second, is not a matter of life cycle. Is a matter of taken into account you are implementing a solution. Here something that can help you, I hope: https://www.projectmanagement.com/blog-pos...-right-solution Saving Changes...
Can value be realized incrementally by phasing in the implementation of the system? If so, an iterative or even adaptive life cycle might be considered assuming there is buy-in from all appropriate stakeholders to this approach.
A lot will depend on the specific business processes impacted and what "current state" looks like. For example, if data migration is part of the scope of this project and the existing source/legacy data is very "dirty", you could find that consuming a tremendous amount of effort.
Depending on the magnitude of change between current and proposed procedures for staff, the organization change management effort might also be significant and a full OCM strategy, plan and tactics might be required.
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Christian,
if I understand you right, your task (implementation) is to bring the SW-System into production with the intended users. As Kiron wrote, this is a OCM type project (organizational change management) and it is focused on the users of the new system.
There are several frameworks that can be used, but in any case you have to build your own which suits your situation. A nice example is here https://projectresources.cdt.ca.gov/ocm/.
Also understand if the project needs to follow a greenfield or brownfield approach. With greenfield a proven practice is to remove (basically fire) all staff from their old job roles, define new roles and governance and let them all apply for the new jobs. Since your project takes a year, my guess it is greenfield. Brownfield means to only change the roles and skills one by one and it makes sure you have push back throughout the project, not only a big bang in the beginning.
You may want to seek advice from a subject matter expert to set it up.
Also, while you are introducing the IT System to the users, it may be that new requirements come up. Some may be deflected, some delayed but some probably need to be implemented in the SW. You have to control this process too.
And yes, there are expected benefits (productivity gains), so make sure you setup measurements (KPIs), baselines and targets, so you can prove your success against this metrics. Good practice I have seen is a monthly dashboard showing the progress on these KPIs. Saving Changes...
If I understand correctly: * the "system" is complete and ready for implementation, or will be soon * your role is to implement the system
My assumptions: * the expectation is that it will take a year to roll it out * it will be a phased implementation across multiple groups * end users will require training on the new system * some job functions may change
Am I close? The variables behind the implementation will, in part, drive your approach. For example, if the implementation is a repeatable process (at a high level, with the difference being what people are trained on), rolling out to multiple organizations, you won't get as much value from phasing in the system. If you're introducing something completely new, you might be able to realize some benefit from phasing in a module at a time. If you are replacing one ERP with another, for example, phasing in modules may be more difficult and provide less value because of the amount of effort needed to keep data synced between systems.
What is the nature of your implementation? Saving Changes...
Andrew SoswaTechnology leader| Leading global financial institutionElk Grove Village, Il, United States
So, many assumptions that need answers.
I'll throw another one - everyone assumes that all IT projects are equal and executed the same way (those who worked in IT know that they are not). Please specify what type of project was it (i.e. software, software with DB changes, software+DB+QA regression/new features, uplift/reformat of old system OR build out new system, +infrastructure (servers, user management), +network, + service desk (operational). The feedback depends on these specific details. Saving Changes...
@Sergio - very inspiring to use the EA view to look at the whole enterprise system and not just the IT and directly involved staff!
@Kiron - Good considerations :) I guess the impact is somewhat limited: The new IT-system will replace the current one, so staff, mainly HR staff, has to learn to use it and hopefully like it. We'll do a gradual phase in, where the first adopters will be the HR workers, and then the rest of the org.
@Thomas - Thanks for your insights and terminology! It'll be a "brownfield" approach, as only a minor part of the HR-staffs roles will be changed. And good idea to be ready to manage late-arriving requests. I'll check out the link for the CA government change programme to!
@Aaron - All your assumptions are correct! :) The system is a generic one that being rolled out across government institutions. The system is "local", so no need for all institutions to go live at exactly the same time. It's pretty much ready to use once data is migrated, albeit part of my project might be to integrate it with the other systems we're using. The project run time is projected to about a year, albeit a lot of that will be spend securing data and tweaking the system. Training staff and making the switch is about 4 months. Thanks for your many ideas about the different ways to implement. I'll look into whether it makes sense to do a phased implementation or not.
@Andrew - Great questions - especially because I don't have the answer! I'm new to IT and the many nuances you mentioned are still lost on me. I'll have to read up on the terms you mention and talk with the people delivering the software, to be able to answer.
Again, thank you all for your great insights and questions! Saving Changes...
Community Champion
