top of page

Implementing Agile Processes for Automation Projects

Updated: Aug 21, 2023

Are you frustrated with continuous requests for enhancements on a project? Maybe your company is pushing for more lean or agile practices. Perhaps you’ve tried running in Agile before but haven’t delivered. There are many great habits that product teams can utilize to help streamline delivery and ensure project success.

One of these habits is introducing agile in the workplace. In its simplest terms, Agile is a methodology that takes an iterative approach to projects. It creates a continuous feedback loop with stakeholders and assures that value is delivered to customers by establishing trust and communication, delivering often, and allowing for flexibility.

Agile Terminology

*Agile terminology comes from Scrum Glossary and SAFe website.

To organizations that do not have a clear understanding of agile principles, the thought of implementing these practices can be daunting. There are several ways to incorporate agile practices into daily operations. Starting small and working toward a full-blown agile solution typically works best for companies hoping to adopt agile practices. Below are just a few examples of modifications that can be made to existing processes to help streamline project delivery.

The Agile Process Explained

The agile process typically starts with requirements gathering. During this phase of the process, product managers and product owners meet with stakeholders to understand their desires. These desires or asks from stakeholders are translated into Features. Once agile leaders gather a list of requirements, they work with the team to prioritize these requirements and plan out phases of work.

After requirements gathering, agile teams will sit down to groom their backlog – the Features they’ve just created from stakeholder meetings. The backlog grooming process typically consists of one or more of the following activities:

  • adding additional detail to describe the purpose of the Feature,

  • creating proper acceptance criteria to help the team understand when the Feature can be moved to a “Done” state, and

  • assigning business value, time criticality, and level of effort to the Feature

After a Feature has been established and groomed, product owners sit down with their team to break Features out even further into user stories. The team uses user stories to track how their day-to-day work contributes toward Feature Completion and prioritizes work for upcoming iterations – usually called sprints. Typically, teams will conduct sprint planning every two weeks or at the end of each sprint cycle.

Prioritizing Work

While there are many ways to prioritize work, an easy and effective way is to use a simple calculation called the “Weighted Shortest Job First” (WSJF). ImagineX has found this method of prioritization to be especially effective when there are many stakeholders.

Fibonacci numbers

The Feature with the highest WSJF score is considered the most critical, while the Feature with the lowest score is regarded as less critical for immediate efforts. Once the team has determined which Features have the highest prioritization, the Product Owners will work with teams to ensure that each User Story has assigned story points (level of effort required to complete a story).

Planning Work

It is important to create a plan for tackling work. This ensures that teams are not over-promising delivery to stakeholders. It is the job of the product manager and product owner to understand and adhere to the capacity constraints of their teams. The easiest way to do this is to utilize a WSJF and simple capacity calculation. That looks a little something like this:


In the above equation, each workday is granted one point for capacity. We are allocating 20% time for meetings, documentation, and other admin work. This leaves us with 80% time for hands-on development work. Baking in time for administrative tasks ensures that the team is allowing for ad hoc meetings they may need with other teams, stakeholders, or their own team scrum meetings. Accounting for time off also ensures that product owners are not over-allocating development efforts when team members are available. This helps to create a happy and efficient working environment, mitigating some of the usual burnout or frustration that employees may face when planning activities have not taken place.

Once Features Have Been Prioritized, Stories Have Been Created, And Capacity Has Been Determined, We Can Start Planning Work For Each Sprint.

It is important to note, however, that when loading work for following sprints, product managers and product owners do NOT load each sprint to 100% capacity. This allows for flexibility in work, as things can change rapidly. Agile principles say it is best to load to 90% for the immediate sprint, 80% for the following, and 70% for the subsequent. With this planning, we have the availability to incorporate feedback from stakeholders as teams iterate through projects.

How Can You Incorporate Agile Principles in Your Project?

Implementing agile requires a lot of work up front, but in the long run, it can be very beneficial to your company when implementing automation projects.

Define Your Scope & Identify Potential Blockers

A successful data project starts with well-defined requirements. By gathering requirements up front, understanding pain points, and documenting all intricacies in the process, teams will be able to anticipate any potential roadblocks and identify areas where additional assistance may be required. This will help the team understand what meetings might be required and design the automation process to where bottlenecks do not become major impediments.

Plan Work using the WSJF scoring and capacity planning formula above. Make sure to adapt the capacity formula to something that makes sense to your team.

Test Frequently, Release Often, And Request Feedback Early

Releases will be iterative – a deployment might not be perfect and the code might still need some cleanup. By gathering feedback quickly and early in the process, teams are able to pivot efforts without losing too much time if stakeholders’ requirements change or major issues are identified during the build process.

By implementing these practices, teams can be more effective in the planning, development, and deployment of projects, allowing for more visibility and collaboration with stakeholders who may play a key part in the funding and expansion of project teams.


bottom of page