43 Brain courses in Glasgow

When used effectively, questioning is a useful teaching and learning strategy. During this workshop we will discuss how questioning can be used effectively to assess, challenge and stretch pupils progress.

In today's dynamic business environment, Managers need to evaluate different courses of action and make decisive decisions.

The 2-hour Baby & Child First Aid class covers CPR, Choking, Bumps, Burns, Breaks, Bleeding, Febrile Seizures and Meningitis & Sepsis Awareness and will give everyone who attends the peace of mind they deserve.

Our *NEW* Mini First Aid Baby Proofing class is our second class, designed for parents and carers of babies and children over 3 months. It can be taken after our 2 hour Baby and Child First Aid class, or in isolation for those parents who are starting their weaning journey, or have a baby on the move!

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

Workplace Mediation

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?