1088 Brain courses in Belfast delivered Online

Duration 2 Days 12 CPD hours This course is intended for Executives, Project Managers, Business Analysts, Business and IT stakeholders working with analysts, Quality and process engineers, technicians, corrective action coordinators or managers; supervisors, team leaders, and process operators; anyone who wants to improve their ability to solve recurring problems. Overview Learn how to initiate a root cause analysis and gather data for investigating process and non-process incidentsDemonstrate how to collect data through interviews and analysisApply powerful techniques to identify and know the difference between symptoms and root causesLearn to know when to use the appropriate technique in root cause identification Learn how to avoid future incidents by developing appropriate recommendations to address causal factors and root causes Develop a process to identify systemic problem areas In this course, participants will learn to apply several practical, systematic methods for analyzing incidents and problems to uncover root causes. Understanding of these techniques will be reinforced by classroom exercises. Introduction & Objectives What is a 'Problem?' Why Problems Persist What is A Root Cause? Why Root Causes are important How to Organize for an RCA RCA Roles and Responsibilities Assemble your RCA Team Modes of Communication How to Resolve Conflict Case Study Exercise Select the Problem to Analyze Define the selection criteria Plan and estimate tasks for the team Finalize the plan and gain agreement among your stakeholders Case Study Exercise Define the Problem What to look for - Problem-as-Given (PAG) vs. Problem-as-Understood (PAU) Developing your problem statement Refining the problem specification Case Study Exercise Identify the Source of the Problem Discuss when to use the appropriate analysis technique to determine the problem source Process Diagram Forms & Checklists Statistical Sampling Fishbone Diagram Surveys Charts - Line, Scatter, Bar, & Pie Case Study Exercise Solution Options Analysis & Selecting the 'Best Fit' How to approach different solution options Brainstorming Weighted Evaluation Selecting the appropriate option Hold an Retrospective on your approach Planning the proposal Case Study Exercise Putting RCA into Practice Create a Root Cause Analysis program within your organization How to develop appropriate recommendations to address root causes at various levels to avoid future incidents Additional course details: Nexus Humans BA10 - Understanding Root Cause Analysis training program is a workshop that presents an invigorating mix of sessions, lessons, and masterclasses meticulously crafted to propel your learning expedition forward. This immersive bootcamp-style experience boasts interactive lectures, hands-on labs, and collaborative hackathons, all strategically designed to fortify fundamental concepts. Guided by seasoned coaches, each session offers priceless insights and practical skills crucial for honing your expertise. Whether you're stepping into the realm of professional skills or a seasoned professional, this comprehensive course ensures you're equipped with the knowledge and prowess necessary for success. While we feel this is the best course for the BA10 - Understanding Root Cause Analysis course and one of our Top 10 we encourage you to read the course outline to make sure it is the right content for you. Additionally, private sessions, closed classes or dedicated events are available both live online and at our training centres in Dublin and London, as well as at your offices anywhere in the UK, Ireland or across EMEA.

Duration 2 Days 12 CPD hours This course is intended for Designed for individuals new to the business analyst role or those who supervise and/or work with business analysts. Overview Understand the role of the business analyst Discuss industry standards/resources for obtaining more information about business analysis Acquire a solid understanding of the various tasks/activities that comprises business analysis Recognize the pre and post project business analysis activities Learn how to plan, elicit, analyze, model, and test requirements This is an introductory course designed to provide students with a basic understanding of the benefits, functions and impact a business analyst has within an organization. The course discusses the business analysis process as it is applied throughout a project as well as the pre-project activities that comprise strategy analysis. Students learn how a business analyst supports the project throughout the solution development life cycle, from defining business needs and solution scope to validating that requirements have been met in the testing phase and ensuring the solution continues to provide value after implementation. Introduction to Business Analysis Business analysis defined The activities that comprise business analysis IIBA/PMI and the goals of a professional association IIBA?s BABOK© Guide and PMI?s Practice Guide in Business Analysis Exercise: Requirements challenges The IIBA? and the role of the Business Analyst Business analyst defined BA role vs. PM role Importance of communication/collaboration The deliverables produced as part of business analysis The BA career path Exercise: Review case Study Strategy Analysis and Change The definition of Strategy Analysis Components of Strategy Analysis Identifying stakeholders and business needs Exercises: Business Need development and RACI Stakeholder Identification Understanding and Defining Solution Scope Defining Solution Scope Project scope vs. product scope Defining a problem statement Techniques for defining scope Exercises: Conduct a brainwriting session and create a context diagram Optional exercise: Create a Use Case Diagram Understanding Requirements Define the term requirement Understand requirement types Present the requirements process Requirements vs. specifications and business rules Exercise: Identify Requirements Planning & Eliciting Requirements The Requirements Work Plan (RWP) Components of the RWP Identifying good questions for elicitation Active listening Categories and types of elicitation techniques Exercise: Planning for elicitation Analzying & Documenting Requirements Understanding requirements analysis The Business Requirements Document (BRD) The BRD vs. the functional requirements specification BRD components The purpose of packaging requirements Exercise: Analyzing Requirements Elicitation & Process Modeling Why models are created Objectives of modeling What is process management Understanding process modeling Modeling using BPMN AS-IS vs. TO-BE modeling BPMN subclasses BPMN simple structure Prototyping Business Process Modeling case study Exercises: Modeling and create a Prototype of your application Verifying & Validating Requirements The difference between validation and verification Characteristics of good requirements Risks associated with requirements Types of testing approaches Creating a test plan Requirements traceability matrix Verified and validated requirements Exercise: Testing Requirements Additional Resources Helpful links for obtaining additional business analysis information Additional course details: Nexus Humans BA01 - Business Analysis Essentials training program is a workshop that presents an invigorating mix of sessions, lessons, and masterclasses meticulously crafted to propel your learning expedition forward. This immersive bootcamp-style experience boasts interactive lectures, hands-on labs, and collaborative hackathons, all strategically designed to fortify fundamental concepts. Guided by seasoned coaches, each session offers priceless insights and practical skills crucial for honing your expertise. Whether you're stepping into the realm of professional skills or a seasoned professional, this comprehensive course ensures you're equipped with the knowledge and prowess necessary for success. While we feel this is the best course for the BA01 - Business Analysis Essentials course and one of our Top 10 we encourage you to read the course outline to make sure it is the right content for you. Additionally, private sessions, closed classes or dedicated events are available both live online and at our training centres in Dublin and London, as well as at your offices anywhere in the UK, Ireland or across EMEA.

