Home
Videos uploaded by user “Kavin Kumar”
Top 10 mostly asked project manager interview questions and answers Part-1
 
05:32
This video explains first part of top 10 mostly asked project management interview questions and answers with practical examples. Link to Part 2 : https://youtu.be/cQWKxgwZqT8 What is your leadership style? What is one skill a project manager needs to succeed? How do you approach a newly assigned project? How do you ensure your team stays on track to meet project deadlines? You are the project manager, and want to do option A. Everyone else on your team wants to do option B. What do you do?
Views: 18916 Kavin Kumar
Top 10 mostly asked project manager interview questions and answers Part-2
 
05:18
This video explains top 10 mostly asked project management interview questions and answers with practical examples. Link to Part-1: https://youtu.be/MNRU0EFFG7w How do you allocate resources in project? How do you handle a team member who is not productive? How Do You Delegate Tasks? How do you handle a difficult stakeholder? What project metrics do you use to ensure project is progressing on track?
Views: 9532 Kavin Kumar
16. PMP Project Change Management Process | Change Control | CCB | Change |  Learn in 5 minutes
 
02:46
Change Management Process is a method by which changes to the project like changing the scope, deliverables, time scales or resources are formally defined, evaluated and approved prior to implementation. Once the project baselines are formed and approved, any changes to them should be handled through Change Management Process Only. Generally change requests are called in short forms like PCR or CR. We can split this process in to four distinct phases for our understanding. The first phase is submit a change request. First the stake holder analyses that whether the change is required or not. If he or she thinks it is required then a change request is raised and logged in to the change management system. Please note that irrespective of whether the change is implemented or not, it needs to be logged in to the change management system and any stakeholder involved in the project can raise the CR. Next phase is, review the change request. In this phase the submitted CR is been reviewed by a responsible stakeholders as mentioned in the project management plan. This can be project manager, sponsor or Change Control Board. During the review, the reviewer looks for alternatives and sees whether the change is really required. If it is required, then the impact on project constraints like scope, time and cost are analysed. Generally the project team analyses the impact initially, before submitting the CR to the change control board. Next phase is approve CR. In this phase, based on the decision made by the change control board, the CR is been either approved or rejected and updated in the change management system accordingly. If it is approved, project management plan is updated accordingly. In the final phase, the change request will be implemented. In this process, Approved change requests are passed to Direct and Manage Project Work process, which is part of execution process group and the necessary activities will be carried out by the project team to implement the CR. Once the CR is implemented, Quality control process evaluates the implementation. After evaluation, if it is accepted it becomes part of verified deliverables and if rejected the rework has to be done.
Views: 5242 Kavin Kumar
2. Complete ITIL service life cycle stages| Process roles tools | ITIL overview in 10 min
 
09:45
This video explains about the ITIL complete service life cycle stages or core publications along with the process, roles and tools used in each stage of the life cycle in this video which helps to align IT with business. As per ITIL v3 there are 5 stages or core publications in I T service life cycle. First stage of ITIL is, Service Strategy which deals with the strategic analysis, planning, positioning, and implementation relating to IT service models, strategies, and objectives. It provides guidance on leveraging IT service management capabilities to effectively deliver value to customers and illustrate value for service providers. Second stage of ITIL is, Service Design Service Design translates strategic plans and objectives and creates the designs and specifications for execution through service transition and operations. Third stage of ITIL is, Service Transition It provides guidance on the service design and implementation, ensuring that the service delivers the intended strategy and can be operated and maintained effectively. Fourth stage of ITIL is, Service Operation which provides guidance on managing a service through its day to day production life. It also provides guidance on supporting operations by means of new models and architectures such as shared services, utility computing, web services, and mobile commerce. Fifth stage of ITIL is, Continual Service Improvement It provides guidance on measuring service performance through the service life cycle, suggesting improvements in service quality, operational efficiency and business continuity. Now we will see the processes, people and the tools in each of the ITIL service life cycle core publications in detail. Four processes in service strategy. First one is Service Catalog Management, which ensures that a Service Catalogue is produced and maintained, containing accurate information on all operational services and those being prepared to be run operationally. second process is Service Level Management, which helps to To negotiate Service Level Agreements with the customers and to design services in accordance with the agreed service level targets. Service Level Management is also responsible for ensuring that all Operational Level Agreements and Underpinning Contracts are appropriate, and to monitor and report on service levels. Capacity Management ensures that the capacity of IT services and the IT infrastructure is able to deliver the agreed service level targets in a cost effective and timely manner. Availability Management is responsible for ensuring that all IT infrastructure, processes, tools, roles are appropriate for the agreed availability targets. IT Service Continuity Management manages risks that could seriously impact IT services. ITSCM ensures that the IT service provider can always provide minimum agreed Service Levels, by reducing the risk from disaster events to an acceptable level and planning for the recovery of IT services. Information Security Management ensures the confidentiality, integrity and availability of an organization's information, data and IT services. next process is Supplier Management, which ensures that all contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments. The last process of service design is Design Coordination, which coordinates all service design activities, processes and resources. process plans and coordinates the resources to deploy a major Release within the predicted cost, time and quality estimates. This can be assumed as equivalent to project management. Change management assists to gather, analyse, store and share knowledge and information within an organization. The primary purpose of Knowledge Management is to improve efficiency by reducing the need to rediscover knowledge. Here the roles in service transition. makes sure Configuration items and services are constantly monitored, and to filter and categorize Events in order to decide on appropriate actions. Incident Management manages the life cycle of all Incidents. The primary objective of Incident Management is to return the IT service to users as quickly as possible. Problem Management manages the life cycle of all Problems. The primary objectives of Problem Management are to prevent Incidents from happening, and to minimize the impact of incidents that cannot be prevented. Request Fulfilment fulfils the Service Requests like password reset. Access Management ensures to grant authorized users the right to use a service, while preventing access to unauthorized users. Apart from these processes, service operation also has the following functions. Continual service improvement uses methods of quality control to learn from past success and failures.
Views: 18297 Kavin Kumar
3. What are the difference between portfolio program and project management| tutorial with example
 
02:49
This PMP project management video clearly explains the relationship and difference between portfolio program and project management with candid example. as per PMI PMP PMBOK definition,A portfolio refers to projects, programs, sub portfolios, and operations managed as a group to achieve strategic business objectives of an organization. PMP PMBOK says A program is defined as a group of related projects managed in a coordinated way to obtain benefits and control that are not available from managing them individually. PMP PMBOK defines Project is defined as a temporary endeavor undertaken to create a unique product, service, or result.
Views: 2180 Kavin Kumar
38.  Example for Project cost estimation with reservce analysis | Bottom Up cost estimation | PMP
 
02:10
This PMI PMP project management tutorial video clearly explains the project cost calculation along with reserve analysis. The example used in this PMP cost calculation video uses bottom up estimation technique to calculate the cost of the project. There are two types of reserves are used in project management. One is contingency reserve for known-unknowns and another one is management reserve for unknown-unknowns. Project cost is defined as adding the management cost with project baseline cost. Widely used approach is bottom up approach and first cost is calculated for each activity. Then it is added up to control account then up to the project level along with management reserve and contingency reserve. Project cost baseline is summed up amount at control account level and then contingency reserve and management reserve are added to get the project final budget and can be changed only through change management process. Hope this video is helpful to understand project cost estimation.
Views: 2431 Kavin Kumar
32. ITIL  | Incident management overview | workflow | service operation
 
