{"id":585,"date":"2024-07-15T09:53:14","date_gmt":"2024-07-15T08:53:14","guid":{"rendered":"http:\/\/localhost:8082\/?page_id=585"},"modified":"2024-07-18T12:06:56","modified_gmt":"2024-07-18T11:06:56","slug":"visual-agile","status":"publish","type":"page","link":"http:\/\/localhost:8082\/scrum-helpline\/visual-agile\/","title":{"rendered":"Visual agile"},"content":{"rendered":"\n
<\/div>\n\n\n\n

Dear Scrum Helpline,

I’m currently working as a Business Analyst in a software development team within a local authority. We aspire to be a cross-functional team, but the reality is the UI design team rules the roost.

So pretty, high-fidelity designs get presented to the client with almost no consideration of whether they add sufficient value or are even possible to implement.

The mess then gets dumped on the BA and architect to fill in the specification gaps and reset expectations.

I feel too far down the foodchain to make much of a difference.<\/em><\/p>\n\n\n\n


\n\n\n\n

Response by Guy Maslen<\/a>, Scrum Master:<\/strong><\/p>\n\n\n\n

<\/div>\n\n\n\n

Dear Friend,<\/p>\n\n\n\n

\u201cTell me you are using a homebrew version of Scrum without telling me you are using a homebrew version of Scrum\u201d.<\/p>\n\n\n\n

Have you heard this saying before?<\/p>\n\n\n\n

By that I mean my go-to tends to be \u201cand when you raised this in your retrospectives what happened?\u201d<\/p>\n\n\n\n

Which then unpacks whether you\u2019ve been having retrospectives, and whether it\u2019s okay to raise difficult topics without relationships being damaged.<\/p>\n\n\n\n

More or less that\u2019s Amy Edmondson\u2019s work on psychological safety and learning in teams, which Google went on to adopt as one of their improvement projects.<\/p>\n\n\n\n