We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byElyssa Odgers
Modified over 6 years ago
Information Security Level 2 – Sensitive© 2009 – Proprietary and Confidential Information of Amdocs Recommend Friends Program
2 Information Security Level 2 – Sensitive© 2009 – Proprietary and Confidential Information of Amdocs Integration Manager (IM)- Delivery Who is Integration Manager? The Integration Manager is the person responsible for the overall functional solution delivered to the customer. The IM’s responsibilities include verification that the solution provided has real business value to our customer, is coherent, adheres to customer requirements, and is delivered at the level of quality expected by Amdocs’ customers. Overview on IM’s Roles & Responsibilities: > Leading the scoping session from the functional aspect. Assisted by relevant product experts from the DCC, Solution Architect group, and Business Analyst from ACD. > Defining the HL solution and the relevant Amdocs products that should be offered to the customer. > Being proficient in customer requirements, and verify that the proposed solution adheres to customer needs. > Being responsible, once BPM becomes available, for preparing the business processes that will be used during the scoping session and during the design stage (assisted by ACD, DCC, SA team). > Participating in the scope finalization with the customer/site. > Reviewing and approving the scope report. > Gathering performance requirements and expected KPIs for preparation of the TACT report (also known as DAD report).
3 Information Security Level 2 – Sensitive© 2009 – Proprietary and Confidential Information of Amdocs Required Skills for IM > An in-depth and thorough knowledge of Amdocs products from functional perspectives. > A good understanding of Amdocs business environment and culture. > Solution architectural abilities. > In-depth knowledge of customer needs, including understanding of customer oriented business processes, regulations, etc. > Experience in business analysis and understanding of software development environments. > Strong oral and written communication skills in English and the local language. > In-depth knowledge of Amdocs commitments to the customer. > In-depth knowledge of Amdocs development methodologies. Location: Pune/ Gurgaon Band: B4 Experience: 7- 13 Years
4 Information Security Level 2 – Sensitive© 2009 – Proprietary and Confidential Information of Amdocs Version Manager (Delivery) Who is VM? The version manager is responsible for all coordination and execution activities required to achieve quality and on-time delivery within budget. Responsibilities of VM include: The responsibilities of the Version Manager are distributed throughout the version life cycle, including Planning, Scoping, Design, Construct, Deploy, and Operate. Throughout the process, Configuration Management plays a major role, which influences version quality, deliver time, customer satisfaction, and budget.
5 Information Security Level 2 – Sensitive© 2009 – Proprietary and Confidential Information of Amdocs Skills Required to be a VM > Knowledge and leadership in overall version planning and management. > Knowledge of requirements management. > Configuration management expertise. > Customer centricity and customer management skills. > Strong documentation management experience. > An understanding of Amdocs product configuration. > Knowledge of version control tools and processes. Location: Pune/ Gurgaon Band: B4 Experience: 7- 13 Years
Implementation of ShipManagement Systems Project Management Prepared by Lana Al-Salem Director of Projects Management SpecTec Ltd.
PROGRAM AND PROJECT MANAGEMENT
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
<<replace with Customer Logo>>
1IT Project Management, Third Edition Chapter 4 Chapter 4: Project Integration Management.
Copyright 2009 Develop the project charter: working with stakeholders to create the document that formally authorizes a project—the charter Develop.
MC365 Introduction to Class. Today We Will: Go over the goals of the class. Review the syllabus. Introduce ourselves. Break up into teams to exchange.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Course Technology Chapter 3: Project Integration Management.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
By Saurabh Sardesai October 2014.
4 4 By: A. Shukr, M. Alnouri. Many new project managers have trouble looking at the “big picture” and want to focus on too many details. Project managers.
“How” We Do It An Introduction to NSLIJ’s Behavioral Expectations Model.
INCOSE 1 st reactions. One other area that struck me has the sheer number of levels of proficiency—in ours we are going with 5 and the first one is limited.
Project Life Cycle Introduction and Overview © Ed Green Penn State University All Rights Reserved.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Release & Deployment ITIL Version 3
Project Human Resource Management
SQA Architecture Software Quality By: MSMZ.
© 2021 SlidePlayer.com Inc. All rights reserved.