I get inconsistent descriptions such as "to manage a portfolio of Cloud-based initiatives, including Telephony, Backups, and Remote Management. Please advise in simple terms the day-to-day description of the Job.
1. Requirements analysis & evaluation
2. Recommending IT components that best meets the requirement
3. Continuously working on improvements and suggesting upgrades
4. Prepare cost estimates, monitor & control budget
5. Supervision to staff, vendors, suppliers & partners
...
2 replies by Katherine Willis-Rice and Rajan Hariramabadran Varada
Oct 25, 2016 7:15 AM
Rajan Hariramabadran Varada
...
Thank You!
Oct 01, 2019 11:29 AM
Katherine Willis-Rice
...
Thank you.
Are you still an Infrastructure PM? I am managing my first Infrastructure project and want to make sure that I am up to speed - so any recommendations would be very helpful.
1. Requirements analysis & evaluation
2. Recommending IT components that best meets the requirement
3. Continuously working on improvements and suggesting upgrades
4. Prepare cost estimates, monitor & control budget
5. Supervision to staff, vendors, suppliers & partners
Infrastructure is certainly pretty broad. You can expect to have provision and manage the following items:
* data center
* appliances
* processes
* staff
* suppliers
Infrastructure is certainly pretty broad. You can expect to have provision and manage the following items:
* data center
* appliances
* processes
* staff
* suppliers
Everyone else has picked up the main points. However, I will be interested to know how you get on with the project to roll out cloud based telephony, and how well it works especially re IVRs/customer self service etc.
Everyone else has picked up the main points. However, I will be interested to know how you get on with the project to roll out cloud based telephony, and how well it works especially re IVRs/customer self service etc.
Thanks Tim Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Sorry, but is a big mistake here. The duties are the same than inside any other type of domain. What you have to do, if you have no knowledge about infraestructure, is performing a critical but often missing activity: obtain knowledge about the domain. That implies that you have to make a reseach in order to understand: 1-what terms and process are used inside the domain? 2-which is the environment (external and internal) where that domain performs? 3-which are the key stakeholders and their concerns in that domain? 4-which type of solutions other organizations inside the domain are using?
Sorry, but is a big mistake here. The duties are the same than inside any other type of domain. What you have to do, if you have no knowledge about infraestructure, is performing a critical but often missing activity: obtain knowledge about the domain. That implies that you have to make a reseach in order to understand: 1-what terms and process are used inside the domain? 2-which is the environment (external and internal) where that domain performs? 3-which are the key stakeholders and their concerns in that domain? 4-which type of solutions other organizations inside the domain are using?
Thanks Sergio! Saving Changes...
Deepa KalangiManager, Program Management, Author, Trainer| CVS HealthCharlotte, NC, United States
Having just successfully deployed a large M&A infrastructure program, I can tell you these points. 1. First off, yes, the PM phases and duties remain the same. No question there. 2. The main difference you would see with an infra project vs others(traditional s/w dev) is the technical processes differ, terminology differs and mostly(90%), these projects are more erratic, less structured than others. 3. So as a PM, you are doing the same activities following your PMLC, however, you can expect more chaos, more complexity, less clarity and engagement from stakeholders.
Terminology- Data Centers, Devices(VOIP, Phones, POS machines), Environments(how they are built- with infra) etc.
