By admin on September 4th, 2014 in Agile
I’ve recently been trying to really polish my process for visual design and UX in agile. Although I feel like my process is getting better, as I covered in my post Agile Design, I still feel like there is room for improvement.
I recently came across a couple of blog posts on design sprints. This looks like it might be the right direction to head. However, these posts kind of deal with the issue from a start up perspective. Although that is useful, I’m more interested in learning about using an approach like this on Enterprise software. Have you done something similar on an Enterprise web application project? If so, please leave a comment explaining your process.
One of the biggest challenges I regularly face is to avoid being a bottleneck for other developers or the agile team as a whole. I was recently talking with another developer who followed a process similar to design sprints but he/she elaborated on it further.
When planning your UX, requirements, use cases, personas, etc… it definitely makes sense to involved some developers at this point. An approach to a feature you have in mind may make zero sense from an implementation stand point, so it can be really useful to involve the developers in the design process.
This will not totally keep them busy while you are working on design though. Another approach was to have developers work on designing back end services in parallel to your design efforts. At that point of the project, it shouldn’t really relate to the UI. That way you can all be moving forward, with no bottlenecks, without as much risk of work needing to be refactored down the road. Once your design sprints are done, there will be some back end architecture setup and you can get to the stories that integrate these two pieces together.
In the future, I definitely plan to try and use this process. What do you think of this model? Have you done something similar? If so, did it work for you team?