IndigoBlue provides a wide variety of courses in Agile, Lean and Kanban at introductory, intermediate and advanced levels. We also provide specialist courses specifically designed for digital and web environments.
Introductory Course - Introduction to Agile: Two-Day Course
IndigoBlue’s foundation course introduces the key concepts and techniques required to run an Agile project successfully.
The purpose of the course is to give teams or organisations a solid grounding in the Agile approach and provide a clear understanding of the changes in mindset that are required to run Agile projects successfully and maximise the benefits of the approach.
The course provides techniques that can be applied immediately and a conceptual framework that offers a deeper understanding, enabling you to address more effectively the challenges that arise.
This course is based on general Agile principles and it also includes specific additions in the areas of planning and tracking that are part of the IndigoBlue governance framework.
This is explicitly not a Scrum course.
The majority of the course will be familiar to Scrum practitioners, but certain Scrum practices are not optimal in many situations. The course identifies explicitly where it deviates from Scrum, and provides reasons why you would choose between the different approaches.
Given that Agile covers a broad spectrum of processes, techniques and tools, IndigoBlue’s advanced courses are either role specific, or focus on specific areas where specialism and deep understanding are required.
Intermediate and advanced training is available for:
- Project Managers and Scrum Masters
- Business Analysts
- Product Owners
Additionally, IndigoBlue provides training for those who sit outside of the immediate project team, including customers, stakeholders and steering (executive) roles.
The training courses are typically designed and configured to meet the specific requirements and context of the client organisation and include the following topic areas:
Values and Implications – what does it mean to do things 'better'? As customers, we are deeply aware of the failings of our suppliers and the frustrations we have in dealing with them. There is a sense that there must be a better way. The first step is to get a deeper understanding of what ‘better’ means. What are the values that the customer role can bring to the project, and what implications do these have on the outcomes, both positive and negative?
New Principles – Incremental Delivery and Dynamic Uncertainty Management introduces two new principles for understanding the shape of an IT project, and maps different configurations onto the values and desired outcomes from the ‘Values and Implications’ section. These two new principles explain how and why traditional processes are suboptimal for IT projects, and at the same time demonstrate how benefits can be achieved from the effective implementation of a more Agile approach.
Collaboration, Decision-making and Behaviour – this section looks in more detail at the relationship between customer and supplier. A collaborative relationship is more effective (based on the desired project outcomes) than a negotiation-based relationship, but what does this mean in practice? How does this change the shape of the ‘agreement’ or commitment between the customer and supplier? How does each party fit into an optimised whole? What does each party do to serve the best interests of the other party?
Incremental Analysis – this section is primarily concerned with the challenge of operating as a Business Analyst in an Agile environment. It includes the development of incremental strategies and plans, uncertainty management, engagement with customers and the development team, and appropriate levels of documentation. Also included is training in Objective Impact Mapping.
Governance and Control – a common concern when adopting a more collaborative relationship is that control will be lost. Are there sufficient mechanisms in place to determine when the supplier is not keeping their end of the commitment, or are not acting in the best interests of the project as a whole? Similarly, if Agile projects are incremental in nature, allowed to change more and offer opportunities for validated learning as they go along, then traditional controls do not work so well. This session demonstrates how business stakeholders can assess the status of the project and how to influence it to make it ‘better’.
Agile Testing – good testing is essential to the success of Agile, and this is required at a number of levels: unit, system, regression, integration and user acceptance testing (UAT). All forms of testing in Agile differ from traditional approaches. This section covers the approaches to testing and Agile test strategies. It looks at the requirements for production plus quality and how this can be achieved in an incremental environment.
Where necessary, this area can be supported with additional in-depth coaching in the technical aspects of testing (e.g. TDD, test-driven development).