65704 Courses

Project Leadership Skills (In-Person) To be effective within an organization, project managers need to have a wide variety of skills and abilities. Included among these are: creating and executing on a vision; motivating others; influencing without authority; networking; communicating up, down and laterally; negotiating; managing stakeholders; and managing conflict. This highly interactive workshop focuses on building the soft skills that are critical to leading a team and creating sustainable business change. Participants will gain insight into the social science as well as the brain science behind motivating and empowering others. They will learn and experiment with a variety of influencing strategies and tactics. Working in pairs as well as small groups, they will collaborate with others to brainstorm, share experiences, and apply concepts to everyday challenges. Participants will also discover their personal communication preferences, strengths, and blind spots and will gain insight into how best to communicate with others they find 'difficult.' They will gain insight into managing the people side of change, learning strategies for dealing with each step in the process. Hands-on negotiation and conflict management activities enhance the theoretical learning, grounding it in real life and making it actionable. Interweaving role play with experiential learning and group activities, this course will help participants refine a skill set that is invaluable to their organization, and one that transfers easily across their professional and personal lives. What you will Learn At the end of this course, you will be able to: Explain the importance of vision in driving motivation and engagement Apply science-based research to better motivate those around you Strategically leverage both personal and positional power to achieve positive project results Determine influencing and networking strategies needed for personal growth Identify ways to problem solve communication challenges when others have different personality styles Connect stakeholder expectations to project success criteria Assess key stakeholders across various dimensions of complexity Apply the four rules of principled negotiation to a real-life conflict situation Recognize key aspects of a physiological response to conflict Utilize selected tools and techniques to 'defuse' an emotional situation Leverage various strategies and tactics to successfully deal with ambiguity at work Getting Started / Foundation Concepts Introductions Course structure, goals, and objectives Beginning a personal action plan Managing Vision and Purpose / Motivating Others Communicating and aligning around vision Tying the present to the future The importance of purpose The art and science of motivation Networking and Influencing Positive politics and project success Types of power within organizations Power and influence Networking best practices Communication The medium and the message Personality and communication styles Communication challenges Stakeholder Management and Negotiation Identifying stakeholders Analyzing stakeholders Negotiation basics Principled negotiation Conflict Management Dynamics of conflict The anatomy of conflict Conflict management approaches and tools Dealing with ambiguity

Assuring Quality Through Acceptance Testing: In-House Training It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. It is the business analyst's job to define the business problem to be solved by IT. It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. The business analyst is not only concerned with the testing itself, but also with the management and monitoring of the users doing the acceptance testing, and recording, analyzing, and evaluating the results. What you will Learn Upon completion, participants will be able to: Create a set of acceptance test cases Manage and monitor an acceptance test stage where users perform the testing Work with the development team in the systems testing stage Assess the solution once it is in the business environment Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide BA roles and relationships through the project life cycle Introduction to assuring software quality through acceptance testing The Scope of IT Testing Overview of testing stages The testing process Testing documentation Pre-Acceptance Testing The BA's role in testing Early development testing stages (unit and integration) Late development testing stage (system) The Acceptance Test Stage - Part I (Planning, Design, and Development) Overview of user acceptance testing Acceptance test planning Designing user acceptance tests Developing individual user acceptance test cases Building effective user acceptance test scenarios The Acceptance Test Stage - Part II (Execution and Reporting) Operating guidelines Execution Reporting Post-Acceptance Testing Overview Project implementation Project transition (project closure) Production through retirement Testing Commercial Off-the-Shelf (COTS) Software Overview Selecting the software Implementing the software Summary What did we learn and how can we implement this in our work environments?

Business Analysis Fundamentals This course is part of IIL's Business Analysis Certificate Program (BACP), a program designed to help prepare individuals to pass the IIBA® Certification exam to become a Certified Business Analysis Professional (CBAP™). This course teaches participants the overall process of business analysis and where it fits in the bigger picture of the project life cycle and the business context. The course is interactive and combines discussion, active workshops, and demonstrations of techniques. The goal is bottom-line results that cut through the real-world problems facing people seeking to improve the way they operate to develop new and improved systems and products or otherwise deliver results through project performance. What you will Learn At the end of this program, you will be able to: Define the solution scope Work with the development team in the systems testing stage Ensure the solution is usable in the business environment Foundation Concepts Defining the business analyst (BA) function The role of the BA as change agent An introduction to the BABOK® Guide BA roles and relationships through the project life cycle (PLC) Business Analysis Planning and Monitoring Overview of business analysis planning and monitoring (BAP&M) Business analysis planning and monitoring - process and tools Business analysis planning and monitoring - roles and responsibilities Business analysis planning and monitoring - governance, information management, and performance improvement Elicitation and Collaboration Overview of elicitation and collaboration Elicitation and collaboration techniques Requirements Life Cycle Management Overview of requirements life cycle management Requirements life cycle management task details Strategy Analysis Overview of strategy analysis Analyze current state Define future state Assess risks Define change strategy Requirements Analysis and Design Definition Overview of requirements analysis and design definition (RA&DD) The anatomy of requirements RA&DD task descriptions RA&DD techniques Solution Evaluation Overview of solution evaluation Solution evaluation tasks Solution evaluation in development stages Underlying Competencies Overview of underlying competencies (UC) Underlying competencies