Duration 3 Days 18 CPD hours This course is intended for This course is intended for intermediate to advanced Business Analysts who are looking to improve their skills for eliciting, analyzing, documenting, validating, and communicating requirements. Overview Obtain a thorough understanding of the core responsibilities of the business analyst Understand the main professional associations and standards supporting business analysts in the industry Discuss and explore the components of each of the domains/knowledge areas that comprise the work of business analysis Recognize the importance of properly defining the business need prior to engaging in requirements activities Formulate a strong understanding of the concepts that comprise strategy analysis Obtain experience with identifying and analyzing stakeholders Decipher between project and product scope and successfully use models to communicate scope Thoroughly understand and identify the various requirements categories and be able to recognize requirements of various types Explore business rules analysis Understand the benefits of process modeling and the common modeling language of BPMN Discuss process models and how the techniques can capture details about the as-is/to-be environment Learn how to properly prepare and conduct interviews Explore the components of use cases Learn what it means to package requirements Obtain hands-on experience with a number of business analysis techniques and gain hands-on experience eliciting, defining, and writing requirements. This course provides students a clear understanding of all the facets of the business analysis role, including a thorough walkthrough of the various domain/knowledge areas that comprise the business analysis profession. Students are provided an opportunity to try their hand at several business analysis techniques to assist with improving their skills in stakeholder identification, scope definition, and analyzing, documenting, and modeling requirements. Introduction to Business Analysis What is business analysis Benefits and challenges of business analysis Project success factors A Closer Look at the Business Analyst Role Definition of a business analyst Responsibilities of a business analyst Importance of communication/collaboration BA role vs. PM role Project roles involved in requirements IIBA/PMI and the goals of a professional association Purpose for having a BA standard IIBA?s BABOK© Guide and PMI?s Practice Guide in Business Analysis Business analysis beyond project work Business analysis core concepts Business analysis perspectives IIBA and PMI certifications for business analysts Workshop: Choose Your Project Supporting the Project Portfolio (Enterprise Analysis) Define Strategy Analysis When to perform Strategy Analysis Components of Strategy Analysis Defining the business need Envisioning the Product and Project Defining business requirements The importance of stakeholders Stakeholder identification Tips for analyzing stakeholders Techniques for managing stakeholder lists Discussion: Who is involved in strategy analysis? Workshops: Define the Business Need, Write Business Requirements, and Identify Stakeholders Understanding and Defining Solution Scope Defining solution scope Techniques for defining solution scope Applying the brainstorming technique Project scope vs. Product scope Finding solution boundaries The Context Diagram Actors and key information Workshop: Draw a Context Diagram Understanding Requirements What is a requirement? Requirement types Business, Stakeholder, Solution, and Transition requirements Assumptions and constraints Business rules Taxonomy of business rules Decision tables How to write simple calculations Requirements vs. business rules Document requirements Workshop ? Document Requirements Elicitation and Process Modeling Why do we model processes? What is Business Process Management? Using a modeling notation ?As Is? vs. ?To Be? modeling Why use BPMN? Basic BPM notation Business Process Modeling ? A case study Business Process Realignment ?As Is? vs. ?To Be? activity diagrams Workshop: Create a Business Process Model Planning & Eliciting Requirements Interviewing ? what and why? Preparing for an effective interview Types of questions to ask Sequencing questions Active listening techniques Planning for elicitation Conducting the interview Establishing rapport Active Listening Feedback techniques Types of elicitation techniques Workshops: Planning for Elicitation and Conducting an Elicitation Session Use Case & User Story Analysis What is an Actor? Types of Actors How to ?find? Use Cases? Diagramming Use Cases Tips on naming Use Cases Explaining scenarios The use case template Components of a use case Scenario examples Best practices for writing Use Cases Scenarios and flows Alternate and exception flows Exercises: Drawing a Use Case Diagram, Writing the Main Success Scenario, and Writing Alternate and Exception Scenarios Analyzing & Documenting Requirements Requirements and Use Cases Non-Functional requirements User Interface Requirements UI Data Table Reporting requirements Data requirements Data accessibility requirements Characteristics of good requirements The business requirements document (BRD) BRD vs. Functional Requirements Specification Preparing the requirements package Requirements traceability Workshops: Develop a User Interface, Analyzing Requirements, and Tracing requirements Additional Resources Useful books and links on writing effective requirements

