1346 Agile courses

Duration 3 Days 18 CPD hours This course is intended for Team leaders, managers, executives, and other business and IT professionals who lead others as well as Individual contributors ready for transformational self-development as a leader. Overview Recognize vulnerability as the emotion we feel during times of uncertainty, risk, and emotional exposure. Explain why courage requires vulnerability. Establish a link between what I learned and behaviors I want to change. Recognize the critical role that self-awareness plays in daring leadership. Give examples to support how armor - not fear -is the greatest obstacle to daring leadership. Identify the four skill sets that make up courage: rumbling with vulnerability, living into our values, BRAVING trust, and learning to rise. Recognize that courage is a collection of four skill sets that are measurable, observable, and teachable. Recognize that vulnerability is the birthplace of many of the behaviors that define daring leadership, including creativity, accountability, and difficult conversations. Give examples of why daring leadership requires showing up for hard conversations and rumbles, including giving and receiving feedback. This workshop is all about your own leadership self-awareness, identifying your call to courage as a leader and the learning, practice and integration of the four courage skills sets so you can show up authentically in life and leadership. Dare to Lead? is the ultimate playbook for developing brave leaders and courageous cultures. The greatest barrier to daring leadership is not fear; the greatest obstacle is armor ? how we self-protect when we feel uncertainty, risk and emotional exposure. Learn the skills to move from armored leadership to daring leadership. Daring leaders are self-aware, know how to have hard conversations, hold themselves and others accountable, build trust, lead with empathy and connection, take smart risks that lead to innovation, reset quickly after disappointments and setbacks, and give and receive feedback. This interactive curriculum is delivered in five, half-day sessions and is based on the research by Bren‚ Brown. This course comes with a PDF workbook and an Amazon gift card to purchase the Dare to Lead? book in the version of your choice. You also have access to a series of leadership and personal development assessments and exclusive training videos led by Dr. Bren‚ Brown. At the end of the event, a digital badge is awarded to those who complete 24 hours of course content. The Heart of Daring Leadership Permission Slips Container Building Armored Leadership versus Daring Leadership Call to Courage Assembling Our Armor Building Grounded Confidence to Replace our Armor Aplying the 5Cs Self-Awareness & Emotional Literacy Developing Emotional Literacy Getting Curious About Emotions Exploring the Iceberg The Myths of Vulnerability Rumbling with Vulnerability The Six Myths of Vulnerability Exploring Your Arena Shame Resilience Shame 101 Defining Shame The Physiology of Shame Shame Shields How Shame Shows Up in Organizations How Shame Shows up at Work Empathy and Self-Compassion Attributes of Empathy What Does Empathy Look Like? Empathy Misses Comparative Suffering Self-Compassion Talk to Yourself the Way You Talk to Someone You Love Empathy & Self-Compassion Commitment Supplemental Exercise: Kristin Neff?s Self-Compassion Scale Supplemental Exercise: Putting Empathy, Curiosity, and Rumble Tools in Action Living Into Our Values Living Into Our Values Values Clarification Taking Values from Professing Words to Practicing Behaviors Grounded Confidence and Rumbling Skills Grounded Confidence and Rumbling Skills Rumble Starters The 5Cs of Strategic Thinking, Decision Making, and Delegation Using the 5Cs Supplemental Exercise ? Gritty Faith & Gritty Facts Supplemental Exercise ? Horizon Conflict Engaged Feedback Giving Engaged Feedback Recognizing Defensiveness in Feedback Conversations BRAVING Trust BRAVING Trust Square Squad Rumbling with Self-Trust Trust with Others Trust on Teams Rumbling with Living BIG Learning to Rise: The Reckoning Learning to Rise: The Rising Strong Process The Rising Strong Process Getting Emotionally Hooked Offloading Hurt: Barriers to Reckoning with Emotion Strategies for Reckoning with Emotion The Rumble and The Revolution Writing My SFD The Delta The Revolution: When the Process Becomes a Daily Practice Supplemental Exercise ? Reset and Resilience Practices Integration Dare to Lead Integration Plan

