2 Educators providing Software Engineering courses in Broughton Astley

SAFe® Agile Software Engineering: In-House Training The introduction of Lean-Agile and DevOps principles and practices into software engineering has sparked new skills and approaches that help organizations deliver higher-quality, software-centric solutions faster and more predictably. This workshop-oriented course explores foundational principles and practices and how continuous flow of value delivery and built-in quality are enabled by XP technical practices, Behavioral-Driven Development (BDD), and Test-Driven Development (TDD). Attendees will learn proven practices to detail, model, design, implement, verify, and validate stories in the SAFe® Continuous Delivery Pipeline, as well as the practices that build quality into code and designs. Attendees will also explore how software engineering fits into the larger solution context and understand their role in collaborating on intentional architecture and DevOps. What you will Learn To perform the role of a SAFe® Agile Software Engineer, you should be able to: Define Agile Software Engineering and the underlying values, principles, and practices Apply the Test-First principle to create alignment between tests and requirements Create shared understanding with Behavior-Driven Development (BDD) Communicate with Agile modeling Design from context for testability Build applications with code and design quality Utilize the test infrastructure for automated testing Collaborate on intentional architecture and emergent design Apply Lean-Agile principles to optimize the flow of value Create an Agile Software Engineering plan Introduction to Agile Software Engineering Connecting Principles and Practices to Built-in Quality Accelerating Flow Applying Intentional Architecture Thinking Test-First Discovering Story Details Creating a Shared Understanding with Behavior-Driven Development (BDD) Communicating with Models Building Systems with Code Quality Building Systems with Design Quality Implementing with Quality

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