Duration 2 Days 12 CPD hours This course is intended for Executives, Project Managers, Business Analysts, Business and IT stakeholders working with analysts, Quality and process engineers, technicians, managers; supervisors, team leaders, and process operators; anyone who wants to improve their Business Analysis skills. Overview After completing this course, students will know how to: Plan, manage and close requirements for software development project in reduced time using Agile Scrum practices Minimize project uncertainty and risk by applying Agile principles through the Scrum method Ensure your project delivers required functionality and adds value to the business Create an environment of self-management for your software development team that will be able to continuously align the delivered software with desired business needs, easily adapting to changing requirements throughout the process. Learn how to apply Agile Scrum by measuring and evaluating status based on the undeniable truth of working, testing software, creating a more accurate visibility into the actual progress of projects. Many of today?s Project Management and Business Analyst Professionals are finding themselves leading, managing and analyzing on Agile development teams - only to find that many of the tools and techniques applied when using a traditional project management approach no longer work as effectively or at all. In order to do more than survive in this iterative development environment, today?s Project Manager and Business Analyst must employ additional project management and business analysis tools and techniques to effectively lead their teams and deliver their projects. Introduction - Fundamentals of Agile Why Agile? Exercise 1a: Waterfall-Lean-Agile Simulation History & Mindset: Understand how the agile approach arose. The Agile Lifecycle Introducing Agile to the organization Roles and Responsibilities on an Agile project team. Understand the purpose, the concepts, the theory, and some applications around the importance of people as individuals providing value through working in teams. Establishing core hours - How will the team work during a day? How to build end-to-end systems in early iterations Exercise 1b: How to build end-to-end systems in early iterations Planning and Managing Business Analysis Communication and Performance Agile and CMMI Exercise 1c: Case Study Project Assembling the team ? Scrum Roles Value-Driven Development: Understand why agile development focuses so heavily on working products, its more general casting as 'value-driven' development, with incremental, iterative and risk-driven approaches. Themes, theory and applications. Exercise 2a: Identify the ?Product Owner? Identify Project Success Criteria Exercise 2b: Review the Scrum Cheat Sheet Establish your Agile team using RACI Exercise 2c: Build the Scrum Team Define the Product and Project Vision Envision the Product and Project outcomes Exercise 3a: Review Agile Checklist Project Chartering (Project Planning) Assemble the Agile project team ? what are their responsibilities? Compile the Product Backlog (Coarse-Grain Requirements) Discuss how to Plan Sprints and Releases Exercise 3b: Product Vision ? Goals and Strategies Establish the Project ?time-box? Exercise 3c: Create a Release Plan Embrace the High-Level (Coarse-Grain) Plan Managing different types of Personas on an Agile Project Identifying and managing ?Information Radiators? Planning in Agile Projects ? Common practices that work Determine how the team will tracking and monitoring activities Exercise 3c: Establish the Project Time-box Tools and Techniques ? Building the Scrum Task board Communications Exercise 4a: Discussion ? Tools and Techniques for Scrum Planning, Monitoring and Adapting Scrum Task Board Exercise 4c: Create a Scrum Task board ? Identify work streams Agile Estimating Agile Analysis and Design Burndown Chart Team Velocity Soft Skills Negotiation Estimating ad Prioritizing Effort Planning Releases. Understand the value, the concepts, the theory and some applications for learning and adapting at all levels and on all topics (the product, the process, the team, and the organization). Exercise 5a: Brainstorm Business Functionality Establishing decision and acceptance criteria for user stories Planning Poker Exercise 5b: Estimate Effort (Coarse-Grain) Prioritize themes and releases Prioritize user stories Exercise 5c: Confirm the Estimated Effort (Fine Grain) Estimating team velocity Preparing for change ? Is the organization ready? Exercise 5d: Hold a daily Scrum and update the Scrum Task Board Exercise 5e: Conduct a Scrum or Scrums Plan the Iteration (Sprint) Sprint Zero activities Elements of a successful Sprint Planning meeting Create a Sprint Backlog How to create a task board Exercise 6a: Using the case study ? Review Iteration Planning Checklist Create a Sprint plan ? Establishing Sprint success metrics Exercise 6b: Discussion Sprint ?Zero? Activities Define the vision and Iteration Requirements Estimating the level of effort (LOE) with the team Creating user Stories for the Product Backlog -Guidelines to consider The art of slicing user stories Exercise 6c: Review the Sprint Plan Managing the Solution Scope and Requirements using 2-4 week Sprints Exercise 6d: Adapting a change-driven Project plan that works Adapting a change-driven (Agile) Project plan that works ? what are the key differences from traditional (waterfall) project plans? Finalize the Iteration Plan and how the team will operate Running the Sprint - from Planning to Review and Retrospective Managing your Scrums and setting expectations with your team Exercise 7a: Using the case study ? Review the Review Planning checklist Using Burndown charts to track progress Exercise 7b: Using the case study ? Review the Review Retrospective checklist Manage changes during the Sprint ? What questions to ask Prepare for the Sprint Review Exercise 7c: Review of roles - Quiz Obtain Customer Acceptance of the Product Increment Hold a Sprint Retrospective - What is working and what needs to be improved upon during the Sprints Update the product backlog - Rework the High-Level (Coarse-Grain) Plan Plan and Execute the next Sprint Create an environment for continuous improvement ? Product, Process and People Additional Information Useful books and links on Agile