Project Requirements Management Poor requirements definition and lack of adequate change control procedures to requirements and scope are the primary contributors to project difficulty and failure. This workshop will provide you with the knowledge, tools, and techniques required to minimize or avoid these pitfalls. What You Will Learn You'll learn how to: Explain the Requirement Management process within the project lifecycle Understand requirements terminology and structure for definition and development Apply and evaluate techniques to identify and draw out requirements from people, places, and things Create models to conceptualize the requirements landscape and communicate effectively with stakeholders Indicate the importance of requirements prioritization Write SMART requirements using structured language skills Understand how to apply checklists, questionnaires, and document templates in the requirements development process Verify and validate requirements to support project success Effectively manage changing requirements across the project lifecycle Requirements Framework Requirements definitions The importance of requirements Type of requirements Developing Requirements: The Process High-level requirements development and management process Stakeholder involvement in requirements management Progressive elaboration in requirements management Elicit Requirements Requirements-Gathering Approach Sources of Information Requirements-Gathering Techniques Analyze Requirements Models and Requirements Using Use Cases Prioritizing Requirements Specify Requirements Specifying Requirements Essential Technical Writing Skills SMART Requirements Quality Attributes Monitor and Control Requirements Why and When Requirements Change Change Management and Control Requirements Traceability Validating and Verifying Requirements Validating Requirements Verifying Requirements Using Checklists

Assuring Quality Through Acceptance Testing It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. It is the business analyst's job to define the business problem to be solved by IT. It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. The business analyst is not only concerned with the testing itself, but also with the management and monitoring of the users doing the acceptance testing, and recording, analyzing, and evaluating the results. What you will Learn Upon completion, participants will be able to: Create a set of acceptance test cases Manage and monitor an acceptance test stage where users perform the testing Work with the development team in the systems testing stage Assess the solution once it is in the business environment Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide BA roles and relationships through the project life cycle Introduction to assuring software quality through acceptance testing The Scope of IT Testing Overview of testing stages The testing process Testing documentation Pre-Acceptance Testing The BA's role in testing Early development testing stages (unit and integration) Late development testing stage (system) The Acceptance Test Stage - Part I (Planning, Design, and Development) Overview of user acceptance testing Acceptance test planning Designing user acceptance tests Developing individual user acceptance test cases Building effective user acceptance test scenarios The Acceptance Test Stage - Part II (Execution and Reporting) Operating guidelines Execution Reporting Post-Acceptance Testing Overview Project implementation Project transition (project closure) Production through retirement Testing Commercial Off-the-Shelf (COTS) Software Overview Selecting the software Implementing the software Summary What did we learn and how can we implement this in our work environments?

Risk Management for IT Projects IT projects may have direct bottom-line impact on the organization, cost millions of dollars, cause organizational change and change the way the organization is perceived by clients. Many IT projects are notoriously hard to predict and are filled with risk. IT Risk Management takes a comprehensive look at IT project risk management using PMI's PMBOK® Guide Risk Management Model in the context of IT Project Life Cycle phases. The goal of this course is to arm the practitioner with a rigorous, common-sense approach to addressing uncertainty in projects. This approach includes the ability to influence project outcomes, avoid many potential project risks, and be ready to calmly and efficiently respond to unavoidable challenges. What you will Learn You'll learn how to: Describe the risk management process, using the PMBOK® Guide's standard models and terminology Discuss the potential barriers to managing risk effectively in IT project organizations Develop an effective risk management plan for IT projects Identify project risks using IT-specific, practical tools Analyze individual risk events and overall project risk using IT-specific, practical approaches Plan effective responses to IT-specific risk based on the results of risk analysis and integrate risk responses into project schedules and cost estimates Manage and control risk throughout the IT project life cycle Implement selected elements of IT project risk management on your next project Foundation Concepts Basic concepts and purpose Risk and project constraints Risk and corporate cultures Risk management and IT PLC standards Plan Risk Management for IT Projects Plan Risk management process Plan Risk management activities Design a standard template Assess the project-specific needs Tailor the template Produce a project-specific risk management plan Gain consensus and submit as part of overall project plan A risk management plan of IT projects Identify Risks for IT Projects Identify risk process overview Risk categories and examples Risk identification tools Risk events by project life-cycle phases Perform Risk Analysis for IT Projects Perform qualitative risk analysis overview Core qualitative tools for IT projects Auxiliary qualitative tools for cost and schedule estimates When to use quantitative analysis for IT projects Plan Risk Response for IT Projects Plan risk response overview Active risk response strategies for IT projects (Threat and Opportunity) Acceptance and contingency reserves Contingency planning for IT projects Plan risk responses for IT projects Implement Risk Response for IT Projects Implement Risk Responses Executing Risk Response Plans Techniques and Tools Used Continuous Risk Management Monitor Risks for IT Projects Monitor risks overview Monitor risks tips for IT projects Technical performance measurement systems Risk management implementation for IT projects