03:08
This ITIL core foundation video explains about the overview, purpose, scope, objectives of incident management process and the incident management workflow chart which is part of the service operation. Also thi tutorial covers the incident management workflow is described with the help of a flow chart. Purpose of Incident management The purpose of incident management process is to restore normal service operation as quickly as possible and thereby minimise the adverse impact on business operations, thus ensuring that the best possible levels of service quality and availability are maintained. Normal service operation implies services operating as per the committed SLAs. Objectives of Incident management Ensure that standardised methods and procedures are used for efficient and prompt response, analysis, documentation, on-going management and reporting of incidents. Increase visibility and communication of incidents to business and IT support staff. Align incident management activities and priorities with those of the business. Scope of Incident management Managing any disruption or potential disruption to live IT services Incidents identified Directly by users through the service desk Through an interface from event management to incident management tools Reported and/or logged by technical staff
Views: 7295 Kavin Kumar
Agile SCRUM vs KANBAN | Comparison | Process Overview | Which is good for project
 
07:26
Agile SCRUM vs KANBAN | Comparison | Process Overview | Which is good for project Though both SCRUM and KANBAN are agile methodologies, which focuses on delivery of continuous value to the customer, what are the similarities and differences between them. Which methodology best suits for my project? I believe as an agile project manager you may have also come across the same question. Based on my experience and some brain storming, Here my thoughts about them. Please let me know your inputs through the comments. Before heading to the comparison, I feel It is worth to recall the fundamental process of SCRUM and KANBAN. SCRUM Overview KANBAN Overview With the fundamental understanding of scrum and kanban methodologies, now we can move to the comparison of these agile methodologies. Though both of these encourages work to be broken down into manageable chunks and place a high value on continual improvement, the primary difference is scrum is time boxed where it limits the amount of time allowed to accomplish a particular amount of work (by means of sprints). Whereas in other hand KANBAN is not time boxed but limits the amount of work allowed at a given point of time. That is only a predefined number of tasks are allowed in work in progress stage. Secondly in terms of roles, SCRUM recommends at least three roles that must be assigned in order to effectively process the work: the Product Owner, Scrum Master, and Team Members and Each role has its own set of responsibilities and cross functional , and they must work together to achieve an orderly and efficient balance. On contrary, in KANBAN no predefined roles are prescribed but evolved based on project and organization needs. The team not necessarily need to be cross functional since it is intended to be used by any and all teams involved in the project. Thirdly when it comes to the workflow,Though SCRUM is flexible to changes, it is slightly rigid on the sprint workflow where once the story points are committed into the sprint backlog, it can not be changed until the end of the sprint. After the retrospective meeting,only at the end of scrum, the story board is cleared and new story points will fill the board at the beginning on next sprint. On other hand, in Kanban workflow, each column has a limited number of allowed stories and there are no requisition for time boxes and there is no reason to reset the Kanban board as work progresses and it will continue as long as the project continues. Fourthly, when it comes to the duration of the project, In scrum the project schedule is estimated in terms of the number of sprints and each sprint varies from 2 weeks to 1 month. Since the KANBAN is not time bound, it doesn't prescribe any specific estimation methodlogy but we can find the velocity by dividing the number of story point completed at a given point of time. Nextly, in terms of the deliverables, in SCRUM at the end of the sprint the work is delivered in batch where as in KANBAN work is delivered at each time the story point is completed. In terms of change management, though SCRUM is providing good amount of flexibility for changes, once the sprint is committed, no changes can be made to the sprint until it finishes. But kanban is still more flexible than scrum, and changes can be introduced on the go. So far we have seen the key similarities and the differences between these two. Both scrum and kanban are part of agile methodologies and looks promising. But which one is suitable for my project? Here my thoughts based on my experience and observation. if you expect unpredictable workloads over the time, and don’t have a clear picture of the tasks upfront, with frequent changes in project scope and focus, then, Kanban can be more helpful. But on the other hand, if you already have a well defined feature list with a clear timeline then scrum would be a good fit.
Views: 12456 Kavin Kumar
45. PMP | What is project Critical chain method | Explain Project critical chain with example
 
01:57
This PMI PMP tutorial video explains what is ""project critical chain method"" and how to critical chain method is used to place the buffers with clear and simple example. As per PMP PMBOK definition, The critical chain method is a schedule method that allows the project team to place buffers on any project schedule path ,to account for limited resources and project uncertainties. Critical chain method is developed from the critical path method approach and considers the effects of resource allocation ,resource optimization ,resource levelling ,and activity duration uncertainty ,on the critical path determined using the critical path method. The project critical chain method adds duration buffers that are non work schedule activities to manage uncertainty. As per PMP, project critical chain method places feeding buffers, schedule buffers to cope up with uncertainties.
Views: 4873 Kavin Kumar
21. PMP tutorial| What are the group creative techniques used to collect requirements in project
 
01:30
In this PMP project management tutorial video, we will look into the group creative techniques that are used in project to collect the requirements from the stakeholders. • Brainstorming. A technique used to generate and collect multiple ideas related to project and product requirements. Although brainstorming by itself does not include voting or prioritization, it is often used with other group creativity techniques that do. •Nominal group technique. A technique that enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization. • Idea or mind mapping. A technique in which ideas created through individual brainstorming sessions are consolidated into a single map to reflect commonality and differences in understanding, and generate new ideas. • Affinity diagram. A technique that allows large numbers of ideas to be classified into groups for review and analysis. • Multi criteria decision analysis. A technique that utilizes a decision matrix to provide a systematic analytical approach for establishing criteria, such as risk levels, uncertainty, and valuation, to evaluate and rank many ideas.
Views: 1550 Kavin Kumar
27. ITIL  | Service Asset and Configuration Management SACM Process overview
 
03:30
This ITIL core foundation video explains about overview,purpose,objective and scope of Service Asset and Configuration Management SACM Process which is part of servie transition stage along with configuration item, CMDB,SKMS, CI, CMS, DML and the relationship among all of them. We will learn about the Service Asset and Configuration Management in this video. The Purpose of SACM is to ensure that the assets required to deliver services are properly controlled, and that accurate and reliable information about those assets is available when and where it is needed. Now we will see the basic component details of the service assets. configuration item configuration item can be defined as anything that needs to be managed in order to deliver an IT Service CI information is recorded in the configuration management system CI information is maintained throughout its lifecycle by configuration management All CIs are subject to change management control Here are some examples IT services, hardware, software, buildings, people and formal documentation such as process documentation and SLA's Next we will look about Configuration baseline Configuration baseline has Configuration details captured at a specific point in time. This captures both the structure and details of a configuration item. It is used as a reference point for future builds, releases and changes. Typically managed through the change management process. Now we will see about the configuration management system, CMS CMS stores all the Information about all configuration items in one or more CMDB irrespective of whether the CI is an entire service, or any component CMS stores attributes. that is Any information about the CI that might be needed CMS stores relationships Between CIs and With incident, problem, change records, etc. CMS has multiple layers like Data sources and tools, information integration, knowledge processing, presentation etc. Next we will move on to definitive media library which is also known as DML. DML is The only source for build and distribution It keeps the Master copies of all software assets like source code, scripts, application files, licenses etc, irrespective of whether in house developed or external one All the files in DML are Quality checked like Complete, correct, virus scanned etc.. Here is the relationship among the CI, CMDB and DML. All the physical and electronic CI's are stored in the DML and all the details about the CI's are stored in CMDB. So whenever there is a service release, the CI's are taken from the DML and the release note will be updated in the CMDB. Now we will see the relationship between CMDB, CMS and Service knowledge management system SKMS. All the CI realted information are stored in one or more CMDB and all these CMDB are part of CMS. This CMS is an integral part of SKMS which helps in informed decision making process. Hre points to remember. SKMS includes CMS. SKMS contains all the information needed to manage the lifecycle of IT Services.
Views: 1722 Kavin Kumar
1. Software Application N-tier (Layered) Architecture design pattern | Tutorial with example
 