Duration 3 Days 18 CPD hours This course is intended for This course is intended for beginner to intermediate business and requirements analysts who are looking to improve their elicitation and requirements writing and documentation skills. This course is also a great fit for technical writers, product and software testers, project managers, product owners who work closely with business analysts or who perform some for of business analysis themselves. Overview Understand the role of the business analyst and core competencies for performing successfully Discuss the criticality of business analysis and requirements for successful project outcomes Understand the main professional associations and standards supporting business analysts in the industry Discuss the common problems with requirements and explore approaches to address these issues Obtain a clear understanding of the various requirements types and the significance for eliciting each type Demonstrate your ability to identify stakeholders Explore various methods for understanding and analyzing stakeholders Discuss and apply good planning practices to requirements elicitation efforts Obtain knowledge and understanding of over 15 current and commonly applied elicitation techniques Understand how to progress from elicitation to analysis to documentation Write well-formed and validated requirements Gain understanding of the best practices for writing quality requirements Learn the technical writing techniques that apply directly to writing requirements documents Discuss writing pitfalls, risks that impact requirements, and how to address them Learn best practices for communicating and collaborating with stakeholders, sharing the results of elicitation and the resulting documentation Learn approaches for validating requirements Understand the difference between validating requirements and validating the solution With elicitation serving as a major component of the requirements process, it is imperative that business analysts maintain high competency levels in elicitation practices and technique use to help organizations overcome the requirements related challenges faced on projects. Regardless whether you are a practitioner just starting off your career in business analysis or whether you have been performing the role for some years, this course will provide insight into the latest thoughts on elicitation and writing effective requirements and present a number of current techniques that are being applied on projects across industries today. Review of Foundational Concepts Definition of a business analysis Definition of business analyst BA role vs. PM role Business analysis competencies Benefits of business analysis Purpose for having a BA standard IIBA?s BABOK© Guide and PMI?s Practice Guide in Business Analysis Business analysis core concepts Discussion: Project challenges Understanding Requirements Common problems with requirements Understand the problem first Define the business need Situation statements and moving to requirements Understanding requirement types Business requirements Stakeholder/User Requirements Solution Requirements Functional Requirements Non-Functional Requirements Assumptions and Constraints Discussions: Requirement problems, business needs, and identifying non-functional requirements Discovering Stakeholders Definition of a stakeholder Stakeholder types Identifying stakeholders Performing stakeholder analysis Stakeholders and requirements Tips for identifying stakeholders Grouping stakeholders Creating a RACI model Tips for analyzing stakeholders Documenting results of stakeholder analysis Workshop: Discovering stakeholders Preparing for Requirements Elicitation Planning for elicitation Benefits of elicitation planning What do you plan? The elicitation plan Setting objectives for elicitation Determining the scope for elicitation Establishing pre-work Determining the outputs for the session The iterative nature of elicitation Elicitation roles Elicitation planning techniques Discussions: Who to involve in elicitation, planning impacts, and unplanned elicitation Workshop: Planning for elicitation Conduct Requirements Elicitation Elicitation skillset Types of elicitation techniques Using active listening in elicitation Techniques for performing elicitation Benchmarking/Market Analysis Brainstorming Business Rules Analysis Collaborative Games Concept Modeling Data Mining Data Modeling Document Analysis Focus Groups Interface Analysis Interviews Observation Process Modeling Prototyping Survey or Questionnaire Workshops Write Effective Requirements Elicitation and Analysis Requirements related issues Implications of bad requirements Elicitation and documentation Writing skillset Documenting requirements Modeling requirements Defining the project life cycle Impact of project life cycle on documentation Requirements specifications Characteristics of good requirements Guidelines for writing textual requirements Structuring a requirement Writing pitfalls Traceability Requirements attributes Risks associated to requirements Discussions: Project Life Cycle and Correcting Poorly Written Requirements Workshops: Documenting Requirements and Identify Characteristics of Good Requirements Confirm and Communicate Elicitation Requirements Business analysis communication Requirements communication Communication skills The 7 Cs Timing of communication Planning communication Importance of Collaboration Planning collaboration Documenting communication/collaboration needs Confirming elicitation results Verify requirements Characteristics of good requirements (revisited) Requirements checklist Requirements validation Signing off on requirements Discussions: Responsibility for Communication, Eliciting Communication Needs, Validation Signoff Workshops: Communicating Requirements and Obtaining Signoff Evaluate the Solution Business analyst role in solution evaluation Why solutions under perform What we are looking for in solution evaluation When does solution evaluation occur Performing solution evaluation Planning solution evaluation Metrics that might exist Evaluating long term performance Qualitative vs. quantitative measures Tools & techniques used in solution evaluation Comparing expected to actuals When solution evaluation discovers a variance Tools/techniques for analyzing variances Proposing a recommendation Communicating results of solution evaluation Discussion: Addressing Variance Wrap up and Next Steps Useful books and links on writing effective requirements BABOK© Guide Business Analysis for Practitioners: A Practice Guide Additional course details: Nexus Humans BA04 - Eliciting and Writing Effective Requirements training program is a workshop that presents an invigorating mix of sessions, lessons, and masterclasses meticulously crafted to propel your learning expedition forward. This immersive bootcamp-style experience boasts interactive lectures, hands-on labs, and collaborative hackathons, all strategically designed to fortify fundamental concepts. Guided by seasoned coaches, each session offers priceless insights and practical skills crucial for honing your expertise. Whether you're stepping into the realm of professional skills or a seasoned professional, this comprehensive course ensures you're equipped with the knowledge and prowess necessary for success. While we feel this is the best course for the BA04 - Eliciting and Writing Effective Requirements course and one of our Top 10 we encourage you to read the course outline to make sure it is the right content for you. Additionally, private sessions, closed classes or dedicated events are available both live online and at our training centres in Dublin and London, as well as at your offices anywhere in the UK, Ireland or across EMEA.

