25 Software Developer courses in Swanscombe

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.

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

Agility has become a prized business attribute. Although Agile methods were once most associated with software development, they are now applied in a host of different areas. Agile continues to find new applications because it is primarily an attitude. This programme delivers a solid grounding in both the Agile mindset and Agile methods. It covers three methods, illustrates the benefits of each and shows how they can be integrated. It includes practical techniques as well as background knowledge. By the end of the session, participants will be able to: Apply Agile concepts to self-manage their work Understand the roles people take on in Agile teams Use a variety of techniques to help deliver customer satisfaction Focus on delivering against priorities Employ a range of estimating techniques 1 Introduction Overview of the programme Review of participants' needs and objectives 2 The basics of Agile What makes Agile different Agile Manifesto and Principles Using feedback to deliver what is needed 3 Agile teams Multi-disciplinary teams Team size and empowerment Agile values 4 Agile at the team level - Scrum Scrum roles Scrum 'events' Scrum 'artifacts' 5 Agile for teams juggling multiple demands - Kanban Taking control of the work Improving throughput Dealing with bottlenecks 6 Agile in projects - AgilePM The phases of an Agile project Managing change requests Delivering on time 7 Estimating T-shirt / Pebble sizing Yesterday's weather Planning poker 8 Pick 'n' mix - some useful techniques The daily stand-up User stories Retrospectives Work-in-process limits Burndown charts Minimum viable product A / B testing 9 Review and action planning Identify actions to be implemented individually Conclusion

Agile project management, already widely used for software development, is increasingly recognised as having much more general application. Continuous improvement programmes, business change projects, new technology development, research and development and a variety of other scenarios characterised by rapid change and high uncertainty can all benefit from an Agile approach. This programme presents the concepts and methods of Agile project management, and shows how to apply them to a range of project and change management situations. Participants will learn: how Agile project management can help with project and change management the 4 values and 12 principles of the Agile 'manifesto' and the range of Agile methodologies how to apply Agile project management methods and techniques in a range of project scenarios alternative Agile project management methods and how they can be applied and adapted what makes Agile project teams succeed the key roles and responsibilities needed to enable Agile project teams to work effectively how to encourage an Agile mindset within their organisation and how to move toward an Agile approach to managing projects 1 Introduction to Agile project management Overview of 'classical' project management and methodologies The link between project success and management performance Limitations of classical approaches and the need for Agile methods The 4 values and 12 principles of the Agile manifesto explained Agile project management values:Individuals and interactions over processes and toolsWorking outputs over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan The cultural challenges of using Agile project management Choosing when and how to adopt Agile project management 2 Initiating a project using Agile project management Some key Agile methodologies explained: SCRUM, XP, Crystal Identifying and engaging project stakeholders; defining roles and responsibilities Setting the project vision and goals; defining project scope The Agile approach to requirements capture and elicitation of needs Tools and techniques for capturing and characterising requirements The role of documentation, reporting and process management 3 The Agile approach to definition and planning Understanding Agile planning; the 'planning onion' concept Developing the culture needed for collaborative involvement and iterative planning Defining project deliverables; the 'product backlog' concept Tools and techniques for defining and prioritising requirements in Agile projects Understanding and applying Agile estimating techniques Dealing with uncertainty and managing risks 4 The Agile approach to execution and delivery The results orientated, fast adapting culture of Agile teams The monthly 'Sprint' process for project planning and review The disciplines needed for effective daily SCRUM meetings Reviewing progress, managing change and project reporting Testing, completing and handing over of work packages Managing the interface between the project team and the business 5 Leadership and teamwork in Agile project teams Why Agile teams are different: the importance of individuals and interactions The skills and attributes needed to lead an Agile project team The challenges faced and skills needed by Agile team members Recognising team development needs; adopting the right leadership style Making the transition from project manager to Agile coach Key coaching skills explored: mentoring, facilitating, managing conflict

The fundamental tool to identify waste, create effective process flow, reduce process cycle times, and implement process improvement.