Agile Sprint Planning The goal of the course is to provide you and your team with the ability to develop effective and realistic Sprint plans. Without effective Sprint Plans, iterations are set up for failure. But Sprint Planning cannot be improved on its own, in isolation. The Scrum processes are highly intertwined and influence each other. The surrounding artifacts, events, and roles must be examined closely, and enhanced, in order to improve Sprint Planning. This course will remind you of the theory to reinforce the principles, but will concentrate on next-level skills, so that you and the team are able to create realistic and usable Sprint Plans. This course is not introductory. You are already aware of the Scrum framework and have been implementing Scrum on your projects. Now is the time to improve efficiency and effectiveness, to facilitate successful Agile projects. What you will Learn You'll learn how to: Identify and correlate the key symptoms and root causes of ineffective sprint plans Improve key Product Backlog elements Evaluate Agile roles in sprint planning Appraise key product practices Enhance project transparency The Product Backlog User stories Acceptance Criteria Backlog Refinement Supporting Roles Product Owner (the Backlog) Development Team Stakeholders and SMEs Supporting Product Practices Roadmaps and release plans and story maps Definition of Done Technical Debt Transparency Daily Scrums Information radiators Retrospectives Sprint Planning Capacity and Velocity Sprint Planning Meetings The Sprint Backlog Summary What did we learn, and how can we implement this in our work environments?

Implementing Scrum for Teams Scrum is an iterative, incremental framework for developing products. It allows the team to deliver a potentially shippable set of functionalities for each iteration, providing the agility needed to respond to rapidly changing requirements. These characteristics have led to Scrum becoming the most popular method in the world of Agile projects. This two-day course provides a practical approach to implementing the Scrum method on your projects. You will learn how to initiate a Scrum project, how to build a Product Backlog, containing user stories, and how to plan and estimate releases and iterations. You will learn how to conduct Scrum events, such as the Sprint Planning Meeting, and how to track progress during an iteration. You will apply what you learn in a series of hands-on, team-based activities and simulations that take you through the entire Scrum process. The overall goal of the course is to enable you to successfully apply the Scrum method on appropriate projects in your environment. What you will Learn At the end of this program, you will be able to: Teach-back Agile and Scrum foundation concepts Initiate a Scrum Project Conduct Team Sprint Planning and Sprint Review meetings Develop Release Plans (including effective user stories and priorities) Build a Sprint plan (including effective estimates) Executive a Sprint (including essential Scrum ceremonies) Implement Scrum in your environment Foundation Concepts Agile Mindset, Values, and Tenets Agile Benefits and Methods Scrum Overview Teams: Self-Managing, Self-Organizing, and Self-Improving Initiating a Scrum Project 'Sprint Zero' Activities Defining the Vision The Product Backlog and User Stories Acceptance Criteria Story Map Planning Releases Planning releases Estimating user stories Prioritizing user stories Selecting a Sprint length Estimating velocity Creating a release plan Planning a Sprint The Sprint Planning Meeting Building the Sprint Backlog Creating a Sprint Plan Running a Sprint Conduct a Sprint Burn-down and Burn-up Charts Negotiating Changes During a Sprint The Sprint Review Meeting Sprint Retrospective Releasing into Production Closing the Scrum Project Implementing Scrum Scrum Simulation Exercise Conditions of Success for Implementing Scrum

