make sliders 1 to 5 and max points is less than half of total possable

[Nitnop]

User Story

Story

As a user I want the product to force me to make choices, I want 5 sliders with 5 options from 1 (not inportant) to 5 (important) and I can only assign 12 points total so that I have to prioritize

Acceptance Criteria

Choose either rules or scenarios and ensure they are verifiable from the perspective of the stakeholder

Rules

*has slider with 5 'notches'

• only alowes user to 'spend' up to 12 points *sliders default to 0

Scenario 1

Given user uses points when user uses too many points then red text saying use less points

Supporting Information

[Relevant information, context, resources, references]

Dependencies

Depends On

[Links to other issues on which this story depends]

Dependents

[Links to other issues that depend on this story]

written by Cove Pontin and Angela Fleenor

[jody]

A user story is intended to guide developers in understanding what objectives the user wants to achieve.

This appears to be a specification of a specific design and implementation, which should be left to the developers.

[Nitnop]

I don't really understand the difference? If I was a user this is what I would ask for...

[jody]

That is a common case when interacting with clients. The job of the software engineer or analyst includes taking the client's statements and transforming them to provide a better solution..

User stories ideally focus on what the user wants to achieve, rather than how it should be done. This is recommended for several reasons:

• Focus on User Needs: It's better for user stories to describe the user's goals, like "control the volume," instead of suggesting specific solutions like using a "slider." This keeps the focus on what the user needs.
• Encourage Creativity: Without locking in specific design ideas, the team can explore different ways to solve the problem, leading to more creative and potentially better solutions.
• Avoid Early Design Decisions: Deciding on specific design elements too early can limit flexibility. By focusing on behaviors, the team can adapt and improve the design as they learn more.
• Adapt to Different Platforms: What works well on one platform (like a slider on a desktop) might not work as well on another (like mobile). Focusing on the behavior helps the team design for different environments.
• Support Agile Development: Agile teams often benefit from user stories being kept at a high level, allowing them to adjust and improve as they go. Avoiding specific design details makes this process easier.

In short, it's usually more effective for user stories to explain what users need rather than how it should look or function, leaving room for the more advantageous solutions.

[jody]

Please update the stakeholder type from "user" to "decision-maker" to match the stakeholder types found in the web documentation and the decision_support/README.md

[jody]

If I was a user this is what I would ask for...

It's great to think from a user's perspective. As developers, our priority is to understand the needs of the actual users and stakeholders. While personal insights can be helpful, the product's specifications should reflect their requirements, which may not always align with what we personally envision. Our role is to uncover and prioritize those needs.

[bhornick10]

I was part of this group and this user story. I just had not added my name.

[Nitnop]

Ok now that I understand the assignment I do think that this would be a good solution to #51, how do you want me to go about it? I think I should ask the user 'is this what you were envisioning'?

[jody]

Based on offline discussions, this represents anticipatory design thoughts. Closing this as a user-story. The issue remains accessible for future reference.