This intensive one-day training programme has been developed to help those involved in producing specifications create high quality documents in an organised and effective way. The programme explains the primary purpose of specifications and the importance of understanding the context in which they are used. It focuses particularly on how to develop and structure content and write requirements that are clear and concise. The methods and techniques presented will provide a practical foundation course for those new to the topic whilst offering new insights to those with more experience. The objectives of the workshop are to: Review and discuss the role and purpose of specifications Present a structured approach for organising and producing specifications Explain each of the key steps involved in creating effective specifications Review some methods for assisting in defining requirements Explain how to define the scope and develop the structure for a specification Present methods to assist the writing and editing of specifications Review how specifications should be issued and controlled 1 Introduction Course objectives Review of participants' needs and objectives 2 Specifications in perspective The role and purpose of specifications The impact of specifications on commercial performance The qualities of an effective specification The five key steps of 'POWER' writing: prepare-organise-write-edit-release 3 Step 1: Preparing to write Defining the purpose the specification; integrating the specification and contract Deciding how to specify: when to specify in functional and technical terms Getting the right people involved at the right time; engaging stakeholders Applying procedures for writing, issuing and controlling specifications 4 Step 2: Organising the specification content Scoping the document: scope maps, check lists, structured brainstorming Clarifying requirements; separating needs and desires Dealing with requirements that are difficult to quantify Useful techniques: cost benefit analysis, Pareto analysis Deciding what goes where; typical contents and layout for a specification Creating and using model forms: typical sections and sub sections 5 Step 3: Writing the specification Identifying and understanding the readers needs Choosing and using the right words; dealing with jargon Important words; will, shall, must; building a glossary Using sentence structure and punctuation to best effect Understanding the impact of style, format and appearance Avoiding common causes of ambiguity; being concise and ensuring clarity 6 Step 4: Editing the specification Why editing is difficult; how to develop a personal editing strategy Key areas to review: structure, content, accuracy, clarity, style and grammar Editing tools and techniques 7 Step 5: Releasing and controlling the specification Key requirements for document issue and control Final formatting and publication issues; document approval Requirements management: managing revisions and changes 8 Course review and action planning What actions should be implemented to improve specifications? Conclusion

