Designers changing mockups and calling correct & completed work defects

Open in a window
Article news.ycombinator.com

Designers changing mockups and calling correct & completed work defects

The business analysts write the ACs with generic "should match the approved mockups", we do the work, sometimes within the same sprint the designers edit the mockups subtlety (add a space, change a font size, change a few letters etc.) and then when the work is being tested, a defect always comes up. Sometimes this is months later and randomly we will have a regression in many spots. Normally it isn't that bad & only noticeable differences between the mockups got reported, however, recently the design team has started reporting defects related to pixel differences in spacing... I've asked the business analysts to include a picture of the mockup in the ticket to avoid these problems & the design team threw a fit saying it's better to use their mockup in live figma because it's more up to date.... I have caught the design team doing this & had a sc of my own when the tester reported a defect & the designers tried to play it off like we were both confused when confronted.

I have two issues with this... Firstly, can they really call it a defect if the spacing size differs slightly between the mockup and the actual page but the style is identical ? If it is being used consistently, I don't see how its a defect. The ACs don't say that it should be to the pixel of the mockup, but it should look like & follow the mockup's design... There is no ACs specifically calling out the margins and padding between elements to the pixel, so adding a defect seems ridiculous. Secondly, and maybe worse... using a live figma board to base the ACs off allows the designers to escape accountability. Any time the designers make a mistake, they can just edit the figma & their mistake turns into the developers mistake adding way more points to stories than would have been if they actually paid attention to the designs. It's so ridiculous that they can change the design mid sprint or sprints later & then call the closed out & completed work a defect, but when their design isn't followed by to the pixel, they have the audacity to open a defect. I'm talking they go into the HTML and then use that as a bases for a defect, if you looked at the mockup it would be identical!

Thoughts?

Discussion 4 comments · 1 points · LandOfMightDev · 1d
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. The list is kept in this browser only.

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Open the marked story in a window.
]
Open the next story in the list in place of the one in front. Back returns to it.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Open several stories to compare them, and switch between them from that bar. A window's Next story link reads on down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.