{"id":798,"date":"2024-09-20T10:30:57","date_gmt":"2024-09-20T09:30:57","guid":{"rendered":"http:\/\/localhost:8082\/?p=798"},"modified":"2024-10-11T09:34:05","modified_gmt":"2024-10-11T08:34:05","slug":"how-ux-design-without-technical-input-caused-our-sprints-to-break","status":"publish","type":"post","link":"http:\/\/localhost:8082\/2024\/09\/20\/how-ux-design-without-technical-input-caused-our-sprints-to-break\/","title":{"rendered":"How UX design without technical input caused our sprints to break"},"content":{"rendered":"\n
The developers failed to deliver their commitment again, and management expressed their frustration by putting the team \u2018on notice\u2019.<\/p>\n\n\n\n
The low down was incomplete features and questionable quality, and the previous four sprints were not much different. The technical team leader couldn\u2019t be more stressed about fronting another disappointing demo.<\/p>\n\n\n\n
This was the situation I walked into when accepting a Systems Analyst role on the team, but I had been briefed ahead of time and felt confident that improving things was more straightforward than it appeared.<\/p>\n\n\n\n
What I Discovered<\/strong> The Problem<\/strong> The Solution<\/strong> As a result of these changes, tickets flowed across the board, delivery predictability increased, and rework significantly reduced. Sprint demos became a joyous occasion, and management praised the team.<\/p>\n","protected":false},"excerpt":{"rendered":" The developers failed to deliver their commitment again, and management expressed their frustration by putting the team \u2018on notice\u2019. The low down was incomplete features and questionable quality, and the previous four sprints were not much different. The technical team leader couldn\u2019t be more stressed about fronting another disappointing demo. This was the situation I […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24,20,17,23],"tags":[],"class_list":["post-798","post","type-post","status-publish","format-standard","hentry","category-case-study","category-software-development","category-software-requirements","category-systems-analysis","missing-thumbnail"],"_links":{"self":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/798","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/comments?post=798"}],"version-history":[{"count":5,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/798\/revisions"}],"predecessor-version":[{"id":865,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/798\/revisions\/865"}],"wp:attachment":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/media?parent=798"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/categories?post=798"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/tags?post=798"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
The UX team produced high-fidelity designs ahead of each sprint, which became sprint commitments without technical validation. Developers then broke the designs into individual screens, creating a ticket for each and forming their backlog.<\/p>\n\n\n\n
The UX team lacked technical expertise and often produced visually appealing but technically unfeasible designs. This resulted in unexpected blockers, frequent rework, missed deadlines, and stress within the development team.<\/p>\n\n\n\n
Design reviews were held earlier in the process to ensure each user journey was technically feasible, collaboration with the UX team promoted more realistic sprint commitments, and developers worked from a well-defined backlog validated by technical analysis.<\/p>\n\n\n\n