Many organisations find that project teams struggle to create and maintain effective plans. Estimates are often overly optimistic and risks go unmanaged until the inevitable happens. Resource managers also find it hard to forecast the likely loading on their departments and requests for support are not provided in a consistent format. This programme has been developed to address these needs in a very practical, hands-on format. Case study work can be based on simulations or on the organisation's current projects for maximum benefit to participants. The aim of this training is to develop and enhance participants' planning and risk management skills in order to maximise the success of project work undertaken by the organisation. The principal training objectives for this programme are to: Provide a structured, integrated approach to planning and risk management Demonstrate practical tools and techniques for each stage of planning Show how to organise and involve relevant people in the planning process Explain how to use the plan for forecasting and pro-active project control Identify ways to improve planning, both individually and corporately The course will emphasise the importance of participative planning techniques that improve the quality of plans whilst reducing overall time and cost of planning. The course will encourage discussion of internal procedures and practices and may be customised to include them if required. DAY ONE 1 Introduction (Course sponsor) Why this programme has been developed Review of participants' needs and objectives 2 Projects and planning Why plan? The benefits of good planning / penalties of poor planning Planning in the project lifecycle; the need for a 'living' plan The interaction between target setting and the planning process Team exercise: planning the project 3 Planning the plan Defining the application and structure of the plan Impact of planning decisions during the project lifecycle Using available time to create an effective plan 4 Defining deliverables Assessing the context; reviewing the goals and stakeholders Developing the scope and defining deliverables; scope mapping Understanding customer priorities; delivering value for money Case study: defining the project deliverables 5 Creating the work breakdown Building the work breakdown structure Detailing the tasks and sub-tasks; structured brainstorming Defining task ownership; the task responsibility matrix 6 Creating and using a logical network Developing the logical network; task boarding Determining the critical path and calculating float Accelerating the plan; concurrent programming and risk Individual and group exercises DAY TWO 7 Developing resource schedules Deriving the Gantt chart from the network Developing the detailed resource schedules Calculating the expenditure profile ('S' curve) 8 Estimating task durations and costs Understanding estimates: effort, availability and duration Estimating tools and techniques Application of estimating techniques during the project lifecycle 9 Case study Developing the project plan Refining the project plan Team presentations and discussion 10 Managing risks and refining the plan Awareness of contractual issues associated with risk Identifying and evaluating risks; deciding ownership Managing risks: determining levels of provision and contingency Controlling risks: maintaining an up-to date risk register 11 Planning for pro-active control The earned value analysis (EVA) concept and its predictive value Deriving the measures needed for cost and delivery performance Practical issues associated with implementing EVA 12 Using and maintaining the plan Tracking progress and updating the plan Publishing and controlling the plan 13 Course review and transfer planning (Course sponsor present) Identify ways of implementing the techniques learnt Sponsor-led review and discussion of proposals Conclusion

High quality specifications are of paramount importance in achieving the right technical performance and value for money. This long-established training programme has been developed to help those involved in producing specifications to create high quality documents in an organised and effective way. It provides a sound foundation for those new to the topic whilst at the same time offering new insights to those with more experience. The programme emphasises the need for a clear definition of requirements combined with the ability to communicate those requirements effectively to third parties. A structured method of preparing specifications is provided, and a range of practical techniques is presented, to enable participants to put the principles into practice. The commercial and contractual role of specifications is also addressed. The objectives of the workshop are to: Provide a clear understanding of the role and purpose of specifications Present a framework for organising and producing specifications Define the key steps involved in creating effective specifications Demonstrate methods for assisting in defining requirements Provide tools and techniques for scoping and structuring specifications Show the role of specifications in managing variations and changes to scope Present methods to assist the writing and editing of specifications Review how specifications should be issued and controlled DAY ONE 1 Introduction Review of course objectives Review of participants' needs and objectives 2 Creating effective specifications The role of specifications in communicating requirements The costs, benefits and qualities of effective specifications Understanding the differences between verbal and written communication The five key steps of 'POWER' writing: prepare-organise-write-edit-release Exercise: qualities of an effective specification 3 Step 1: Preparing to write - defining readership and purpose; the specification and the contract Designing the specifications required; applying BS 7373 Defining the purpose, readership and title of each document Effective procedures for writing, issuing and controlling specifications The roles and responsibilities of the key players Understanding contracts; the contractual role of the specification Integrating and balancing the technical and commercial requirements Writing specifications to achieve the appropriate contract risk strategy Deciding how to specify: when to use functional and technical specifications The role of specifications in managing variations and changes to scope 4 Case study 1 Teams review a typical project scenario and identify the implications for the specification Feedback and discussion 5 Step 2: Organising the specification content Defining the need and establishing user requirements Deciding what issues the specification should cover Scoping techniques: scope maps, check lists, structured brainstorming Clarifying priorities: separating needs and desires Dealing with requirements that are difficult to quantify Useful techniques: cost benefit analysis, QFD, Pareto analysis 6 Case study 2 Teams apply the scoping techniques to develop the outline contents for a specification Feedback and discussion DAY TWO 7 Step 2: Organising the specification content (cont) Deciding what goes where; typical contents and layout for a specification The three main segments: introductory, key and supporting Creating and using model forms: the sections and sub-sections Detailed contents of each sub-section Tools and techniques for outlining and structuring specifications 8 Case study 3 Teams develop the detailed specification contents using a model form Feedback and discussion 9 Step 3: Writing the specification The challenges of written communication Identifying and understanding the readers needs Choosing and using the right words; dealing with jargon Problem words; will, shall, must, etc; building a glossary Using sentence structure and punctuation to best effect Understanding the impact of style, format and appearance Avoiding common causes of ambiguity Being concise and ensuring clarity Choosing and using graphics to best effect Exercises and examples 10 Step 4: Editing the specification Why editing is difficult; how to develop a personal editing strategy Key areas to review: structure, content, accuracy, clarity, style and grammar Editing tools and techniques 11 Step 5: Releasing and controlling the specification Key requirements for document issue and control Final formatting and publication issues; document approval Requirements management: managing revisions and changes 12 Course review and action planning What actions should be implemented to improve specifications? Conclusion