Recovering Troubled Projects: In-House Training Despite our best intentions, many of the projects that organizations undertake either don't achieve their intended business results or end in complete failure. Most seasoned project managers have had their share of experiences with difficult or troubled projects and unless they are careful, they will encounter more. This workshop does not focus on 'failed' projects but rather on those projects which without appropriate intervention would be headed for failure. Failed projects are those beyond help and which should be terminated. Here we focus on projects that are salvageable. It is an exercise-driven, no-nonsense, professional practice-focused workshop positioning the participant to immediately apply the tools and lessons learned in the classroom. The workshop employs the use of both illustrative and practical/working case studies. Illustrative case studies will examine insights from real-world troubled projects. Participants will be asked to bring descriptions of their own examples of troubled projects on which they're currently working or on which they have worked in the past. A number of these will be used as the basis for the practical/working case studies. The approach builds on and complements the disciplines addressed in Project Management Institute's PMBOK® Guide and also addresses issues that arise when managing projects in a complex environment. What You Will Learn You will learn to: Recognize the value of a structured project recovery process Explain the reasons most projects fail Analyze the causes of a project's troubles Construct a negotiation process to use with key stakeholders Apply an effective strategy to planning the recovery effort Manage, evaluate, and adjust the ongoing recovery effort Foundation Concepts Recognizing a troubled project Defining the project recovery process The Reasons Projects Fail Putting failure in perspective Reviewing management issues Analyzing planning issues Exploring complexity issues Assess the Project Stabilizing the project Determining preliminary Go / No-Go Conducting a detailed recovery assessment Negotiate the Recovery Reviewing the basics of negotiation Setting reasonable expectations Obtaining appropriate PM authority Securing key stakeholder support Plan the Recovery Planning for recoveries Rebuilding the project team Reshaping the project plan Managing parallel activities Planning for change management Implement and Adjust the Project Implementing project recoveries Facilitating change Enabling continuous learning Fostering the project team Sustaining stakeholder engagement

Scrum Master Exam Prep This workshop prepares you for the Scrum.org Professional Scrum Master (PSM)™ I certification. A voucher for the exam and the access information you will need to take the exam will be provided to you via email after you have completed the course. NOTE: If you have participated in any of IIL's other Scrum workshops, you can bypass this program and focus on reading/studying the Scrum Guide and taking practice exams from Scrum.org. A Scrum Master helps project teams properly use the Scrum framework, increasing the likelihood of the project's overall success. Scrum Masters understand Scrum values, practices, and applications and provide a level of knowledge and expertise above and beyond that of typical project managers. Scrum Masters act as 'servant leaders', helping the rest of the Scrum Team work together and learn the Scrum framework. Scrum Masters also protect the team from both internal and external distractions. The Professional Scrum Master™ I (PSM I) certificate is a Scrum.org credential that enables successful candidates to demonstrate a fundamental level of Scrum mastery. PSM I credential holders will grasp Scrum as described in The Scrum Guide™1 and recognize how those concepts can be applied. They will also share a consistent terminology and approach to Scrum with other certified professionals. Scrum.org does not require that you take their own sponsored or any preparatory training. However, training can facilitate your preparation for this credential. And this course is based on IIL's Scrum Master Workshop, which is aligned with The Scrum Guide™ and was built based on PSM I credentialed expertise. It will provide you with the information you need to pass the exam and IIL will make the arrangements for your online exam. You will be provided with an exam code and instructions, so that you can take the exam at your convenience, any time you are ready after the course. Passwords have no expiration date, but they are valid for one attempt only. What you will Learn You'll learn how to: Successfully prepare for the Scrum.org PSM I exam Comprehend the Agile Manifesto and mindset Explain the fundamental principles of Scrum, including events, artifacts, and roles Guide the Scrum team in their responsibilities Define Ready and Done Write requirements in the form of user stories Estimate using planning poker and prioritize using MoSCoW Facilitate the team through the 5 Sprint events Fulfill the role of Scrum Master in a Scrum project Create Information Radiators to enable transparency Define the structure of the retrospective Getting Started Introductions Workshop orientation Exam prep preview Foundation Concepts Agile History, Values, and Mindset Introduction to Scrum Scrum events Scrum artifacts Scrum Roles and Responsibilities Product Owner responsibilities Scrum Master responsibilities The Team responsibilities Cross-functional teams Building effective teams The Product Backlog and User Stories The Product Backlog User Stories Definition of Done Backlog grooming Estimating User Stories Story points, planning poker Prioritizing User Stories The Sprint Team capacity and velocity The Sprint Planning Meeting The Sprint Backlog The Sprint Learning to self-manage, self-organize, self-improve Sprint Review and Retrospective Project Progress and Completion The Daily Scrum The Task Board and The Burndown Chart Information Radiators Closing a Scrum Project Summary and Next Steps Review of course goals, objectives, and content Exam prep next steps