144 Courses in Nottingham delivered On Demand

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/

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: 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).

Running a Sprint Agile methods are becoming increasingly prevalent, and have facilitated projects in reducing time to market, being adaptive to changing customer requirements, and increasing value provided to customers and organizations. These benefits have been implemented in both IT and non-IT environments to help all types of projects. The Sprint is where it all comes together to deliver the value to the customer in the form of a finished product. This course builds on the knowledge of the 3 Scrum roles, 3 artifacts and 5 events and adds the necessary Agile techniques to get to 'Done'. In addition, you will relate the three Scrum tenets transparency, inspection and adaptation to the overall Sprint process. What you will Learn At the end of this program, you will be able to: Identify the different roles, events & artifacts Understand Basics of a Sprint Transition a managed team to a self-managing team Understand different technical practices Bring visibility into Project Status Understand Do's & Don'ts during a Sprint Sprint Basics Review Self-Organization Technical Practices Transparency Sprint Review and Retrospectives

DASA DevOps Professional: Enable and Scale: In-House Training DevOps embodies both cultural changes and practices through which organizations can facilitate the IT functions of software development (Dev) and software operation (Ops). The DevOps movement advocates automation and phase-based monitoring practices. Its objectives include: Decreasing development cycles · Increasing deployment frequency Improving the reliability of releases Developing a closer alignment with business objectives The DASA DevOps Professional: Enable and Scale course (formerly known as DevOps Practitioner) is designed to provide individuals with the core education necessary to put DevOps into practice. With the help of DevOps theory, pragmatic examples and exercises, and interactive group discussions, the course will help you understand how to apply the necessary skills to practice DevOps. Building on the knowledge learned on theFundamentals course (the 'why'), you will learn the 'how'. The DevOps Professional: Enable and Scale course focuses on improving the skill set of the DASA competency model, which includes competencies like Courage, Teambuilding, DevOps Leadership, and Continuous Improvement. On completion of the DASA DevOps Professional: Enable and Scale training and passing the exam, the certification is awarded. What you will Learn At the end of this program, you will be able to: Explain the importance of DevOps culture and the aspects that can influence it Explain why courage, teambuilding, leadership, and continuous improvement are required in a DevOps environment Explain why courage is essential to enable trust, honesty, and experimentation Identify and evaluate different types of behavior in a DevOps environment Recognize the signals indicating impediments and/or team dysfunctions Describe how to form good DevOps teams and assess their maturity List the effects of happiness and motivation on team performance Identify how leaders encourage feedback and transparency Discuss the factors that leaders can influence to build trust Explain how and why leaders promote a 'safe to fail' environment Analyze value streams to improve throughput and flow Facilitate the tools for continuous improvement: structured problem-solving workshops, Story Mapping sessions, and retrospectives TEAMBUILDING Teambuilding is about understanding the other's point of view, collaboration, mutual accountability, common purpose, and the ability to integrally support the service/product. Design Teams Characteristics of a DevOps team Skills of a DevOps Team Self-organization and autonomy Rules to consider when designing DevOps teams Build Teams Effects of happiness and motivation on performance Feedback Creating high-performance teams Governance Governance within teams and between multiple teams Governance between organizations DevOps contracts DEVOPS LEADERSHIP This module describes how to facilitate teams to high performance, DevOps behavior, transparency, and a service lifecycle mindset. Build Culture Creating the right environment and providing vision and purpose Stimulating the right behavior Servant leadership: giving control, supporting, and inspiring Create Purpose Defining and aligning purpose Purpose of having a purpose Alignment versus autonomy Be a Servant Leader Give control to the team Inspire and support the team Focus on Success Output versus outcome Measuring and steering COURAGE The Courage module is about coaching courageous behavior, proactivity, reflection, trust, open discussions, experimentation, fail fast, and the courage to change. Build Courage The importance of courage Courage in relationship with leadership and feedback Enabling courage at the team level Dealing with failure Think Different Courage day to day Encourage critical thinking Techniques to promote courageous behavior VALUE CUSTOMER-CENTRIC ACTION This module describes the important aspects that are relevant to identify and deliver the required and expected value for all relevant stakeholders. Aspects of Value and Managing Expectations The different aspects of value Stakeholder management Customer collaboration and using customer feedback How to do prioritization CONTINUOUS IMPROVEMENT Continuous improvement describes the importance of a Kaizen mindset, quality at the source, first time right, knowledge-sharing, and the ability to adapt. Build Flow Understanding the importance of flow Using Lean to optimize flow Kaizen as a mindset Radical change versus Kaizen Using Pull to optimize flow Continuous Improvement Tools Kaizen Event Value Stream Mapping Visual Management Retrospective Daily Standup Five Times Why

DASA DevOps Professional: Enable and Scale: Virtual In-House Training DevOps embodies both cultural changes and practices through which organizations can facilitate the IT functions of software development (Dev) and software operation (Ops). The DevOps movement advocates automation and phase-based monitoring practices. Its objectives include: Decreasing development cycles · Increasing deployment frequency Improving the reliability of releases Developing a closer alignment with business objectives The DASA DevOps Professional: Enable and Scale course (formerly known as DevOps Practitioner) is designed to provide individuals with the core education necessary to put DevOps into practice. With the help of DevOps theory, pragmatic examples and exercises, and interactive group discussions, the course will help you understand how to apply the necessary skills to practice DevOps. Building on the knowledge learned on theFundamentals course (the 'why'), you will learn the 'how'. The DevOps Professional: Enable and Scale course focuses on improving the skill set of the DASA competency model, which includes competencies like Courage, Teambuilding, DevOps Leadership, and Continuous Improvement. On completion of the DASA DevOps Professional: Enable and Scale training and passing the exam, the certification is awarded. What you will Learn At the end of this program, you will be able to: Explain the importance of DevOps culture and the aspects that can influence it Explain why courage, teambuilding, leadership, and continuous improvement are required in a DevOps environment Explain why courage is essential to enable trust, honesty, and experimentation Identify and evaluate different types of behavior in a DevOps environment Recognize the signals indicating impediments and/or team dysfunctions Describe how to form good DevOps teams and assess their maturity List the effects of happiness and motivation on team performance Identify how leaders encourage feedback and transparency Discuss the factors that leaders can influence to build trust Explain how and why leaders promote a 'safe to fail' environment Analyze value streams to improve throughput and flow Facilitate the tools for continuous improvement: structured problem-solving workshops, Story Mapping sessions, and retrospectives TEAMBUILDING Teambuilding is about understanding the other's point of view, collaboration, mutual accountability, common purpose, and the ability to integrally support the service/product. Design Teams Characteristics of a DevOps team Skills of a DevOps Team Self-organization and autonomy Rules to consider when designing DevOps teams Build Teams Effects of happiness and motivation on performance Feedback Creating high-performance teams Governance Governance within teams and between multiple teams Governance between organizations DevOps contracts DEVOPS LEADERSHIP This module describes how to facilitate teams to high performance, DevOps behavior, transparency, and a service lifecycle mindset. Build Culture Creating the right environment and providing vision and purpose Stimulating the right behavior Servant leadership: giving control, supporting, and inspiring Create Purpose Defining and aligning purpose Purpose of having a purpose Alignment versus autonomy Be a Servant Leader Give control to the team Inspire and support the team Focus on Success Output versus outcome Measuring and steering COURAGE The Courage module is about coaching courageous behavior, proactivity, reflection, trust, open discussions, experimentation, fail fast, and the courage to change. Build Courage The importance of courage Courage in relationship with leadership and feedback Enabling courage at the team level Dealing with failure Think Different Courage day to day Encourage critical thinking Techniques to promote courageous behavior VALUE CUSTOMER-CENTRIC ACTION This module describes the important aspects that are relevant to identify and deliver the required and expected value for all relevant stakeholders. Aspects of Value and Managing Expectations The different aspects of value Stakeholder management Customer collaboration and using customer feedback How to do prioritization CONTINUOUS IMPROVEMENT Continuous improvement describes the importance of a Kaizen mindset, quality at the source, first time right, knowledge-sharing, and the ability to adapt. Build Flow Understanding the importance of flow Using Lean to optimize flow Kaizen as a mindset Radical change versus Kaizen Using Pull to optimize flow Continuous Improvement Tools Kaizen Event Value Stream Mapping Visual Management Retrospective Daily Standup Five Times Why