The aim of this programme is to help attendees create better quality technical documents in an organised and efficient manner. It will give those new to the topic an appreciation of how to approach the task professionally whilst those with more experience will be able to refresh and refine their skills. The programme comprises three complementary one-day modules: The programme presents a structured methodology for creating technical documents and provides a range of practical techniques that help delegates put principles into practice. Although not essential, it is strongly advised that delegates for modules 2 and 3 have already attended module 1, or another equivalent course. Note: the content of each module as shown here is purely indicative and can be adapted to suit your particular requirements. This course will: Explain the qualities and benefits of well written technical documents Present a structured approach for producing technical documents Review the essential skills of effective technical writing Demonstrate practical methods to help create better documents Provide tools and techniques for specification and report writing Review how technical documents should be issued and controlled Note: the content of each module as shown here is purely indicative and can be adapted to suit your particular requirements. Module 1: Essential skills for technical writers 1 Introduction to the programme Aims and objectives of the module Introductions and interests of participants 2 Creating effective technical documents What is technical writing? how does it differ from other writing? Key qualities of an effective technical document Communication essentials and the challenges faced by technical writers The lessons of experience: how the best writers write The five key steps : prepare - organise - write - edit - release (POWER) 3 Preparing to write Defining the document aims and objectives; choosing the title Understanding technical readers and their needs Getting organised; planning and managing the process Integrating technical and commercial elements The role of intellectual property rights (IPR), eg, copyright 4 Organising the content The vital role of structure in technical documents Deciding what to include and how to organise the information Categorising information: introductory, key and supporting Tools and techniques for scoping and structuring the document Creating and using document templates - pro's and con's 5 Writing the document Avoiding 'blinding them with science': the qualities of clear writing Problem words and words that confuse; building and using a glossary Using sentence structure and punctuation to best effect Understanding the impact of style, format and appearance Avoiding common causes of ambiguity; being concise and ensuring clarity Using diagrams and other graphics; avoiding potential pitfalls 6 Editing and releasing the document Why editing is difficult; developing a personal editing strategy Some useful editing tools and techniques Key requirements for document issue and control Module 2: Creating better specifications 1 Introduction Aims and objectives of the day Introductions and interests of participants The 'POWER' writing process for specifications 2 Creating better specifications The role and characteristics of an effective specification Specifications and contracts; the legal role of specifications Deciding how to specify; understanding functional and design requirements Developing the specification design; applying the principles of BS 7373 Getting organised: the key stages in compiling an effective specification 3 Preparing to write a specification Defining the scope of the specification; deciding what to include and what not Scoping techniques: scope maps, check lists, structured brainstorming The why/what/how pyramid; establishing and understanding requirements Clarifying priorities; separating needs and desires: the MoSCoW method Useful quantitative techniques: cost benefit analysis, QFD, Pareto analysis Dealing with requirements that are difficult to quantify 4 Organising the content The role of structure in specifications Typical contents and layout for a specification What goes where: introductory, key and supporting sections Creating and using model forms: the sections and sub sections Detailed contents of each sub-section Exercise: applying the tools and techniques 5 Writing the specification Identifying and understanding the specification reader Key words: will, shall, must; building and using a glossary Writing performance targets that are clear and unambiguous Choosing and using graphics Exercise: writing a specification 6 Editing and releasing the document Key editing issues for specifications Issue and control of specifications Module 3: Writing better reports 1 Introduction Aims and objectives of the day Introductions and interests of participants The 'POWER' technical writing process for technical reports 2 Creating better reports What is a technical report? types and formats of report The role and characteristics of an effective technical report Understanding technical report readers and their needs The commercial role and impact of technical reports Getting organised: the key stages in compiling a technical report 3 Preparing to write reports Agreeing the terms of reference; defining aims and objectives Being clear about constraints; defining what is not to be included Legal aspects and intellectual property rights (IPR) for reports Preparing the ground; gathering information and reference documents Keeping track of information: note making, cataloguing and cross referencing Tools and techniques for developing a valid and convincing argument 4 Organising the content The role of structure reviewed; some typical report structures Who needs what: identifying the varied needs of the readership What goes where: introductory, key and supporting sections Creating and using model forms: the sections and sub sections Detailed contents of each sub-section Exercise: applying the tools and techniques 5 Writing the report Planning the storyline: the report as a journey in understanding Recognising assumptions about the reader; what they do and don't know Converting complex concepts into understandable statements Presenting technical data and its analysis; the role of graphics Presenting the case simply whilst maintaining technical integrity Exercise: writing a technical report 6 Editing and releasing the report Key editing issues for technical reports Issue and control of technical reports

