123 Software Development courses in Warlingham

Software comes in a variety of guises - application software, firmware, middleware, system software. Increasingly, however, it doesn't necessarily present that way, especially as the boundaries between software, data and source code are becoming more and more blurred. And as software becomes more complex and more difficult to disentangle, so it becomes harder to manage and to value. But as it becomes more integral to every aspect of a business, so it is ever more important to keep on top of the technical, legal and commercial issues that arise, issues such as: To address these issues, organisations need a process for evaluating their current situation from all perspectives and for identifying the key actions they need to take to ensure holistic management of their software. This very practical programme will help set your organisation on the right path. Note: this is an indicative agenda, to be used as a starting point for a conversation between client and consultant, depending on the organisation's specific situation and requirements. This programme is designed to give you a deeper understanding of: The technical, legal and commercial risks associated with software development, procurement, use and commercial exploitation The most appropriate processes and responsibilities for managing those risks Note: this is an indicative agenda, to be used as a starting point for a conversation between client and consultant, depending on the organisation's specific situation and requirements. 1 Software business model What is the software business model? What options exist? Has the software business model been thoroughly reviewed to ensure its viability? This means fully understanding the market opportunity, the business environment and customer and end-user expectations. 2 Technology What are the technologies? How has the technology selection been validated considering the competitiveness, structure, and potential for future innovation? 3 UI and UX What is the UI and UX? How to best articulate this? Has the user interface and user experience been studied from both a subjective and objective view to give insight into customer behaviour? 4 Legal framework / commercial aspects Has the necessary legal framework or commercial aspects that may impact upon use or operation of the software been understood and risks identified and mitigated? 5 Software development What is the software development process? Are both the business management and development team's processes resilient in order to improve the company's capability and the maturity of the software? 6 Software quality What is quality? What are the metrics around software quality? What is the maturity level, based around a qualitative and quantitative assessment? 7 Intellectual property associated What IP should be considered when it comes to software? Does the company understand both the intellectual property risks and potential opportunities associated with this software? 8 Security What does software security mean in this context? How is it being addressed? 9 An holistic approach Review of roles and responsibilities to ensure appropriate management and protection

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 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

Use Cases for Business Analysis The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?

Use Cases for Business Analysis: In-House Training The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?

This course shows you how to apply various approaches and algorithms to solve business problems through AI and ML, follow a methodical workflow to develop sound solutions, use open-source, off-the-shelf tools to develop, test, and deploy those solutions, and ensure that they protect the privacy of users. This course includes hands-on activities for each topic area.

Introduction to Agile for Executives: In-House Training This session provides executives with an overview of Agile values and principles, the key benefits of an Agile approach, and its differences with the traditional Waterfall method. During the session, we compare and contrast the major Agile methods, with an emphasis on Scrum, as the most popular in the market. And most importantly, we present some criteria for Agile Transformation, possible certifications to pursue, and what is needed at the senior leadership level to achieve the best business results. What you will Learn At the end of this program, you will be able to: Explain the basics and benefits of using an Agile approach Describe the Scrum framework, its events, artifacts, and roles and responsibilities Illustrate an Agile approach outside of Software Development Define Scaled Agile Determine how to support an Agile transformation for your organization Getting Started Introduction Course structure Course goals and objectives Agile Introduction What is Agile? Agile benefits Agile myths and realities Overview of Agile Methods Overview of Agile methods Scrum method Lean and Kanban methods Criteria and certifications What Executives Need to Know About Agile Agile is not just for IT Agile can be scaled Agile transformation needs your support Summary and Next Steps Review Personal Action Plan

Introduction to Agile for Executives This session provides executives with an overview of Agile values and principles, the key benefits of an Agile approach, and its differences with the traditional Waterfall method. During the session, we compare and contrast the major Agile methods, with an emphasis on Scrum, as the most popular in the market. And most importantly, we present some criteria for Agile Transformation, possible certifications to pursue, and what is needed at the senior leadership level to achieve the best business results. What you will Learn At the end of this program, you will be able to: Explain the basics and benefits of using an Agile approach Describe the Scrum framework, its events, artifacts, and roles and responsibilities Illustrate an Agile approach outside of Software Development Define Scaled Agile Determine how to support an Agile transformation for your organization Getting Started Introduction Course structure Course goals and objectives Agile Introduction What is Agile? Agile benefits Agile myths and realities Overview of Agile Methods Overview of Agile methods Scrum method Lean and Kanban methods Criteria and certifications What Executives Need to Know About Agile Agile is not just for IT Agile can be scaled Agile transformation needs your support Summary and Next Steps Review Personal Action Plan

In this course, students will learn general strategies for planning, designing, developing, implementing, and maintaining an IoT system through various case studies and by assembling and configuring an IoT device to work in a sensor network.

How to be a Great Executive Sponsor: In-House Training This three-hour course provides key tips and techniques for becoming an actively engaged, and impactful, Executive Sponsor of projects and programs. It will explain not just what your role is, but the very specific actions you can, and must, take to increase your project's probability of success. This three-hour course provides key tips and techniques for becoming an actively engaged, and impactful, Executive Sponsor of projects and programs. It will explain not just what your role is, but the very specific actions you can, and must, take to increase your project's probability of success. And, it will highlight the key personality and other traits that are found in successful Sponsors. Regardless if you're sponsoring an Agile software development project, a construction megaproject, or any other type of project in between, this course will help get you 'hit the ground running' and being an 'impact player' on day one. Various activities and discussions will acquaint you with this important role and what you need to do to become a great executive sponsor. What you Will Learn At the end of this program, you will be able to: Define project success so everyone is 'singing from the same sheet of music' Immediately apply the ten key attributes of a great sponsor on your project Recognize great sponsorship and determine if you're the right fit for the role Practice Sponsorship over the course of the project life cycle by engaging in very specific actions and activities Be a better investment manager by analyzing the behaviors of successful activist investors Foundation Concepts The quantifiable benefits of being an actively engaged Sponsor Sponsor defined Clarence Kelly Johnson and the SR-71 Blackbird: An example of the power of Sponsorship Defining Project Success Project success: More than meeting the triple constraints Benefits management: The Sponsor's focus The Investment - Life-cycle vs. the Project Life-cycle The three questions Sponsors need to ask to define project success 10 Key Attributes of a Great Sponsor 10 Key Attributes of a Great Sponsor The Makings of a Great Sponsor The most important skills and competencies of an executive sponsor What great Sponsors do and when Four Things a Great Sponsor Can Learn from an Activist Investor The story of Outerwall, Inc. and Glen Welling of Engaged Capital, LLC Sponsors and Activist Investors Sponsorship of the 2nd Avenue Subway in Manhattan: A classic textbook example