Learn how to use culture for enhancing the employee performance with the Lean Leadership and Change Management Diploma course. The course is designed to teach you Lean leadership and change management. A lean leader will change the way your thinking and the way you lead your organisation. Lean leadership is the approach that teaches you how to improve the overall performance of your organisation by bringing change in its culture. You will learn about the lean culture and lean leadership. The course illustrates the history of lean, the essential principles and practices, and the fundamental functions of the lean leader. There are two ways of lean implementation. You can change and redesign the whole process, or you may acquire the habits of problem-solving and continuous improvement. The course covers these two processes and helps you to choose the right methods for you. The purpose of the course is to prepare you for applying the lean leadership approach of lean culture in your organisation. Assessment: At the end of the course, you will be required to sit for an online MCQ test. Your test will be assessed automatically and immediately. You will instantly know whether you have been successful or not. Before sitting for your final exam you will have the opportunity to test your proficiency with a mock exam. Certification: After completing and passing the course successfully, you will be able to obtain an Accredited Certificate of Achievement. Certificates can be obtained either in hard copy at a cost of £39 or in PDF format at a cost of £24. Who is this Course for? Diploma in Management Skills is certified by CPD Qualifications Standards and CiQ. This makes it perfect for anyone trying to learn potential professional skills. As there is no experience and qualification required for this course, it is available for all students from any academic background. Requirements Our Diploma in Management Skills is fully compatible with any kind of device. Whether you are using Windows computer, Mac, smartphones or tablets, you will get the same experience while learning. Besides that, you will be able to access the course with any kind of internet connection from anywhere at any time without any kind of limitation. Career Path After completing this course you will be able to build up accurate knowledge and skills with proper confidence to enrich yourself and brighten up your career in the relevant job market. Introduction Why 00:04:00 What 00:04:00 Curriculum 00:05:00 How 00:04:00 What is Culture 00:06:00 Culture Drivers 00:08:00 Resources 00:05:00 Activity 1 00:03:00 The House of Lean House of Lean 00:03:00 Evolution 00:04:00 Shingo 00:09:00 Honda 00:09:00 Activity 2 00:02:00 Lean Culture Principles & Practices JIT 00:07:00 Kanban 00:08:00 Continuous Improvement and Leadership 00:04:00 Waste Intro 00:10:00 Forms of Waste 1 00:06:00 Management Waste 00:07:00 Activity3 00:02:00 Scientific Method 00:07:00 Gemba Walk 00:06:00 Heijunka 00:05:00 Visual Display 00:07:00 Activity 4 00:02:00 Kaizen 00:06:00 The Job of the Lean Leader - To Challenge and To Serve Lean Leadership Intro 00:07:00 The Mind of the Lean Leader 00:04:00 The Mind of the Lean Leader - Transitions 00:07:00 Lean Leadership1. External Challenge 00:05:00 Lean Leadership 2. Internal Challenge 00:06:00 Activity 5 00:02:00 Lead WSA 00:02:00 Be the Model 00:03:00 Coach Others 00:07:00 Motivation 00:04:00 Reinforce Your Strategy 00:04:00 Activity 6 00:01:00 Intrinsic Reinforcement 00:08:00 Getting to Lean - Designing the System for a New Culture Paths to Lean 00:05:00 How You Change 00:03:00 Design Thinking 00:08:00 Design Process 00:08:00 Capability Analysis 00:05:00 Charter 00:05:00 Activity 7 00:02:00 Design Team 00:06:00 Discovery 00:06:00 Discover the Process 00:07:00 Dream 00:07:00 Design technical 00:07:00 Design Structure 00:08:00 Social Design 00:06:00 Activity 8 00:03:00 VON Case Study 00:10:00 WSA Summary 00:04:00 Activity 9 00:02:00 The Habits of Continuous Improvement - The Team Kata Why Teams 00:06:00 Types of Teams 00:06:00 Team Charter 00:05:00 Team Maturity 00:05:00 Team Roles and Responsibilities 00:05:00 Team Agenda 00:05:00 Activity 10 00:02:00 Facilitation 1 00:06:00 Facilitation 2 00:04:00 Team Scoreboard 00:07:00 Activity 11 00:01:00 Map Team's Work 00:03:00 Attitudes 00:05:00 Five Whys 00:03:00 PDSA 1 00:04:00 PDSA 2 00:04:00 PDCA example 00:01:00 Activity 12 00:01:00 A3 00:05:00 Standard Work 00:05:00 Leader Standard Work 00:04:00 Activity 13 00:02:00 Summary 00:03:00 Resources Resources - Lean Leadership and Change Management Diploma 00:00:00 Certificate and Transcript Order Your Certificates and Transcripts 00:00:00

Developing the Business Case Business analysts must be able to create business case documents that highlight project benefits, costs, and risks. The business case is based on the real business need to be solved. These become parts of proposals, feasibility studies, and other decision support documents. This course teaches the purpose, structure, and content of a business case. It presents the basic techniques for determining financial ROI, non-tangible benefits, and the probability of meeting expectations. What you will Learn At the end of this program, you will be able to: Perform feasibility studies Justify the business investment to solve the business problem Prepare an effective business case document Plan and implement a business case approval process Foundation Concepts The role of the BA An introduction to the BABOK® Guide The business analyst and the product / project life cycle (PLC) The business case deliverable Introducing the Business Case Process The BA and strategy analysis The BA and the business case process (BCP) The BA during the business case process (BCP) The BA after the business case process (BCP) Importance of defining solution performance metrics Defining the Business Need Overview of defining the business need Business needs: problem / opportunity statement Product vision Objectives and constraints Exploring Business Case Solutions Overview of exploring solutions Solution identification for feasibility Solution definition for analysis Assessing project risks Justifying the Business Case Overview of justifying the business case Qualitative justification Quantitative justification Approving the Business Case Overview of business case approval Developing recommendations Preparing the decision package - documents Preparing the decision package - presentations

Developing the Business Case: In-House Training Business analysts must be able to create business case documents that highlight project benefits, costs, and risks. The business case is based on the real business need to be solved. These become parts of proposals, feasibility studies, and other decision support documents. This course teaches the purpose, structure, and content of a business case. It presents the basic techniques for determining financial ROI, non-tangible benefits, and the probability of meeting expectations. What you will Learn At the end of this program, you will be able to: Perform feasibility studies Justify the business investment to solve the business problem Prepare an effective business case document Plan and implement a business case approval process Foundation Concepts The role of the BA An introduction to the BABOK® Guide The business analyst and the product / project life cycle (PLC) The business case deliverable Introducing the Business Case Process The BA and strategy analysis The BA and the business case process (BCP) The BA during the business case process (BCP) The BA after the business case process (BCP) Importance of defining solution performance metrics Defining the Business Need Overview of defining the business need Business needs: problem / opportunity statement Product vision Objectives and constraints Exploring Business Case Solutions Overview of exploring solutions Solution identification for feasibility Solution definition for analysis Assessing project risks Justifying the Business Case Overview of justifying the business case Qualitative justification Quantitative justification Approving the Business Case Overview of business case approval Developing recommendations Preparing the decision package - documents Preparing the decision package - presentations

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

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?

Business Analysis Fundamentals: In-House Training 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

Use Cases for Business Analysis The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?

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?

Use Cases for Business Analysis: In-House Training The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?