The Benefits of Agile,
the Needs of HW Development

MAHD Step 4: Building the Agile Backlog

Building the Agile Backlog

In step four, the team is now ready to develop their backlog — the prioritized list of work items that need to be done. Since the team is still engaged in On-ramp planning (and haven’t even started their first sprint), they will take a high level approach to capture large work items, knowing that each will be broken down further into more detailed tasks during sprint planning. User stories, requirements, product attributes, tasks, risks, resources and the progress toward completing the iteration successfully will all be reassessed by the team with each sprint.

MAHD Step 4: Building the Agile Backlog

Share This Post

Waterfall for Product Development Manifesto and 12 Principles

The Agile Manifesto for Software only needs minor changes to work for Hardware-based solutions. The primary differences are 1) hardware iterations cannot always “working” product to show progress and 2) while “individual” success is important in both software and software, it’s the collaboration of disciplines and teams that ultimately drive success for hardware solutions. Download the Agile Manifesto: HW Vs. SW to see how they compare along with the Five Pillars for MAHD Success.

Read More »

Get Started Going MAHD

Download one of resources below to get started on your agile for hardware journey. 

Get the Latest Resources

Sign up for the Going MAHD newsletter and get the latest resources delivered directly to your email. Your contact information will never be shared and unsubscribe at any time. 

Yes

A MAHD Overview

The five-page overview provides a quick summary of the MAHD Framework, benefits and unique attributes.

Intro to MAHD Core

The key elements of the MAHD Framework and how to get started including each step, the On-ramp, Focus Matrix and more.

Schedule a Discussion

Request a complementary 45-minute overview and discussion of your situation.