Masterclasses? Refreshers? Introductions? It depends what you're looking for and where you want to pitch them, but here are six tried-and-tested highly focused sessions that organisations can take individually or as a series, to help develop their teams' project management capabilities one topic at a time. Objectives for each individual session are set out below, as part of the session outlines. Taken together, as a series, however, these modules are an ideal opportunity to develop your team's levels of project management capability maturity, whether that's by introducing them to the basic principles, refreshing them on best practice, or giving them the opportunity to really drill down into a specific area of challenge in your particular operating environment. Session outlines 1 Stakeholder management Session objectives This session will help participants: Understand why stakeholders matter to projects Be able to identify and engage stakeholders Be able to categorise stakeholders by their significance 1 Key principles What does 'stakeholder' mean - in theory? What does this mean in practice? Why stakeholders matter Consequences of missing stakeholders The stakeholder management process:IdentifyAssessPlanEngage 2 Identifying stakeholders Rapid listing CPIG analysis PESTLE analysis Drawing on the knowledge and experience of others Other ways to identify stakeholders 3 Assessing stakeholders Which stakeholders are significant? Stakeholder radar Power-interest maps Power-attitude maps 4 Planning The adoption curve Dealing with obstacles Who should engage which stakeholder? How should the project's organisation be structured? How will communication happen? 5 Engaging Seven principles of stakeholder engagement 2 Requirements and prioritisation Session objectives This session will help participants: Understand how clarity of requirements contributes to project success Use different techniques for prioritising requirements Agree requirements with stakeholders Manage changes to requirements 1 Understanding and managing stakeholder needs and expectations What are 'requirements'? What is 'requirements management'? Sources of requirements - and the role of stakeholders Are stakeholders sufficiently expert to specify their needs? Do they understand the detail of what they want, or do they need help to tease that out? What do stakeholders want to achieve? Working within constraints Prioritising requirements - three techniques 2 MoSCoW prioritisation 'Must have', should have', 'could have, 'won't have this time' When to use MoSCoW 3 The Kano Model Customer satisfaction - 'attractive' and 'must-be' qualities When to use Kano 4 Value-based prioritisation Understanding risk v value Using risk v value to prioritise features and schedules 5 Agreeing requirements Perfect v 'good enough' Establishing acceptance criteria Requirements traceability Agreeing project scope 6 Changing requirements Why requirements change Why change control matters Impact on projects A formal change control process Paying for change - managing change for different types of project 3 Estimating Session objectives This session will help participants: Understand the different purposes estimates satisfy Be able to use different estimating techniques Understand how to achieve different levels of accuracy 1 Key principles What's an estimate? Informed guesswork What needs to be estimated? Costs, resources, effort, duration Tolerances Precision v accuracy 2 Estimating through the lifecycle Start Plan Do 3 Early estimates Comparative ('analogous') estimating Parametric estimating Using multiple estimating techniques 4 Bottom-up estimating Bottom-up ('analytical') estimating Pros Cons 5 Three-point estimating Three-point ('PERT': Programme Evaluation and Review Technique) estimating Uncertainty and the range of estimates Calculating a weighted average Three-point with bottom-up 4 Scheduling Session objectives This session will help participants: Understand how to create a viable schedule Be able to use different forms of schedule Understand the concept of the critical path 1 Key principles The planning horizon Rolling wave planning Release planning 2 Viable scheduling Creating a viable schedule Define the scope Sequence the work Identify the risks and build in mitigations Identify the resources Estimate the effort and durations Check resource availability Refine until a workable schedule is produced 3 Critical path analysis The critical path Network diagrams Sequence logic Practical application:Network diagram with estimated durationsThe 'forward pass'The 'backward pass'Calculating total floatIdentifying the critical pathCalculating free float Gantt charts 5 Risk and issue management Session objectives This session will help participants: Understand the difference between risks and issues Be able to identify and assess risks Understand ways of mitigating risks Manage issues 1 Key principles Understanding risk Threats and opportunities The risk management processPreparation - proactive risk managementThe process - identify, assess, plan, implementStakeholder communication Roles and responsibilities Risk management strategy The risk register Risk appetite 2 Risk identification Brainstorming Interviews Assumption analysis Checklists 3 Risk assessment and prioritisation Probability, impact and proximity Triggers Qualitative risk assessment Qualitative impact assessment Qualitative probability assessment Probability / impact grid Bubble charts Risk tolerance 4 Planning countermeasures To mitigate or not to mitigate? Categories of risk response Avoid and exploit Reduce and enhance Transfer Share Accept Contingency Secondary risks 5 Issue management What is an issue? Tolerances Issues and tolerances The PRINCE2 view of issues Ownership of issues An issue management process Issue register 6 Budgeting and cost control Session objectives This session will help participants: Understand what to include in a budget - and why Choose - and use - the appropriate estimating technique Align the budget with the schedule Understand how to monitor spend and control costs Trouble-shoot effectively to get projects back within budget Session format Flexible. The session can be tailored to the participants' average level of project management maturity - a 60-minute session (delivered virtually) is an effective introduction. A 90-minute session allows for more in-depth treatment. A half-day session (face-to-face or virtual) gives time for a more challenging workshop, particularly to discuss specific cost control issues with any of the participants' current projects. 1 Where is the money coming from? Can we pay from revenue? Do we need to borrow? How long will the project take to pay back? The lifecycle of the budget Through-life costs Stakeholder involvement 2 Estimating costs Reminder: the relationship between estimates Reminder: possible estimating techniques What do we need to estimate?PeopleEquipmentMaterialsFacilities and operating costsWork package estimateEstimated project costs Estimating agile projects 3 Aligning budget and schedule Scheduling and financial periods Spreading the budget 4 Reserves and agreeing the budget Contingency reserve Management reserve Agreeing the budget 5 Cost control Planned spend over time Actual spend over time Work completed over time Evaluating different scenarios: delivery v spend 6 Trouble-shooting Why are we where we are? What has caused the project to spend at the rate it is? Why is it delivering at the rate it is? What are the root causes? What can we do about it?