search

cfpb / sbl-ux

Small business lending project's UX design and research issue repository
Creative Commons Zero v1.0 Universal
1 stars 0 forks source link

Update story template in project repo #20

Open natalia-fitzgerald opened 3 weeks ago

natalia-fitzgerald commented 3 weeks ago

Task

We have now made changes to our work process. The purpose of this task will be to determine what we would like to include in the updated story template on the sbl-project board.

We can use this blank issue in sbl-project as our prototype: https://github.com/cfpb/sbl-project/issues/291

Screenshot 2024-10-28 at 2 35 02 PM

Checklist

dan-padgett commented 2 weeks ago

To better understand the scope here, are we:

For the UX work, we also need to think about what level of detail goes into the project repo tickets vs the ones in this repo. For example, we could try adding "Review UX Research and Design Questions doc for relevant user insights" as a task for design work to ensure that we're using that information. That seems like it's specific enough to just be a part of tickets in this repo. But maybe we want a more general "Problem discovery and definition" task for the project repo tickets.

Also, where is our updated process documented? If it's not also in GH, we should consider adding a doc that outlines the process as we work through this ticket. Especially if we're going to capture tasks for tickets in both project repo tickets and ux repo tickets.

natalia-fitzgerald commented 2 weeks ago

@dan-padgett The purpose of this story template update is to broadly capture the cross-discipline work that goes into tackling our user stories. We will be adding UX, Content, and Data task sections. The work of these disciplines was not previously represented in our story issue template. As a part of this story issue template update, we can also better define the UX design/research work that should be built into each story.

We still need to update our process documentation to reflect recent changes.

dan-padgett commented 2 weeks ago

Given that, I think there are a few things we might want to consider as checklist items for UX:

  1. Define design problem: this is kind of similar to the "Write initial user story" item in 293 but might be more aimed at revising any initial user stories (or recommending that they don't fit an actual user need) and gathering any other information we need (from data, e.g.).
  2. Design exploration: initial creation of mockups to solve the design problem
  3. Review options with team and decide on solution approach: this would make review at the design/dev sync a gate for moving forward. Included here could be any revisions that need to happen.
  4. Finalize design and update acceptance criteria to reflect desired UI behavior: I think this is a nice way to "handoff" design work since there's a good chance that we'll have discovered use cases or interaction requirements while working on a solution.

Within UX tickets, we could obviously get a bit more granular. For instance, making sure that we're accounting for any relevant research by looking at the UX research and design question tracker during step 2 and adding any new questions as a part of step 4.

@natalia-fitzgerald What do you think of those 4 steps as a general framework to start with for the user story template?

natalia-fitzgerald commented 1 week ago

@dan-padgett Here's an image of the current template we're using.

Image

The main sections are:

In your post it sounds like you are getting at how we can further refine the UX part of the "Technical tasks" section. Currently under UX we have the following:

UX

Pass at applying what we discussed today

It seems as though a lot of what we've been discussing related to the backlog refinement process will pull a lot of items out of the UX section. Perhaps we may want to add a separate section called Story refinement or something like that. There we could track the progress that we discussed in this morning's meeting --- refinement ready, refinement in progress, refinement complete.

Epic

Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.

User story

Acceptance criteria

Story refinement steps

Technical tasks

Once story refinement is complete and the story has been brought into the current sprint, team members should create task issues and add links to those tasks.

UX

Front end

Back end

Data