04:45
This video explains about the most commonly used software architecture, layered architecture which is also known as N-tire architecture. I have shown the commonly used 5 layers in most of the software application architecture in the layered architecture or N-tire architecture, but generally the layers can be selected based on the needs of the application. Presentation layer. second layer is service layer. Third layer is business logic layer. Fourth layer is, persistence layer. Fifth layer is database layer. In this layered N tire architecture, each layer performs a unique role and even the components inside these layers are also performs some unique tasks. So let's see how the each layer communicates with each other. The architecture diagram that shown in the example is a closed architecture. Here the closed indicates that the request that comes to any of application layer should go through all of the layers. Also this layered architecture provides the separation of concern. Based on the business scenario, some layers can be opened but detailed care should be taken while doing so since it may have heavy performance or security risks. Arbitrary scores are also given based on different features like development, testing, deployment, performance and agility.
Views: 27279 Kavin Kumar
2. What is project and project management | Difference between project and operations
 
01:52
This PMI PMP project management tutorial training video explains What is project and what is project management. Also depicts the Difference between project management and operation management as per the PMI PMP standards. As per PMI PMP, Project is defined as a temporary endeavour undertaken to create a unique product, service, or result. The temporary nature of the project doesn't mean it is short but the project has a definite end date. Project management is the application of knowledge and skills to manage the project. Examples for project management are building a house, developing a software. There is always a question to the PMP aspiring project management professionals as what is the difference between project management and operational management. operation management is an on-going business supporting process and will do the same repetitive tasks. Examples of operation management are call center operation. Main difference between the project management vs operation management is the duration and non-repetitive nature. As opposed to the PMP project definition, operation management is an on-going repetitive process.
Views: 2465 Kavin Kumar
1. PMI PMP Exam application process | PMP exam eligibility criteria tutorial explained step by step
 
04:55
This video clearly explains the step by step process of PMI PMP Exam application process and PMI PMP exam eligibility criteria. PMI PMP exam is a widely recognized project management certificate across the world and holding a PMP title, clearly gives an edge for the project managers to prove their capability to lead the projects. The main PMI PMP eligibility criteria for applying for PMP certificate exam is to have real time project management experience. Based on your education qualification, the amount of project management experience required to apply for PMP exam varies. PMI PMP exam application process is quite straight forward but requires little time to prepare the PMP application where you need to prove your project management experience for each of the recent project that you have worked. Applicant can apply for the PMP exam online through PMP application channel as shown in the video. Though PMI PMP eligibility requiments states that one need to direct and lead project, the applicant doesn't require to hold the title of a project manager but must be accountable for leading atleast a part of project. The PMI PMP Application fee varies based on the PMI membership where 550 USD for non PMI members and 405 USD for PMI members. The exam eligibility code given by PMI for taking the PMP exam is valid for one year and the applicat can retake the PMP exam two more time in case of any unsuccessful attempets. PMI PMP exam costists of 200 questions and all the questions are need to be answered with in 4 hours. After meeting the PMP eligibility criteria and during the PMP application process, you may get caught in audit process where the applicants are picked up randomly. This is not a mammoth task and you just need to prove your project management experience with supporting documents. Upon the PMP application approval and fee payment, you can schedule the PMP exam, and pass the PMP exam. After successfully completing the PMP exam, you can retain the certificate by obtaining 60 PDUs in 3 year cycle.
Views: 4089 Kavin Kumar
4. Learn project management in less than 5 minutes | PMI PMP Project management overview
 
02:31
This video defines what is Project management and helps to learn about project management in less than 5 minutes. It covers all the basic processes like stakeholder management, requirements collection, and balancing the project constraints in project management as per PMI PMP. As per PMP PMBOK-5, there are totally 47 processes in project management and are grouped into five process groups initializing, planning, executing , monitoring and controlling, closing.
Views: 1475 Kavin Kumar
59. PMP Tutorial| Quality management| What are the seven basic quality tools in project management
 
02:58
Let's learn about the important seven basic quality tools in this PMBOK-5 based project management tutorial video. There are totally 7 quality tools are used basically in the project quality management to ensure the quality of project delivervable. The seven tools are explained with clear examples and are as follows. 1. Cause and effect diagram which is also called fish bone diagram 2. flow chart 3. check sheet or tally sheet 4. pareto diagram which is also called 80/20 rule 5. histogram 6. control chart 7. scattered diagram All the above seven basic quality tools are used to ensure the quality of project irrespective of the domain.These seven quality tools are used in six sigma as well.
Views: 1347 Kavin Kumar
69. PMP | project team conflict management | conflict resolution techniques | Source of conflict
 
02:30
This video describes the various Conflict Management techniques of a project team as per PMI PMP PMBOK standard. Conflict Management - Conflict is an inevitable consequence of organizational interactions but ,can lead to increased creativity and better decision making ,if managed properly. - Conflict can be avoided by: - Keeping team informed of the exact project status - Clearly assigning work with no overlapping responsibilities - Continuously motivating the team about the work challenges - Establishing team ground rules ,group norms ,and solid project management practices Conflict resolution - If the differences become a negative factor ,project team members are initially responsible for their resolution. - If conflict escalates,then the project manager should help facilitate a satisfactory resolution. - Conflict should be addressed early and usually in private ,using a direct ,collaborative approach. - If disruptive conflict continues ,formal procedures may be used ,including disciplinary actions. - Sources of Conflict: - Scarce resources - Scheduling priorities - Personal work styles Conflict Resolution Technique: - Withdraw or Avoid Retreating from an actual or potential conflict situation ;postponing the issue to be better prepared or to be resolved by others. - Smooth or Accommodate Emphasizing areas of agreement rather than areas of difference ;conceding one’s position to the needs of others to maintain harmony and relationships. - Compromise or Reconcile Searching for solutions that bring some degree of satisfaction to all parties in order to temporarily or partially resolve the conflict - Force or Direct Pushing one’s viewpoint at the expense of others ;offering only win-lose solutions ,usually enforced through a power position to resolve an emergency. - Collaborate or Problem solve Incorporating multiple viewpoints and insights from differing perspectives ;requires a cooperative attitude and open dialogue that typically leads to consensus and commitment.
Views: 1892 Kavin Kumar
46. PMP | what are resource optimization techniques in project management
 
02:01
This PMI PMP project management video explains about the various resource optimization techniques that are used in project management. As per PMP PMBOK guide, there are two methods used in resource optimization techniques. 1.Resource levelling 2.Resource smoothing First resource optimization technique is resource levelling. As per PMP PMBOK-5 guide,resource levelling technique ,in which start and finish dates are adjusted based on resource constraints with the goal of ,balancing demand ,for resources with the available supply. Second resource optimization technique is resource smoothing. Resource smoothing technique that adjusts the activities of a schedule model such that ,the requirements for resources on the project do not exceed certain predefined resource limits. In resource smoothing ,as opposed to resource levelling, the project’s critical path is not changed and the completion date may not be delayed.
Views: 2500 Kavin Kumar
Product management vs Project management vs SDLC | Comparison and Relationship
 
05:15
We will look into the relationship and difference between product life cycle management, project life cycle management and SDLC (Software Development Life cycle management) with a simple example in this video. First we will try to define, life cycle phases and major focus of each of these. Product management: Product life cycle management is the process of managing the entire life cycle of a product from inception, through engineering design, and manufacture, to service and disposal of manufactured products. Generally Product life cycle management has the following phases. Idea generation Idea Screening Business Analysis Product Development Test Marketing Commercialization Evaluate and refine Major focus of product life cycle management is, the features and functionalities of the product that it offers to the customers. Now we will look into Project management. As per Project management institute (PMI), Project can be defined as a temporary endeavor undertaken to create a unique product, service, or result. the temporary indicates the project has a define start and end time. Project management can be defined as the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements. As per PMI, project management has five process group or phases as follows. Initiating, Planning, Executing, Monitoring and Controlling Closing. The main focus of project management is, to ensure the deliverable are meeting the requirements. Let's move on to SDLC life cycle management. SDLC can be defined as a process for planning, developing, testing, and deploying an information system. SDLC management deals with this managing the process associated with SDLC to build the IT system. Generally it has following 5 phases and according to the selected methodology these phases may or may not overlap. Requirements gathering Design Development Testing, and Implementation Major focus of SDLC management is, to build the system according to the specifications. Let me connect the product, project, and SDLC life cycle with a simple example. Lets imagine a scenario where company XYZ wants to launch a new online web store that helps the merchants to sell their products online. As a first step The XYZ company will start with the initial process of product life cycle management, idea generation, idea screening and business analysis are been performed and business cases are produced to support the launch of the online store. Now the company will start a new project for developing and launching the site. At this stage, the first phase of the project Initiation will be kicked off and project charter, stake holder register will be created. At the time project planning phase, SDLC life cycle starts. Also during the project planning phase, Software Development Methodology (SDM) will be chosen to implement the SDLC process and the software development starts. Normally entire SDLC will be contained in planning, execution, monitor & control phases of project life cycle. I would like to mention one point here. we can't exactly define at what phases of project management life cycle, the SDLC process will fit in, as the SDLC process might or might not overlap based on the selected software development methodology. So here I made an assumption of water fall SDLC methodology is followed. System development and launching process will start either at the planning, or slightly before that, and go through the execution and finishes at the monitoring and control phase. At this stage, SDLC life cycle ends. Next phase of the project is the project closing phase where the required documents will be submitted and the project will get closed formally. Though the project is closed here, still the product life cycle continues here. Product evaluation and refining is a continuous process and the product will be evolved further based on the customers feed back or through some analysis. Lets say, the company wants to roll out a mobile version of the application to the market. At this point of time one more project will be started and will continue the same cycle as mentioned above. So in a nut shell, a product life cycle will have many project life cycles and SDLC will be a part of the project management life cycle.
Views: 3555 Kavin Kumar
43. What are the schedule compression techniques in project management | PMP Tutorial
 
01:45
This PMP project management tutorial explains about the schedule compression techniques used in project management. Schedule compression techniques are used to shorten the schedule duration without reducing the project scope, in order to meet schedule constraints, imposed dates, or other schedule objectives. As per PMP PMBOK-5, There are two types of compression techniques are used. Crashing and fast tracking. Crashing is the technique used to shorten the schedule duration for the least incremental cost by adding resources. Crashing does not always produce a viable alternative and may result in increased risk and/or cost. fast tracking is A schedule compression technique in which activities or phases normally done in sequence are performed in parallel for at least a portion of their duration. Fast tracking only works if activities can be overlapped to shorten the project duration.
Views: 1356 Kavin Kumar
6. What are the project selection methods | PMP Tutorial | How a project is selected
 
05:51
This video explains the various project selection methods which helps to choose the best fit among alternatives.There are two methods using which projects can be selected. First one is ,benefit comparison method which is based on comparative approach ,and the second one is ,constraints optimized method which is based on mathematical approach. Examples for Benefit comparison project selection methods are peer review, scoring model, economic model. Examples for constraints optimized methods are Linear programming, Present value PV, Net present value NPV, Internal rate of return IRR, Payback period, Return on investment RoI Each of this project selection method is been explained clearly with suitable examples for better understanding.
Views: 11463 Kavin Kumar
4. ITIL| define what is Process | Function | Role
 
03:14
This free complete and full ITIL foundation tutorial video explains and defines what is a process, what is a function, and what are the roles in IT service management, as defined by ITIL. what is a process. As per ITIL, a process can be defined as, A set of activities designed to accomplish a specific objective. A process takes defined inputs and turns them into defined outputs. A process may include roles, responsibilities, tools, and management controls required to deliver the outputs. The characteristics of process? It is measurable It delivers specific result Primary result is delivered to customers or stakeholders It responds to specific events what is a function? Function can defined as, A team or group of people and the tools they use, to carry out one or more processes or activities. Now we will look into the roles in service management. service owner role. Service owner is the person who is accountable for the delivery of a specific IT service, They are responsible for continual improvement and management of change affecting services under their care. Example: The owner of the infrastructure service Process Owner role Process owner is the person responsible for ensuring that the process is fit for the desired purpose and is accountable for the outputs of that process. Example: The owner for the availability management process RACI matrix which connects the process and functions along with the roles. RACI is an acronym for the following four main roles: Responsible The person or people responsible for getting the job done Accountable Only one person can be accountable for each task Consulted The people who are consulted and whose opinions are sought Informed The people who are kept up-to-date on progress
Views: 1036 Kavin Kumar
5. Organization structure Influence project management | Functional Matrix Projectized organization
 
04:13
It is better for the Project managers to know the influence of organizational structure on project management. As per PMI PMP, organizations can be classified as functional organization, weak matrix organization, balanced matrix organization, strong matrix organization and projectized organization. This tutorial video clearly explains the level of influence of the organizational structures like functional, weak matrix, balanced matrix, strong matrix and projectized on the project management. As per PMP PMBOK, the authority of the project manager is high on decision making while comparing to functional or matrix organizations. In functional and weak matrix structure, the project manager merely work as a project co-coordinator and has very low authority in decision making.
Views: 12448 Kavin Kumar
33. PMP Tutorial | Define Activities Process Overview | ITTO,input,tools and techniques, output
 
03:02
This PMI PMP project management tutorial video explains about the define activity process and the ITTO, inut, tools and techniques and output. - PMP PMBOK Define Activities is the process of identifying and documenting the specific actions to be performed to produce the project deliverables. - The key benefit of this PMP PMBOK Define Activities process is to break down work packages into activities that provide a basis for estimating, scheduling, executing, monitoring and controlling the project work. Let's see the Input ,Tools and techniques and ,output of Define activities process. Here the inputs of PMP PMBOK Define Activities process Schedule management plan Scope baseline Enterprise environmental factors Organizational process assets Tools and technique used in PMP PMBOK Define Activities process Decomposition Rolling wave planning Expert judgement Output of this PMP PMBOK Define Activities process. Activity list Activity attributes Milestone list
Views: 1378 Kavin Kumar
23. PMP | how to define scope process tutorial in project | ITTO | Input,tools and techniques,output
 
03:02
This video explains about the process of define scope in project manage as per PMP PMBOK guide. Also the ITTO input, tools and techniques and output of this process is explained in this video. Define Scope is the process of developing a detailed description of the project and product. The key benefit of this PMP Define Scope process is that it describes the project, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope. During PMP define scope process, the project team identifies which requirements are included in the project and which requirements are not included in the project scope. As a result of this PMP Define Scope process,a detailed description of the project, product, service, or result will be developed. Here the inputs of PMP Define scope process . Scope management plan Project charter Requirements documentation Organizational process assets tools and techniques used in PMP Define scope process are as follows. Expert judgement Product analysis Alternatives generation Facilitated workshops The output of PMP Define scope process process. Project scope statement Project documents updates
Views: 935 Kavin Kumar
65. PMP | Human Resource Management Theories | Organizational Theories | tools and techniques
 
03:52
Let's learn about some tools and techniques of plan human resource management process in this PMP project management tutorial. First we will look into project Organization Charts and Position Descriptions. Various formats exist to document team member roles and responsibilities. Most of the formats fall into one of three types: hierarchical, matrix, or text-oriented. Regardless of the method utilized, the objective is to ensure that each work package has an unambiguous owner and that all team members have a clear understanding of their roles and responsibilities. First we will look into the hierarchical model. In this model, The traditional organization chart structure can be used to show positions and relationships in a graphical, top-down format. the organizational breakdown structure (O BS) is arranged according to an organization’s existing departments, units, or teams with the project activities or work packages listed under each department. As shown in the example, the project organization is split into 3 reporting groups named, Hardware leader, software leader and product leader and the other reporting relationships are portrayed at below these roles. Next will look into RACI matrix. It is a grid that shows the project resources assigned to each work package. It is used to illustrate the connections between work packages or activities and project team members. In the example, R indicates responsible, A indicates accountable, C indicates consulted and I indicates informed. In some of the projects, simple text formats are used which has the details of roles, responsibilities, authority etc. Here a sample for that. let's move on to some interesting organizational theories. First we will look at McGregor’s Theory of X and Y. according to this theory, all the workers are fit into two categories. First one is theory X which states that, People should be watched every minute. People avoid work whenever possible. second theory is Theory Y which states that, People are willing to work without supervision , nd they want to achieve something. Next theory is maslows hierarchy of needs. Maslow's hierarchy of needs is a motivational theory in psychology, comprising a five tier model of human needs, often depicted as hierarchical levels within a pyramid. There are totally five levels and One must satisfy lower level deficit needs ,before progressing on to meet higher level growth needs. Here are the five levels from bottom of the pyramid to top. physiological, safety, love and belonging , esteem and self actualization. Next we will look into Herzberg theory. - This heory calls satisfiers as motivators and the dissatisfiers as hygiene factors - Using the term ""hygiene"" in the sense that they are considered maintenance factors that are necessary to avoid dissatisfaction but that by themselves do not provide satisfaction. As per this theory the hygine factors are, - Company policy - Supervision - Relationship with Boss - Work conditions - Salary - Relationship with Peers And motivators are, - Achievement - Recognition - Work itself - Responsibility - Advancement - Growth
Views: 1190 Kavin Kumar
41. ITIL | Continuous Service Improvement | seven step improvement process
 
03:28
This ITIL foundation tutorial video explains about the seven step improvement process of continuous service improvement. The seven step process is the vital process of continuous service improvement, CSI. It enables an organizational resource to identify and understand which process and function of their service operations needs major enhancement. The purpose of the seven step improvement process is to define and manage the steps needed to identify, define, gather, process, analyze, present and implement improvements. Now we will look into each step in detail. First step of seven step improvement process is, Identify the strategy for improvement Before an improvement plan is executed it is really necessary to understand the need for improvement. In this stage, A thorough understanding of business objectives are carried Areas of enhancements are identified. All the information related to what all services need to be measured is gathered This data is then fed into the CSI improvement plan cycle. Second step is, to define what you measure. CSI conducts gap analysis to identify the opportunities for improvement. One can find out the areas to measure by knowing the new service level requirement, available funds and IT capabilities. Third step is, to gather the data After defining what needs to be measured, data is gathered according to the goals and objectives of service operation. Monitoring should be in place to get the raw quantitative data. The quality of data is critical and it can be gathered through either manual or automatic. Fourth step is to process the data Once the data is gathered, it will be processed to get the desired information. Critical Success Factor and Key Performance Indicators plays a vital role in processing the data. The raw data is organized and divided according to its categories and operation, which makes it easy to process and transform the data into information. Fifth step is, to analyze the information After deriving the required information from the raw data, it is carefully analyzed to find missing gaps and its impact on business. The information is thoroughly evaluated taking into consideration all relevant, internal and external factors that can directly or indirectly impact the data. The information is converted into knowledge or facts. Sixth step is, present and use the information. The analyzed data is shared with the business stakeholders in a clear and defined manner, presenting them an accurate picture of the results of the improvement plan that is implemented. CSI works closely with senior management and assist them to make strategic decisions and determine the next step to optimize and improve the service. Final step is to implement the corrective activities. As CSI has identified the areas that need a change, solutions and remedial plans are communicated to the management to improve the service. A change, thus implemented for the improvement, sets a new baseline and the cycle begins again.
Views: 2740 Kavin Kumar
9. PMP Tutorial | What are the Organizational Process Assets | Overview with examples
 
01:50
This PMP tutorial video explains about the organizational process assets. Organizational process assets are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. They include any artifact, practice, or knowledge from any or all of the organizations involved in the project that can be used to perform or govern the project. These process assets include formal and informal plans, processes, policies, procedures, and knowledge bases, specific to and used by the performing organization. The process assets also include the organization’s knowledge bases such as lessons learned and historical information. Organizational process assets may include completed schedules, risk data, and earned value data. Organizational process assets are inputs to most planning processes. Throughout the project, the project team members may update and add to the organizational process assets as necessary. Organizational process assets may be grouped into two categories: (1) processes and procedures, and (2) corporate knowledge base.
Views: 1030 Kavin Kumar
102. PMP | Stakeholder analysis grid | Power/influence power/interest grid matrix explained
 
02:03
Let's analysis the process of stakeholder analysis in this PMI PMP project management tutorial video. - Stakeholder analysis is a technique of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. - Stakeholder analysis grid identifies the interests, expectations, and influence of the stakeholders and relates them to the purpose of the project. Here are some classification models that helps to better organize and manage the stakeholders. - Power/interest grid: grouping the stakeholders based on their level of authority (""power"") and their level or concern (""interest"") regarding the project outcomes - Power/influence grid: grouping the stakeholders based on their level of authority (""power"") and their active involvement (""influence"") in the project - Influence/impact grid: grouping the stakeholders based on their active involvement (""influence"") in the project and their ability to effect changes to the project’s planning or execution (""impact"") - Salience model: describing classes of stakeholders based on their power (ability to impose their will) ,urgency (need for immediate attention), and legitimacy (their involvement is appropriate).
Views: 1164 Kavin Kumar
27. PMP Tutorial | What is Project Scope Baseline | Define Scope Baseline
 
01:23
This PMI PMP project management tutorial video explains what is project scope baseline. The scope baseline is the approved version of a scope statement, work breakdown structure, and its associated WBS dictionary. Once approved, scope baseline can be changed only through formal change control procedures and is used as a basis for comparison. It is a component of the project management plan. Components of the scope baseline include: Project scope statement. WBS WBS dictionary
Views: 1599 Kavin Kumar
61. PMP| what are Quality Management and Control Tools | Quality assurance audit tools example
 
03:36
We will look into the important quality assurance tools,quality management and control tools in this PMI PMP project management basics video tutorial. First quality assurance tool is affinity diagram. affinity diagram is used to generate ideas that can be linked, form organized patterns of thought about a problem. Next quality assurance tool is process decision program chart (PDPC) which is also called PDPC. This technique is used to understand a goal in relation to the steps for getting to the goal. Next quality management and control tool is , inter relationship digraphs. This technique is Used for creative problem solving in moderately complex scenarios that possess intertwined logical relationships for up to 50 relevant items. Next quality management and control tool is tree Diagram. This technique is used to represent decomposition hierarchies and to visualize parent-child relationship. Next quality assurance technique is prioritized matrices. This technique is used to identify the key issues and the suitable alternatives to be prioritized as a set of decisions for implementation. Next qulaity assurance technique is activity network diagrams. Activity network diagrams are used with project scheduling methodologies. Matrix digram is one of the commonly used quality manage and control tool. The matrix diagram seeks to show the strength of relationships between factors, causes and objectives. Last quality audit technique is quality audit. - A quality audit is a structured, independent process to determine ,if project activities comply with organizational and project policies, processes ,and procedures.
Views: 4149 Kavin Kumar
29.PMP Tutorial | Explain control scope process | ITTO | input,tools and techniques,output
 
02:27
In this PMI PMP project management tutorial, the process of project control scope is explained along with ITTO,input,tools and techniques, output. PMP Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. The key benefit of PMP Control Scope process is that it allows the scope baseline to be maintained throughout the project. PMP Control Scope controls the scope creep and gold plating. PMP Control Scope avoids any scope deviation like Scope creep,gold plating Let's see the Input ,Tools and techniques and ,output of control scope process. Here the inputs of PMP Control Scope process. Project management plan Requirements documentation Requirements traceability matrix Work performance data Organizational process assets Tools and technique of PMP Control Scope process Variance analysis Output of PMP Control Scope process. Work performance information Change requests Project management plan updates Project documents updates Organizational process assets updates
Views: 884 Kavin Kumar
95. PMP | Frequently used important terms in Project procurement management
 
01:23
Let's look at some important terms in project procurement management in this PMI PMP PMBOK based project management tutorial. - RFI: Request for information - RFP: Request for proposal - RFB: Request for bids - RFQ: Request for quotation - PO: Purchase order - SOW: Statement of work - Quotation - NDA: Non-disclosure agreement - LOI: Letter of intent - T&C: Terms and conditions - Force majeure This is a A French term literally translated as ""greater force"", this clause is included in contracts to remove liability for natural and unavoidable catastrophes that interrupt the expected course of events and restrict participants from fulfilling obligations. - Doctrine of waiver - Privity of contracts the relation between the parties in a contract which entitles them to sue each other but prevents a third party from doing so. - Dispute resolution - Termination for convenience of buyer
Views: 1233 Kavin Kumar
6. ITIL | Service Strategy | Types of Services | Core, enabling, enhancing services
 
01:31
This ITIL core foundation video explains about the three types of services in the service strategy with a clear example. Core service, enabling service and enhancing service core service: core service can be defined as a service that delivers the basic outcomes desired by one or more customers. enabling service: which can be defined as a service that is needed in order to deliver a core service. enhancing service: which is a service that is added to a core service to make it more attractive to the customer.
Views: 1107 Kavin Kumar
34. PMP Tutorial | Project Schedule Sequence Activities Process Overview | ITTO,input,tools,output
 
03:34
This PMI PMP project management tutorial video explains about the sequence activities process which is part of the project schedule management. PMP Sequence activities is the process of identifying and documenting relationships among the project activities. - The key benefit of this PMI PMP sequence activity process is that ,it defines the logical sequence of work to obtain the greatest efficiency given all project constraints. - Every activity and milestone except the first and last activities ,should be connected to at least one predecessor with a finish to start or start to start logical relationship ,and at least one successor with a finish to start or finish to finish logical relationship. Let's see the Input ,Tools and techniques and ,output of sequence activities process. Here the inputs of PMP sequence activity process which is part of project schedule management. Schedule management plan Activity list Activity attributes Milestone list Project scope statement Enterprise environmental factors Organizational process assets Tools and techniques used in this PMP sequence activity process. Precedence diagramming method Dependency determination Leads and lags Output of this PMP sequence activity process. Project schedule network diagrams Project documents updates
Views: 1045 Kavin Kumar
30. PMP Tutorial | Project Schedule Time Management | frequently used Important terms with examples
 
02:32
In this PMI PMP project management tutorial, some frequently used important project schedule time management related terms like lead,lag,hammock activity,milestone,schedule,effort,duration, are explained with examples. This PMP project management tutorial explains about some of the frequently used important terms in project schedule management. network diagramming methods is an important term used in PMP project schedule management. There are two types of diagrams. One is Precedence Diagramming Model or Activity on Node and the other is Arrow Diagramming Model or Activity on Arrow. Hammock Activity ,which is A summary activity used to indicate milestones for reporting Here is the very often used term milestone. Milestones are similar to regular schedule activities, with the same structure and attributes, but they have zero duration because milestones represent a moment in time Lead: Lag: Rolling wave plan: Effort: Duration:
Views: 690 Kavin Kumar
28. PMP Tutorial | Explain validate scope process | ITTO | input,tools and techniques,output
 
03:26
This PMI PMP project management video explain about the validate scope process along with ITTO,input,tools and techniques and output. PMP Validate Scope is the process of formalizing acceptance of the completed project deliverables. The key benefit of this PMP validate scope process is that it brings objectivity to the acceptance process and increases the chance of final product, service, or result acceptance by validating each deliverable. The PMP Validate Scope process differs from the Control Quality process. Let's see the Input ,Tools and techniques and ,output of validate scope process. Inputs of PMP validate scope process. Project management plan Requirements documentation Requirements traceability matrix Verified deliverables Work performance data Tools and techniques used in PMP validate scope process. Inspection Group decision-making techniques Output of PMP validate scope process. Accepted deliverables Change requests Work performance information Project documents updates
Views: 864 Kavin Kumar
1. What is ITIL | ITSM | IT service | Define ITIL | ITIL Tutorial Basics
 
03:08
This video explains about what is ITIL, benefits of ITIL, ITSM, IT service delivery and the link among all of them. IT services refers to the application of business and technical expertise to enable organizations in the creation, management and optimization of or access to information and business processes. IT service management which is also known as IT S M, refers to the whole activities directed by policies, organized and structured in processes and supporting procedures that are performed by an organization to plan, design, deliver, operate and control information technology services offered to customers. The goal of every IT Service Management framework is to ensure that the right processes, people, and technology are in place so that the organization can meet its business goals. Some of the popular IT service management framework are, ITIL, COBIT, Microsoft Operational Framework which is called M O F and I S O 20000. ITIL is framework which consists a set of good practices for IT service management, that focuses on aligning IT services with the needs of business. ITIL contains detailed process descriptions, flows, success factors, metrics and implementation guidance that organizations can adapt to work in their environment. The ITIL framework can help organizations establish and improve their overall IT Service Management capability, increase alignment with the business, maximize and demonstrate value to the business. It focuses on delivering IT services to the company.
Views: 2657 Kavin Kumar
43. ITIL | important key terms and concepts in service management
 
