2555 Courses near Maidenhead

In this course you will understand what mentoring is about, understand your roles in the process. Gain self-insight into your own interpersonal style and way of relating to others that may affect mentoring interactions.

Gold CSCS Card NVQ Level 3 Diploma in Construction Contracting Operations This qualification is designed for those in a technical job role, This qualification is appropriate for employees in the construction and built environment sector working at a technical level in disciplines such as estimating, buying, planning, surveying, site technical support and design co-ordination. You could be site-based and have responsibility for functions such as dimensional control, surveys, physical testing, and work planning. You may work across one or more of the following pathways: Estimating Buying Planning Surveying Site Technical Support Design Co-Ordinator General Induction - As soon as you register you will be given a dedicated assessor. They will arrange an induction and together with your assessor, you will get to decide on the pathway which best proves your competency. The induction is used to plan out how you will gather the relevant evidence to complete the course. During the course - The assessor will work with you to build a portfolio of evidence that allows you to showcase your knowledge, skills and experience. The assessor will also regularly review and provide you with feedback. This will allow you to keep on track to progress quickly. You will be assessed through various methods such as observations, written questions, evidence generated from the workplace, professional discussion and witness testimonials. On completion - Once all feedback has been agreed, the Internal Quality Assurer will review your portfolio and in agreement with your assessor the certificate will be applied for. To download our PDF for this course then please click here.

Implementing Scrum for Teams: In-House Training 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

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

Scrum Master Workshop: In-House Training 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. What you will Learn You'll learn how to: Comprehend the Agile Manifesto and mindset Explain the fundamental principles of Scrum Guide the Scrum team in their responsibilities Write requirements in the form of user stories Define Ready and Done 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 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

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

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?

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

Writing and Managing Requirements Documents: In-House Training This course is part of IIL's Business Analysis Certificate Program (BACP), a program designed to help prepare individuals pass the IIBA™ Certification exam to become a Certified Business Analysis Professional (CBAP™). Learn more at www.iil.com/bacp. Once a business analyst has completed the information gathering and analysis to produce the solution to a business problem, the results must be documented for all stakeholders to see and understand. This course will enhance the skill set needed for writing and managing the complex readership that business analysts interact with on a day-to-day basis. What you will Learn Upon completion, participants will be able to: Write an understood requirements document that is approvable and acceptable Validate a requirements document Manage the changes to requirements documents through the SDLC Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide The business analyst and the product/project life cycle The requirements documentation process Planning for Effective Requirements Documentation Overview of requirements planning Planning for validation Planning for verification: well-formed criteria Planning for verification: understood and usable criteria Writing Effective Requirements Documents Overview of writing requirements documents Using a standard structure / template Applying formatting techniques Meeting the challenge of writing non-functional requirements Baselining Requirements Documents Overview of the requirements baseline process Validation Verification Approval Managing Requirements Change through the Product Life Cycle Overview of requirements change management Establishing a formal change management process Tracing requirements through design and development (build, test, and implementation) Following through to post-implementation (transition and early production)

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?