220 Courses

Duration 5 Days 30 CPD hours This course is intended for The primary audience for this course is any IT, facilities or data centre professional who works in and around the data centre and has the responsibility to achieve and improve efficiency and environmental sustainability, whilst maintaining the availability and manageability of the data centre. Overview After completion of the course the participant will be able to: Understand the impact of data centres on the environment Describe the various environmental/energy management standards Understand the purpose and goals of the legally binding international treaties on climate change Implement various sustainable performance metrics and how to use them in the data centre environment Manage data centre environmental sustainability using international standards Set up the measurement, monitoring and reporting of energy usage Use power efficiency indicators in a variety of data centre designs Use best practices for energy savings in the electrical infrastructure and in the mechanical (cooling) infrastructure Use best practices for energy savings for the ICT equipment and data storage Understand the importance of water management and waste management Understand the different ways to use sustainable energy in the data centre Get practical tips and innovative ideas to make a data centre more sustainable The CDESS© course is aimed at providing knowledge of the standards and guidelines related to environmental sustainability, and how to move your data centre (existing or new) to a more environmentally sustainable design and operations. Impact of Data Centres on the Environment Predictions in 2010 Current situation Outlook and commitments What is Environmental Sustainability The importance of sustainability Senior management commitment Environmental sustainability framework Sustainability policies Performance standards and metrics Information policies Transparency Awareness Service charging models Environmental Management Environmental sustainability framework (ISO 14001) Standards and guidelines ? ISO 50001 / ISO 30134 Measurement and categories Baselining Trend analysis Reporting Power Effiðciency Indicators Various eðfficiency indicators Power Usage Effectiveness (PUE) PUE measurement levels Factors affecting PUE Measurement points and intervals PUE in mixed source environments Measuring PUE in a mixed-use building PUE reporting Impact of PUE after optimising IT load Electrical Energy Savings (Electrical) Identifying the starting point for saving energy Sizing of power DC power Generators UPS systems Power Factor (PF) Energy savings on lighting Electrical Energy Savings (Mechanical) Energy savings on the cooling infrastructure Temperature and humidity setpoints Various energy eðcient cooling technologies Energy savings on the airflow Liquid cooling Energy reusage PUE, ERE/ERF and Control Volume Electrical Energy Savings (ICT) Procurement IT equipment energy eðfficiency ITEEsv, SMPE, SMPO IT equipment utilisation Server virtualisation Open compute project Electrical Energy Savings (Data Storage) Data management Data storage management Data storage equipment effiðciency Water Management Water Usage Effectiveness (WUE) Improving WUE Water usage at the power generation source Energy Water Intensity Factor (EWIF) Waste Management Waste management policies Life-cycle assessment (Cradle to the grave) 3 R?s for waste management Reduce Reuse Second-hand market Recycle Sustainable Energy Usage Sustainable energy sources Power purchase agreements Energy attribute certificates Renewable Energy Factor (REF) Matching renewable energy supply and demand Sustainable energy storage Carbon trading Automated Environmental Management Systems Use of AI and machine learning Load migration Data Centre Infrastructure Management (DCIM) solutions

Opaque Transparency: The Silent Project Killer A 2014 report from the Standish Group showed that a staggering 31.1% of software projects get cancelled before completion. Further, over 50% of projects will cost nearly 200% of their original estimates, and only 16% of software projects are completed on time and on budget. The report cited user collaboration, executive level support and clearly stated requirements as key contributors to success, but what's the common denominator? Having led many public and private classes, and consulted with many corporations, I hear the same pain points over and over. Sharing these pains (which everyone of course believes are unique to them!) will hopefully lead to more project managers pushing for support, executives introspecting a little deeper and more realistically, and team members asking for more project transparency! I've summed up the major project pains from folks mentioned above in to one collective term: transparency. Transparency means clarity, and there are many opportunities from day one of a project to introduce clarity, yet so often these opportunities are missed one after the other. This makes the lack of transparency a silent project killer, slowly choking any chance of success and lending itself to the sad statistics shown above. Thankfully, there is hope! A clear and realistic project charter gets things off to a good start, but it needs to be followed up with other key processes. This presentation talks about those key processes, and more importantly, the fact that brilliant processes are useless without the right people employing them.

a full assessment of your ex’s call 3 ex’s to discuss issues and negative aspects of the ex-partner. 30 mins session with each ex 3x 1 session per week with the client x4 Exes must be willing to take part in this assessment and notified beforehand 4x week programme Trying to establish why relationships keep going wrong and ascertain any problem areas aim to improve relationship skills and self-understanding https://relationshipsmdd.com/product/transparency-package/

On this course, we will use case studies to enhance the delegates understanding of Real Estate financial appraisals, and help them fully appreciate the theory behind the numbers.

All organizations have policies and procedures that guide how decisions are made and how the work is done in that organization. Professionally written policies and procedures increase organizational accountability and transparency and are fundamental to quality/standards assurance and quality improvement.

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

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

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

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

Kanban is a popular framework used to implement Agile and DevOps software development. It requires real-time communication of capacity and full transparency of work. A Kanban board is an Agile project management tool designed to help visualize work, limit work-in-progress, and maximize efficiency (or flow).