06:22
This video explains the important key terms and definitions in ITIL service management. ITIL Information Technology Infrastructure Library is a set of best practices being practiced by most of the infrastructure service providers to deliver services to the customers to meet their business needs within predicted cost and quality. Service Service is a means of delivering value to customers by achieving customer's desired results while working within given constraints. Service Level It is measured and reported achievement against one or more Service Level Targets. Service Level Agreement It is agreement between service provider and customer. The SLA describes the IT Service, documents Service Level Targets and specifies the responsibilities of provider and customer. Service Strategy Service Strategy helps to design, develop and implement service management as organizational capabilities and strategic assets as well. It enables a service provider to consistently outperform competitive alternatives over time, across business cycles,industry disruptions and changes in leadership. Service Model Service Model is the high level description of the service and components required to deliver that service. Service Portfolio Service Portfolio is the set of services provided by the service provider. Service Catalogue Service Catalogue is the set of specific services being provided by service provider to a specific customer. Customer Portfolio Customer Portfolio is used to record all customers of IT service provider. Demand Management Demand Management is very important and critical process in service strategy. It helps to understand customer demand for services so that appropriate capacity can be provisioned to meet those demands. Pattern of Business Activity It is an extremely important activity achieved by knowing customer how they operate and future requirement they might need. Service Design Service Design provides a blueprint for the services. It not only includes designing of new service but also devises changes and improvements to existing ones. Operational Level Agreement OLA is an agreement between IT service provider and another part of same organization. Service Level Report It gives insight into a service provider’s ability to deliver the agreed service quality. Service Level Requirements It is a document containing the requirements for a service from the client viewpoint,defining detailed service level targets. Service Asset Service Assets are the resources and capabilities owned by the service provider enabling it to deliver service to the customer. Configuration Item Configuration Item is subset of service assets and have direct impact on delivering services. All servers, networks, applications that have impact on production are known as configuration item. Service Assets and Configuration Management It deals with maintaining up to date and verified database of all assets and CIs which are also made available to other service management processes. Change Change refers to modifying existing services. Event Event is defined as detectable occurrence that has significance for the delivery of IT service. Events are created by Configuration Item or the monitoring tools. Incident Incident is defined as any disruption in IT service. Incident can be reported either through the Service Desk or through an interface from event management to incident management tools. Service Request Service Request refers to demand by the users. These requests can be regarding small changes, changing the password, installing additional software application, requesting information etc. Problem Problem is defined as unknown cause of one or more incident. Known Error Known Error is well identified problem with its cause and resolution. It is stored in Known Error Database K E D B. core service A service that delivers the basic outcomes desired by one or more customers. A core service provides a specific level of utility and warranty. Service Provider An organisation supplying services to one or more internal customers or external customers. Service provider is often used as a short form for IT service provider. There are three types of service provider available. Internal provider Share service provider External Service provider
Views: 554 Kavin Kumar
81. PMP Tutorial | Identify risk process overview | ITTO,input,tools,output
 
04:50
This PMI PMP PMBOK based project management vide explains about Identify Risks process. - Identify Risks is the process of determining which risks may affect the project and documenting their characteristics. - The key benefit of this PMP project identify risk process is ,the documentation of existing risks ,and the knowledge ,and ability ,it provides to the project team to anticipate events. - Identify riks process belongs to planning process group - The primary output from Identify Risks is the initial entry into the risk register. The risk register is a document in which the results of risk analysis and risk response planning are recorded. risk register is an important output of this identify risk process. Here the ITTO,input,tools,techniques,output of PMP Identify risk process Per PMP PMBOK-5, Input of project Identify risk process is, .1 Risk management plan .2 Cost management plan .3 Schedule management plan .4 Quality management plan .5 Human resource management plan .6 Scope baseline .7 Activity cost estimates .8 Activity duration estimates .9 Stakeholder register .10 Project documents .11 Procurement documents .12 Enterprise environmental factors .13 Organizational process assets PMP PMBOK-5 says following tools and techniques are used in project Identify risk process .1 Documentation reviews .2 Information gathering techniques .3 Checklist analysis .4 Assumptions analysis .5 Diagramming techniques .6 SWOT analysis .7 Expert judgment Following are the output of project Identify risk process as per PMP pmbok-5 .1 Risk register
Views: 454 Kavin Kumar
2. Software Application Event Driven Architecture (EDA) design pattern | Tutorial with example
 
06:06
This video explains about one among the commonly used software architecture called, event driven architecture EDA, which is also known as message driven architecture. An event can be defined as a, 'significant change in state'. So whenever there is a significant change in the state of a application or a variable, it triggers the event. This event in turn, emits a message or notification. Normally in an event driven architecture of software applications, there will be three roles involved. First is Event Source, where the event occurs and the message is triggered. Second is the Event Consumer, which receives and interpret the message that is triggered from event source. Third is Event bus or the middle ware which receives the message from source and forward it to consumer. Though this event bus is an optional element, it recommended to have it in the event driven architecture. There are two types of typologies are used in event driven architecture. Mediator topology broker topology The mediator topology is useful for events that have multiple steps and require some level of orchestration to process the event. There are four main types of architectural components within the mediator topology: event queues, an event mediator, event channels, and event processors. The broker topology differs from the mediator topology in the way that, there is no central event mediator. Rather, the message flow is distributed across the event processor components in a chain like fashion through a lightweight message broker. This topology is useful when you have a relatively simple event processing flow and you do not want central event orchestration. There are two main types of architectural components within the broker topology: a broker component and an event processor component.
Views: 1431 Kavin Kumar
25. PMP Tutorial | Explain how create WBS Process | ITTO,input,tools and techniques,output
 
03:13
This PMI PMP PMBOK based tutorial explains about the process of creating WBS work breakdown structure along with the ITTO, input,output,tools and techniques. PMI PMP Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. The key benefit of this PMBOK based PMI PMP process is that it provides a structured vision of what has to be delivered. The WBS work breakdown structure is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The planned work is contained within the lowest level of WBS components, which are called "work packages". A work package can be used to group the activities where work is scheduled and estimated, monitored and controlled. In the context of the WBS, work refers to work products or deliverables that are the result of activity and not to the activity itself. Let's see the Input ,Tools and techniques and ,output of create WBS process. Here the inputs of PMI PMP Create WBS based on PMBOK-5. Scope management plan Project scope statement Requirements documentation Enterprise environmental factors Organizational process assets Tools and techniques used in this PMI PMP Create WBS based on PMBOK-5 process. Decomposition Expert judgement Output of this PMI PMP Create WBS based on PMBOK-5 process. Scope baseline Project documents updates
Views: 609 Kavin Kumar
13. ITIL service strategy Process | business relationship Management purpose,scope,objectives
 
02:30
This ITIL core foundation video explains about the scope,purpose and objectives of business relationship management process which is part of service strategy. Purpose of business relationship To establish and maintain relationship between the service provider and customer based on understanding the customer and their business needs. To identify customer needs and ensure that the service provider is able to meet these needs as business needs change over time and between circumstances. Objectives of business relationship Ensure that the service provider understands the customer perspective of service, and is therefore able to prioritise its services and service assets appropriately. Ensure high levels of customer satisfaction, indicating that the service provider is meeting customer’s requirements. Establish and maintain a constructive relationship between the service provider and the customer based on understanding the customer and their business drivers. Identify changes to the customer environment that could potentially impact the type, level or utilisation of services provided. Work with customers to ensure that services and service levels are able to deliver value. Identify technology trends that could potentially impact the type, level or utilisation of the services provided. Scope of business relationship Business outcomes that the customer wants to achieve. Services that are currently offered to the customer, and the way in which they are used by the customer. Understanding who is responsible for the service, what levels of service have been agreed, the quality of service delivered and any changes that are anticipated. Understanding who is responsible for the service, what levels of service have been agreed, the quality of service delivered and any changes that are anticipated. How to optimize services for the future. How the service provider is represented to the customer.
Views: 320 Kavin Kumar
98. PMP Tutorial | Project control Procurement process overview | ITTO,input,tools,output
 
