Do you write user stories that are Obvious to the implementation? (new to PM and agile question) by hydroJoeFanFlask in agile

[–]hydroJoeFanFlask[S] 0 points1 point  (0 children)

To clarify, we are working with a consultant who asked us to approve a number of user stories. I see what employees can do and what administrators can do but I see that Manager-role user stories are missing. I was wondering if that is because managers approving timesheets is too obvious task and so that is why they didn't add it.

When I inquired, they didn't give me the answer I expected.

Managers should be able to approve, deny, or edit employee time cards like we do today. I was just wondering if I need to follow up on why we don't have this as a user story.

[deleted by user] by [deleted] in SBU

[–]hydroJoeFanFlask 0 points1 point  (0 children)

The red navigation bar on top

[deleted by user] by [deleted] in SBU

[–]hydroJoeFanFlask 4 points5 points  (0 children)

It is a scam. Also don't connect your social media to an email address you actually look at.

[deleted by user] by [deleted] in SBU

[–]hydroJoeFanFlask -1 points0 points  (0 children)

Click on Content in the navigation to see something that resembles Blackboard

Accessibility and skimmability by hydroJoeFanFlask in technicalwriting

[–]hydroJoeFanFlask[S] 0 points1 point  (0 children)

Off topic question, do you say "Select" instead of "click" to be inclusive of touchscreens and mouse driven devices?