Worldwide Locations
126 Results Found
Traditionally, ITIL and TOGAF professionals have been part of different teams within an organization. Due to the ongoing alignment of business and IT, these professionals now often find themselves on the same team. Because of this crossover, there is a growing trend towards organization of work based on multiple best practice models.
For a project manager (PM) who has served as a military officer on a battalion or higher staff, the parallels between the military decision-making process (MDMP), the orders production process, and project management doctrine prescribed by the Project Management Institute (PMI) are difficult to ignore. Both the MDMP and the processes outlined in A Guide to the Project Management Body of Knowledge—Fifth Edition (PMBOK® Guide) are iterative in nature, allow for the introduction of changes to the original plan, assign tasks and responsibilities, and involve the concept of managing the scope of the operation or project.
Many I&O leaders and customers see little value from investments in ITIL. Not getting the Return on Investment (ROI) you expect normally comes from using ITIL incorrectly. You, your staff, and your customers must share the same goals and understand exactly what to expect from your ITIL investments. The goal of ITIL is not “business and IT alignment” or “competitive advantage from IT investments.” Instead, its first goal is to stabilize service operation. This builds a base for the second goal: increasing value through service optimization. You must have clear-cut, documented, and managed expectations for each activity, and order is vital. Success requires that you stabilize service delivery before trying to optimize. Focusing on the correct goal and linking each ITIL task to that goal is the correct use of ITIL.
Meet Global Knowledge course director and lab topology architect Joey DeWiele, a specialist in Unified Communications. Joey will walk you through the benefits of our exclusive Cisco UC lab architecture - a more scalable and stable approach to the all-important labs featured in unified communications courses. Our labs feature upgraded hardware and software including Custom Lenovo T61 PCs, 7965 IP Phones, 3560 Switches and Call Manager 7. With our flexible UC architecture, students are able to view and experience the full lab architecture regardless of which Cisco UC course they are taking or the skill set they are seeking. The lab architecture features a realistic network with redundant environments that are made rich with multiple machines, pre-deployed tools with shortcuts, online documentation that is particular to individual pods, and multiple OS support for all virtual machines (Windows, Linux, VMware).
ITIL is generally not prescriptive. In reality, the CSI Register at any given organization might look significantly different than the example given in the CSI book. The fields given in this example are important.
A video covering our Cisco Unified Communications courses - ACUCW1 & ACUCW2 - by Global Knowledge Course Director and Lab Topology Architect Joey DeWiele, a specialist in Unified Communications.
Global Knowledge Course Director and Lab Topology Architect Joey DeWiele, a specialist in Unified Communications, discusses Cisco Unity, Unity Connection & Unity Express.
Once an organization has categorized suppliers, one of the benefits that is quickly realized is an understanding of how supplier changes affect the buying organization and vice-versa. Changes are the modification, addition, or removal of something from the environment. The scope and scale of each change can be different. Change management covers everything from regular, low-risk, operational modifications all the way to significant organizational strategic shifts.
Organizations that plan for and conduct supplier management according to defined processes and boundaries are more likely to receive predictable, high-quality goods and services from their suppliers in a timely manner.
Lessons learned is a theory, or conclusion, based on evidence at a given time and describes what went wrong (as well as what went right) throughout the lifecycle of a project. Although it’s completed during the project closeout process, it should occur during the entire project lifecycle to ensure all information is captured and documented. Consequences of not having a project review of lessons learned are the increased likelihood of repeating actions that might have caused: