Skip to content
This repository was archived by the owner on Jun 5, 2025. It is now read-only.

Update user story issue template#984

Closed
ethomson wants to merge 1 commit intostacklok:mainfrom
ethomson:issue_template
Closed

Update user story issue template#984
ethomson wants to merge 1 commit intostacklok:mainfrom
ethomson:issue_template

Conversation

@ethomson
Copy link
Copy Markdown

@ethomson ethomson commented Feb 7, 2025

Add some additional information to our user story template to include additional information for the "feature brief".

Add some additional information to our user story template to include
additional information for the "feature brief".
Copy link
Copy Markdown

@scottdouglasbuchanan scottdouglasbuchanan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fussy with word choice. Under Description:

From "Describe the need. Why is it needed? What is the expected outcome? What is the impact?" Consider simplifying to: "What is the current pain or problem? What job is the developer trying to get done?"

From: "What is the feature? What is the expected outcome? Why does it matter? Who benefits? Consider simplifying to: "How would you explain what this feature and why it matters to a peer learning about it for the first time?"

^I think framing in this way will produce material that is less immediately technical, and more usable across channels.

id: release_date
attributes:
label: Release date
description: Estimated release date (yyyy-mm-dd)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No one would know this at this point, it would still need to go through backlog prioritization and even then, if something more important comes up, it could well get dropped.

- type: dropdown
id: release_tier
attributes:
label: Release tier
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this even been known at this point? If it means someone needs to discuss with marketing first and have it planned to this degree, I would say we are still to new and in discovery to be planning this much.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. I think we should remove 'release tier' from the brief.

Copy link
Copy Markdown

@lukehinds lukehinds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels a bit overwhelming with how many questions there are, to be honest.

@annajomorelia
Copy link
Copy Markdown

I'm fussy with word choice. Under Description:

From "Describe the need. Why is it needed? What is the expected outcome? What is the impact?" Consider simplifying to: "What is the current pain or problem? What job is the developer trying to get done?"

From: "What is the feature? What is the expected outcome? Why does it matter? Who benefits? Consider simplifying to: "How would you explain what this feature and why it matters to a peer learning about it for the first time?"

^I think framing in this way will produce material that is less immediately technical, and more usable across channels.

The only addition I would have is: What are the characteristics of a developer that would find this valuable?

I think that way, it's just three questions to start with so should feel less overwhelming.

@dussab
Copy link
Copy Markdown
Member

dussab commented Feb 19, 2025

@ethomson What are the next steps here? Should we close the issue and revisit it later on?

@ethomson
Copy link
Copy Markdown
Author

I'm going to rework this; in the meantime, I'm closing this. 🙏

@ethomson ethomson closed this Feb 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants