How we use Agile in a real-life project

At Hiyield, our product managers run their projects using the agile methodology, and we do this for multiple reasons.

Why do we work agile at Hiyield?

The main reason we work in an agile manner is to adapt swiftly to changing requirements and market dynamics, ensuring efficient delivery of high-quality solutions that meet client needs effectively.

How we implement the agile methodology.

To incorporate the agile methodology into our work, we follow this process:

User stories

We start by looking back at our discovery phase, and based on what we learned, we write our user stories.

Design solutions

Based on the user stories written we come up with design solutions that fit into this.

Split into features

We split the product up into epics/features, making it easier to look at.

Backlog features with tasks

We backlog features with user stories and tasks so that we can assign the team to tasks more easily.

Estimate time

Looking at all the tasks we have, we estimate the development time needed to build all the features.

Create sprints

We split all the features into different sprints based on priority.

Sprint time

For sprints, we plan, design, develop, test, deploy, and review. We include the client and users by gathering feedback to add to the next sprint on a separate Kanban board, ensuring we focus on one sprint at a time.

What is a Kanban board?

Great question! Let’s dive into everything Kanban boards and why we use them at Hiyield. 👇

Transparency

Having a Kanban board for each sprint provides transparency and helps with clear communication in the team.

Progress

This helps the team be aware of our progress throughout the entire sprint.

Status of tasks

A Kanban board clearly represents the tasks that still need to be completed at a glance.

Visual representation

We know everyone processes information differently, and we’ve found that having a visual representation of tasks works best for our teams.

Constantly updated

Our Kanban boards are always being updated, so they will give our teams an up-to-date view of the sprint.

Planning

A Kanban board massively helps when it comes to planning as we can quickly see the number of tasks needed to be completed and assign people in the team to projects and tasks at the beginning of a week.

Using the agile methodology in a real-life project: Proper Plan

This project was managed using the agile methodology, one of the main things we took was using sprints to divide tasks effectively and ensure progress was being made. Acceptance criteria and check-ins were conducted so that the product delivered was meeting the client’s needs. We fostered a feedback loop needed for refining features and meeting user expectations.

To be transparent with our client, we shared shippable features, with a dashboard sent out every couple of weeks before to launch to evaluate progress and provide feedback, allowing for a more focused view of individual features.

User feedback played a key role throughout development, informing changes to feature priority and incorporating new technologies based on user preferences. Connecting with beta testers through interviews gave us insights, letting the team refine the product further and enhance user satisfaction.

If you’d like to find out more about how we work in an agile method for projects, get in touch we’d love to talk about how we can use this to make your dream a reality.