Agile Courses, ICAgile

Agile Fundamentals Bootcamp (ICP)

This program is conducted in association with Agilemania.

Course Description:

In order to succeed with agile, teams and organizations should focus first on “being agile” as a foundation for success in “doing agile.” Agile fundamentals ICP training learning objectives delve into key concepts such as adaptive planning, value-driven development, team collaboration, and frequent feedback for continuous improvement. The course also covers the history of agile, the agile manifesto, the agile principles, and some widely applied frameworks and practices.

Students come away with a solid understanding of core concepts as they prepare to embark on their agile journey. Consequently, participants leave the course more confident in five key areas:

➜   The intention behind agile practices
➜   Value-driven development
➜   Adaptive planning
➜   Customer engagement in agile
➜   Putting lean agile into action

Course Objectives:

➜   Origin and History of Agile.
➜   Agile Values and Principles.
➜   Clarity about transitioning to the Agile roles.
➜   What is Empirical Process?
➜   Deeper understanding about various agile frameworks.
➜   Understanding about where to use Scrum, Kanban or both.
➜   Overview about Scrum framework.
➜   Scrum Roles, Artifacts and events.
➜   Definition of Done and Acceptance Criteria.
➜   Exploring Differences between various frameworks.
➜   Tools for Agile Project Management.
➜   Tracking and measuring project success in agile.
➜   Value delivery vs Fixed Schedule Project.
➜   Essential elements for Agile Way of Working.

Who Should Attend?

There are no specific requirements needed to attend this workshop. If you are looking for improvements in the way they work, want to start using Agile at work or levelling up their knowledge, have creative work that requires frequent feedback from the client or user.

Course Topics:

Origins of Agile

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. Anchor the ideas of Agile development in earlier work, giving the learners continuity from the past to the present.

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. Introduce Agile as a mindset and explain that agility is achieved through both “being” and “doing” Agile. The Agile mindset is characterized by things like valuing early failure for learning, collaboration, continuous improvement, continuous discovery, etc.

One anchor of Agile development is incremental development. Introduce the concept and value of incremental development, and how it differs from effort-based or task-based management.

It is easy to lose sight of the cost of rework in incremental-iterative development. Introduce and highlight why Agile developers need to keep an eye.

Who is supposed to be a good product owner? What Product Owner does in Scrum? Do they write stories or maximize value? Why do we need a Scrum Master? Who decides Scrum Master for the team? What’s the meaning of a Self-Organized Development Team? Is a Self-organizing team good enough or we need a self- managed team? Developers are cross-function or Development Team is cross-functional?

Why change is hard and what can be done to make it real? What organizational changes needed to see the real benefits of Scrum?

The story map is populated by the group writing user stories to fulfil each of the product features, ensuring the stories remain aligned with the product vision and value drivers. Will have an understanding about how to split complex features into manageable stories.

Identifying and responding to non-functional requirements to ensure they don’t get lost in the process of defining product success and lead to hidden risks.

Using key metrics and visualizing them with cumulative flow diagrams to help see where work is and how to improve the flow from concept to reality. Helping product owners to focus upon the right metrics and avoid those metrics that drive undesirable behaviors in development teams and by stakeholders.

How to measure the success of an agile project in the ever-evolving requirement? Discussion around key metrics like business values, velocity chart, release burndown and sprint burndown. How to incorporate feedback in the forecast and how to forecast the project completion date.

The 2001 Manifesto for Agile Software Development is still the anchor document for all forms of Agile development. Make clear that the Agile Manifesto is a set of values, not a prescription for a particular type of process. Also, learners should be introduced to the fact that the values on the left are preferable to those on the right.

Experiencing the Agile mindset is the best way to establish it in a learner Allow the learner to experience situations in which the Agile mindset is likely to be different from their current way of working, so the learner can internalize the difference experientially, not just in concept.

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. Develop and practice techniques for breaking problems into value-based parts and tracking progress against them.

How is the Scrum theory implemented through time-boxes events, roles, rules and artefacts? How can these be used most effectively? We will experience why the Scrum framework is constructed as it is and how you as Scrum Master can effectively use Scrum to control risks and create maximum value.

Are you able to deliver a truly done product? What “DONE” means in Scrum and why it is important? Workshop focuses on differentiating DONE and UNDONE but also brings discussion about Technical Debts. Participants have to learn the meaning of DONE increment by defining definition in the workshop. Why not to have technical debt is critical to a growing organization? How Acceptance Criteria is different from Definition of DONE?

From concepts/ideas that may be vague, product owners are taken through the steps to turn this into a tangible and valuable artefact: a product vision statement. In a group exercise, the product vision statement is developed using proven techniques such as Elevator Pitch, Lean Canvas and Product Box. From the product vision statement, a story map is developed, breaking down the vision into a manageable number of steps or functional areas, depending upon what best suits the product. With this initial outline in place, high-level functional requirements are written, introducing the concept of user stories and epics.

The planning exercise is repeated a number of times using different criteria such as risk, value, complexity, size and marketability.

Using key metrics and visualizing them with cumulative flow diagrams to help see where work is and how to improve the flow from concept to reality. Helping product owners to focus upon the right metrics and avoid those metrics that drive undesirable behaviors in development teams and by stakeholders.

Understand the role of the product in relation to the development team, how best to support them and what they need from a product owner to be effective in their role. Working with stakeholders, keeping them informed of progress and risks, influencing their decision making and managing expectations.

Agile way of working has become buzzwords after the ING case study and recent adoption at ANZ. Let’s understand the pros and cons of the agile way of working. Will have a discussion around various models for organization agility and way to adopt. The focus will be on owning a roadmap for organization agility vs renting processes.



What is the duration and timings of this course?

NA ..

No. We do not provide any tools with this course.

Yes this certification is valid for lifetime.

No, we do not provide placement.

The maximum batch size is 20 members in one batch.

Yes post training support will be provided, you can contact the trainers for any queries which you may have.

No, coding is not a prerequisite.

We strongly recommend that the participants attend the batch which they have specifically registered for. There can be exceptions in case of emergencies but the difference in fee(if any) will have to be borne by the participant.

No we do not provide refunds upon cancellation.

Yes we can arrange for an in-house batch for your company given there are a minimum of 10 participants per batch.

Agile Fundamentals ICP


ramit verity trainer

Ramit Manohar

Program highlights:

Book your slot:

Book your slot

Other trending courses

Speak to an Expert

Please call on the below contact numbers directly or fill in your details for a call back from our team.

Mr. Vinay +91 99101 05147 
Mr. Anil +91 98230 64054