Early Bird

Agile Fundamentals (ICP) | 16-17 September 2020 | London

£1,195.00 £1,045.00


Essential skills for all agile leaders and teams. This two-day Agile Fundamentals course, accredited by ICAgile, is for anyone who needs to work in an agile team or lead an agile transformation. You will learn the mindset and skills to succeed with Scrum, Kanban, Agile Project Management (DSDM), Lean Startup, DevOps, or SAFe. Fully accredited by ICAgile, a community-driven organisation of pioneers, experts, and trusted advisors. Participants will be awarded ICAgile Certified Professional on successful completion of the course.

We’ve got you covered.

The only course that combines Scrum, Kanban, Agile Project Management, and Lean Startup.

Delivered by ICAgile-approved instructors in London, UK, participants will work in small groups to experience the new roles, iterative and incremental delivery of products, customer engagement, and planning practices with examples in Scrum, Lean, Kanban, Lean Startup, and Agile Project Management. This course is delivered using a mix of teaching, facilitator-led activities, and participant discussions of real-world problems in agile organisations.

Who Should Attend

Agile Fundamentals is an excellent introductory course for agile leaders and teams. Learn the essential agile mindset, behaviours, and practices which are the foundation of working with any of the agile frameworks. So it’s suitable for people working in product management, HR, IT service delivery, product development, operations, software development and testing, enterprise architecture, and research and development.

This course is delivered in-person in London, United Kingdom.

Course Outline


  • Why use an agile approach? Responding to change and uncertainty
  • ICAgile Learning Tracks
  • Earning your certificate: ICAgile Certified Professional
  • Personal learning objectives

History & Mindset

  • Iterative development – XP, Scrum, DSDM, and Lean Startup
  • Origins of agile methods
  • Agile Manifesto
  • Beyond software development
  • Understanding the agile mindset
  • Benefits of agile development

Individuals & Interactions

  • What is a team? Success factors for agile teams
  • Agile roles – development team, agile leader, product owner
  • The journey to mastery
  • How will your role change?
  • Experience collaboration

Value-Driven Development

  • Incremental development
  • Scrum’s inspect-and-adapt cycles
  • Making progress visible
  • Work in progress and flow
  • Continuous integration
  • Prioritisation

Customer & User Involvement

  • Defining the customer
  • Understanding stakeholders
  • Write personas and user stories
  • User involvement and feedback
  • Craft a product vision statement

Planning & Adapting

  • Sensible planning horizons for uncertain business environments
  • Estimating in agile development
  • Prioritisation to protect on-time delivery
  • Making progress visible – continued
  • Process and project adaptation
  • Release planning

Continuing Your Development

  • Review personal learning objectives and plans for the future

Learning Outcomes

History & Mindset

  • Many people entering the Agile world see the Agile Manifesto as the beginning of the world, where it was really the summing up of much previous work. 
  • The 2001 Manifesto for Agile Software Development is still the anchor document for all forms of Agile development. 
  • Agile is gaining increasing adoption throughout the organization. 
  • Many people come to Agile looking for “the Agile process”. However, while some processes and methodologies may be more supportive or common in Agile organizations than others, the mindset must come first. 
  • Experiencing the Agile mindset is the best way to establish it in a learner 
  • The level of knowledge and experience held by individuals, teams and organizations can affect behaviors, processes and adoption. 

Individuals & Interactions

  • Soft skills such as attitude, community, trust and morale have traditionally been left out of team-based design. Agile brings them to the fore. 
  • Projects can be impacted when organizations underestimate the cost of physical and cultural separation. 
  • When teams ignore tacit vs. documented knowledge, they are not able to make conscious decisions about sharing information. 
  • It is easy to set up work spaces that hinder rather than help the team. 
  • Collaboration needs to be experienced, not just talked about. 
  • The Agile community has adopted several tools and techniques to support shared understanding. 
  • The term “self-organizing” can create concern for individuals and organizations because it infers shifts in traditional power structures. Agile learners and organizations need to define and align old and new role definitions. 

Value-Driven Development

  • One anchor of Agile development is incremental development.
  • Many people, even understanding the idea of incremental development, can’t see how to break work into small, value-centered work items and track their progress.
  • It is easy to lose sight of the cost of rework in incremental-iterative development.
  • Work-in-Progress (WIP), a term from lean manufacturing, seems to many people a strange concept to introduce outside of manufacturing, but WIP shows up in incremental development.
  • Continuous integration is a valuable goal in software development; non-software projects can still use the more general concepts of frequent integration.
  • Delivering is not merely giving a demo; it includes costs as well as benefits.

Customer & User Involvement

  • The literature and common usage can be confusing in defining the customer. 
  • Product/project success correlates with end-user involvement. Many teams face resistance to getting end-users to participate in a project, which then can fail even if the team practiced every other Agile habit besides getting feedback from real users. 
  • Ongoing user feedback is important for maximizing customer value. 
  • An unprepared team can suffer from reacting too vigorously to change requests. 

Planning & Adapting

  • A misconception of Agile development is that it involves no planning and no promises. 
  • Agile teams understand the value of collaborative estimation during planning. 
  • A team and its sponsors need to know how the work is progressing. 
  • A common mistake is to imagine that there is a single process that can fit all projects & situations; even a good process becomes mismatched to the team over time. 
  • Reflection workshops are necessary for both product and process adjustment. Techniques for conducting reflection workshops are best learned experientially.


This course is accredited by ICAgile, a community-driven organisation of pioneers, experts, and trusted advisors.

On successful completion of the course, participants will be awarded ICAgile Certified Professional.

Participants must complete a Lessons Learned Log and submit it to the course instructor, to receive the certificate. Online courses only: participants must score at least 75% correct on quizzes at the end of each day of training, in addition to submitting their Lessons Learned Log, to receive certification.


“Deep knowledge of the theory, the mindset and the practice of Agile and its applications.”

“Absolutely worth the investment.”

”Laura was a great host, brilliant online facilitator and clearly knowledgeable about both coaching and agile. I felt very safe in her hands and learned a huge amount from her.”

“Related it to the different attendees, covering both business and technical aspects.”

“Laura is a very good instructor and she used a lot of learning approaches during the training. Her comfortable style and training skills made the training very enjoyable. I will definitely recommend her to other people interested in learning and understanding the Agile mindset.“

“Excellent throughout.”

“Thank you for an awesome experience of learning Agile Fundamentals.”

“Keep doing it, it was really good.”

“The exercises were super simple, but so effective.”

“Insightful, practical, and has given me tools, tips and ideas on how to approach specific challenges at work.”

“Thank you for passing on some powerful tools for facilitating team bonding and growth.”

“Very positive experience. Laura showed great enthusiasm for the topic which was infectious.”