Skip to main content
  • Contact us
  • Search

    Lay a strong foundation to make your team truly Agile

    Tailored Agile Fundamentals Training

    Training themed illustration - Agile
    To succeed with Scrum, Kanban, or any other Agile work, you need to get the fundamentals right. And since a chain is only as strong as its weakest link, you need the whole team completely on board.

    The Scrum Master, Product Owner, or any other member of the development team - they all need to understand their roles and responsibilities. And a leader must be able to steer and monitor Agile development, and understand the economics behind it. This training will make you truly Agile, and will be tailored to your specific team. From short, to-the-point sessions, to larger training programs.

    Key reasons to give your team Agile training

    • Better understand the fundamentals of good Agile
    • Work more effectively across the board
    • Reduce waste
    • Make your work more predictable
    • Let your teams and people manage themselves better
    • Give everyone a stronger sense of purpose and direction

    Duration:

    Per agreement, based on the attendees’ needs 

    Type:

    Classroom or remote training

    Audience:

    Development organization, leaders, and stakeholders

    Let your whole team enjoy Agile at its best - they deserve it

    Contact us and we’ll find the perfect training plan for your team or organization.

    Eficode's trainers have been very professional, and they have been able to offer us a tailored training package, which is exactly what we wanted.

    Mikko Saarentaus
    Director at DNA Entertainment Business

    Read case
    DNA case image (1)

    On the path to becoming an Agile organization

    Get the fundamentals right to be Agile

    To truly benefit from Agile, your whole team needs to understand the Agile principles and values, and do small things right, like ceremonies or Definition of Done. 

    Even a mature team needs to revisit the Agile fundamentals from time to time and discuss where there is room for improvement.

    agile spot

    Work more effectively

    Give your development teams a chance to realize their full potential. And be sure they work on the right things, with the right specification. Make them Agile with capital A.

    alarm-clockt-spot

    Cut out waste in development

    Give your teams a chance to steer their work more directly toward the target, solve customer problems faster, and avoid having to “fix” things later, or rework solutions. 

    calculate savings - calculator - hexagon eficode

    Make work predictable

    With a better understanding of the problem to be solved, your teams will make better estimates and forecasts. And with a disciplined approach to story specifications, you will reduce delays and make more accurate development predictions.

    valuable ideas bulb - hexagon gray

    Modules we can build your course around

    What are Agile practices? To adopt them, you need to understand why Agile works - and when it works. It is absolutely critical to embrace Agile values. In this introductory module, your team will learn the foundations behind good Agile practices. The module also quickly introduces the main working models, roles and ceremonies.

    Topics included:

    • Agile values, principles, and history
    • Scrum and Kanban
    • Roles in Agile teams
    • Agile ceremonies introduction
     

    This module takes a deeper look at the Scrum ceremonies. Each ceremony—typically run by a Scrum Master—is a regular, repeating meeting with a goal. 

    Improving the format, components, and preparation of the ceremonies, raises your team’s level of quality and productivity.

    Topics included:

    • Backlog refinement
    • Sprint planning
    • Daily
    • Retrospective
    • Sprint review

    Unlike Scrum, in Kanban you do not use a fixed-duration timebox. Your team members work on individual work item: tickets. While it is easy to start using Kanban, to succeed with it, you need more discipline than with Scrum.

    Topics included:

    • When to use Kanban vs. Scrum 
    • You main challenges in Kanban
    • The 6 basic rules of good Kanban
    • Planning and forecasting with Kanban



     

    When managing Agile requirements, you may deal with both requirements and backlog items. Requirements management varies greatly between teams and environments. Backlog management is the responsibility of the Product Owner.

    Topics included:

    • Backlog management
    • Requirements vs. backlog items
    • Requirements traceability
    • Tool configurations and options

    In Acceptance Test Driven Development, the development organization (both business and technical people) together defines how a system should behave before any actual development is done. By specifying the test cases together beforehand, the team ensures the right feature is built, and that test cases that result in this work are reusable and can be easily automated.

    • Why ATDD?
    • Understanding users
    • A conversation around ATDD”
    • Gherkin syntax and test case formulation

    Agile testing is highly collaborative, with a focus on delivering high-quality software frequently. The goal is to equip software development teams with the skills and knowledge to test and deliver software in an Agile environment effectively.

    Topics included:

    • Quality practices in Agile
    • The team testing approach and the Testing Quadrants
    • Agile testing practices to support amplified feedback 
    • Using the benefits of CI/CD and DevOps

    Many product backlog items are written as user stories. It is essential to craft them well. Epics are larger stories that are later split into smaller stories. 

    In this module you will learn how to write better epics and user stories, and how to split stories into usable sizes.

    Topics included:

    • Good and bad epics
    • Good and bad user stories
    • Splitting stories and epics

    Sometimes Agile goes bad. Your organization thinks it is Agile, but you don’t see the results. Why? How do you know if your Agile has turned dark, and  how do to recover?

    In this module, you will learn the characteristics of Dark Agile, and what you can do to fight it.

    Topics included:

    • How to know when your Agile transformation has gone bad
    • Typical Agile anti-patterns
    • How to fight Dark Agile

    To plan and prioritize correctly, and to avoid starting too large work items, you need to estimate an item’s effort required. 

    In this module your team will learn how to estimate initiatives, epics, stories and tasks, and how to update these different estimates and use them in reporting 

    Topics included:

    • What to estimate: Initiatives, epics, features, stories, and bugs
    • Estimation scales
    • How best to use estimates
    • Dangers of estimation and metrics

    Empower your entire team with new skills

    Contact us to plan this training just for your team or organization