Labels

What are the real-world needs? What sorts of considerations do we need to look at?

How does a feature fit into the broader software? How do users enter and leave? How do we onboard and offboard?

We understand how something is going to work, but how is going to function, look, and feel?

Product team has finished the commercial assessment, ready to handoff.

Big picture discussions, clarificiations, and direction. “Where do we want to go?” rather than, “How do we get there?”

Fixing the issue is really hard and requires an investment. The exact causes are unknown, require additional profiling, or a major restructure of the codebase.

This is so easy to fix, you should probably have already done it.

Fixing the issue provides a moderate challenge. Clear your schedule for the next couple of hours, you've got this!

This is a difficult issue. You will need knowledge of the codebase and it will require a significant amount of time.

A specific use-case or set of criteria that needs to be captured in a test (which is preferably automated).

An issue or merge request that is being used for feature work. It will be closed during a comprehensive review that is part of hand-off.

A planning item that tracks multiple issues or merge requests. (A really big piece of scope.)

The feature has been implemented and is waiting to be reviewed or otherwise just hanging out. (Another way of saying, almost done.)

The issue is currently in staging and requires review, or has appeared as part of quality assurance and needs to be addressed.

Fixing the issue is easy, probably an afternoon project.

High value software feature. Provides a significant improvement to the software and should be scheduled for implementation.

Low value software feature. May bring some value improvement to the software but it is either niche or "nice to have" in nature.

Moderate value software feature. Solid improvement to the software which will impact many (if not the majority) of users.