03:39
Let's learn about the project Control Procurements process in this PMI PMP PMBOK based project management tutorial video. Control Procurements is the process of managing procurement relationships, monitoring contract performance ,and making changes and corrections to contracts as appropriate. The key benefit of this Control Procurement process is that it ensures that both the seller’s and buyer’s performance meets procurement requirements according to the terms of the legal agreement. Control Procurement belongs to monitoring and control process group. - Settlement of all claims and disputes through negotiation is the preferred method. Here the ITTO,input,tools,techniques,output of PMP control Procurement process Per PMP PMBOK-5, Input of project control Procurement process is, .1 Project management plan .2 Procurement documents .3 Agreements .4 Approved change requests .5 Work performance reports .6 Work performance data PMP PMBOK-5 says following tools and techniques are used in project control Procurement process .1 Contract change control system .2 Procurement performance reviews .3 Inspections and audits .4 Performance reporting .5 Payment systems .6 Claims administration .7 Records management system Following are the output of project control Procurement process as per PMP pmbok-5 .1 Work performance information .2 Change requests .3 Project management plan updates .4 Project documents updates .5 Organizational process assets updates
Views: 829 Kavin Kumar
24. PMP tutorial | What is project scope statement | Part of project scope statement
 
03:22
This PMI PMP project management tutorial video explains what is a project scope statement and how project scope statement is developed and parts of project scope statement. The project scope statement is the description of the project scope, major deliverables, assumptions, and constraints. The project scope statement documents the entire scope, including project and product scope. PMP project scope statement describes, in detail, the project’s deliverables and the work required to create those deliverables. The detailed project scope statement, either directly, or by reference to other documents, includes the following: •Product scope description •Acceptance criteria •Deliverable •Constraints •Assumptions
Views: 1908 Kavin Kumar
36. ITIL | IT service desk function Overview | Types | Service Operation
 
02:54
This ITIL foundation tutorial video explains about the overview, purpose, scope, objectives of IT serice desk or IT help desk function which is part of the service operation. IT service desk structure: A service desk can be defined as a functional unit made up of a dedicated number of staff responsible for dealing with a variety of service events, often made via telephone calls, web interface, or automatically reported infrastructure events. Acts as daily single point of contact for IT users. The objectives of service desk are as follows. To restore the 'normal service' to the users as quickly as possible. Operate as level 1 for incident management and request fulfillment, i.e. log calls, do initial diagnosis and investigation and if possible resolve and close. Manage incidents throughout its life cycle, which also includes user communication and technical and hierarchical escalations. Conducting customer or user satisfaction survey. Now we will look into the different types of organization structure of service desk functionality. First is local one. This is located physically close to the user community it serves and provides clear visible presence. This type can be used when there are Language and cultural or political differences, different time zones, or for a specialized group. Sometimes it can often be inefficient and expensive to resource if it serves for a low call volume. Next is centralized where Service desk is deployed at one central physical location. It is More efficient and cost effective, allowing fewer overall staff to deal with a higher volume of calls. Next model is virtual service desk, which has the impression of single, centralized service desk, through the use of technology and tools to create a virtual service desk. Single visible service desk which may actually be run by staff in multiple locations. Allows for 'homeworking', secondary support group, off shoring or outsourcing or any combination necessary to meet user demand. In Follow the sun service desk structure, Multiple service desks will work across time zones to provide 24 bar 7 service. last one is Specialized model where Specialist groups within the overall service desk structure will address the incidents relating to a particular IT service. Incidents will be routed directly (normally via telephony ,IVR or a web based interface) to the specialist group. For example, we can say a specialized service desk that only supports the ERP system of an organization.
Views: 902 Kavin Kumar
17. PMP Close Project Process tutorial | ITTO | Input,tools and techniques,Output
 
02:34
Let's explore the details of closing project process in this PMP project management tutorial video along with ITTO,Input,output,tools and techniques. Close Project or, Phase is the process of finalizing all activities across all of the Project Management Process Groups to formally complete the project or phase. The key benefit of this process is that it provides lessons learned, the formal ending of project work, and the release of organization resources to pursue new endeavors. Key activities of this process are as follows. Actions and activities necessary to satisfy completion or exit criteria for the phase or project; Actions and activities necessary to transfer the project’s products, services, or results to the next phase or to production and or operations; Activities needed to collect project or phase records, audit project success or failure, gather lessons learned and archive project information for future use by the organization. Here the inputs. Project management plan The project management plan becomes the agreement between the project manager and project sponsor, defining what constitutes project completion. Accepted deliverables Accepted deliverables may include approved product specifications, delivery receipts, and work performance documents. Organizational process assets Next let's have a look at Tools and techniques used in this process. Expert judgement Expert judgement is applied when performing administrative closure activities. Analytical techniques Meetings Meetings may be face-to-face, virtual, formal, or informal. This may include project team members and other stakeholders, involved in or affected by the project. Now let's see the output of this process. Final product, service, or result transition This output refers to the transition of the final product, service, or result that the project was authorized to produce Organizational process assets updates
Views: 751 Kavin Kumar
12. PMP Tutorial | Develop Project Management Plan | ITTO | Input,Tools and techniques,output
 
02:00
This PMP tutorial covers the process of Develop Project management plan with ITTO, input, tools and techniques,output which is part of the integrated project management knowledge area. As per PMP PMBOK-5 definition, Develop Project Management Plan is the process of defining, preparing and coordinating all subsidiary plans and integrating them into a comprehensive project management plan. The key benefit of this process is a central document that defines the basis of all project work. This plan defines how the project is executed, monitored and controlled and closed. Generally the PM plan progressively elaborated as the project evolves and changes are controlled by integrated change control board. Here the inputs. Project charter The size of the project charter varies depending on the complexity of the project and the information known at the time of its creation. Outputs from other processes Any baselines and subsidiary plans that are an output from other planning processes are inputs to this process. Enterprise environmental factors Organizational process assets Next let's have a look at Tools and techniques used in this process. Expert judgement Facilitation techniques Facilitation techniques have broad application within project management processes and are used to guide the development of the project management plan. Now let's see the output of this process. Project management plan The project management plan is the document that describes how the project will be executed, monitored, and controlled .
Views: 1237 Kavin Kumar
10. PMP Tutorial | project integration management knowledge area | processes |
 
03:07
Project Integration ,Management includes the processes, and activities to identify, define, combine,unify, and coordinate the various processes ,and project management activities; within the Project management process groups, which are crucial for successfully completing the project. Project Integration Management, includes making choices about resource allocation, making trade-offs among competing objectives, and alternatives, and managing the interdependencies, among the project management ,Knowledge Areas. There are six processes are there in this knowledge area, as follows. Develop Project Charter Develop Project Management Plan Direct and Manage Project Work Monitor and Control Project Work Perform Integrated Change Control Close Project or Phase
Views: 881 Kavin Kumar
3. ITIL  | what is service, service management and stake holder
 
01:54
This video explains about the fundamental core concepts of ITIL foundation, what is a service, what is service management, and who are the stake holders. what is a service. As per ITIL, service can be defined as, A means of delivering value to customers by facilitating outcomes that customer want to achieve, without the ownership of specific costs or risks. In a service, - Costs and risks are transferred to service provider. - Customers focus on outcomes versus means. Stakeholders are the one's who are interested in an organization, project or service, and may be interested in the activities, targets, resources or deliverables from service management. Stakeholders examples Organizations Service providers customers Consumers users partners employees shareholders owners and suppliers
Views: 421 Kavin Kumar

Chromatische zahl beispiel essay
La courthouse case summary
Essay paper on faith
Demystifying dissertation writing and editing
Surdas in hindi essay