The Design Sprint is a new process for most people. It’s not immediately obvious how important are some of its aspects. This can easily spiral out of control, as one person’s assumption can have a knock-on effect on the entire group and the outcome. A skilled facilitator will alleviate most of these concerns, but it’s useful for every participant to know what “danger” is around the corner.
There’s a lot to unpack when working with an agile agency or advocating for agile at your own company. To an untrained eye, agile ceremonies might look like an overhead. Two of them – review and retrospective – have synonymous names. It doesn’t help your case.
Solving problems in a meeting is a bit of a myth. They drag on; the group gets overpowered by the loudest voices, and it usually ends with an email and an invitation to a follow-up meeting. What if I told you there’s an infinitely better way to do that? It takes just an hour, you can do it remotely and applies to any kind of problem.
An innovation framework calls for an innovative approach to dining. When we facilitate Design Sprints, our choice of food and snacks is scientific. Even though we don’t bring heaps of chocolate, it’s still delicious and fun. And, in the end, there is some chocolate. 😉
Technical debt is a metaphor for the shortcuts that we take in software development. In the same way that financial debt can be useful when it helps you to achieve your goals quicker, technical debt can make sense when it enables you to get something working quickly. These shortcuts come at the cost of increased development effort in future releases—effort that may be impossible to predict, but which can often be significant.
What is a user story? Why write it? Who writes? What is a good example of a user story? Are there any exceptions? In this article, I focus on an in-depth analysis of writing user stories from different angles.
The design sprint is an excellent innovation framework that brings the best out of the members of your team. But before diving deep into the exercises, the facilitators have an important job – to help you assemble the right design sprint team. Here’s are the key design sprint roles and tips on how to prepare a shortlist of participants from your company.
Have you ever wondered why web design projects take so long? For the most part, scale is achieved by throwing more resources on a project. But there’s plenty of room of improvement when it comes to traditional processes. We’ve adjusted the way we work to keep up pace with agile development, and here’s how we did it.
If you’ve never had an awful experience with building a website, cast the first stone. Projects are often a drag, they become a tug of war and everyone heaves a sigh of relief when they are done. This is probably the shortest and most accurate description of the traditional “waterfall” approach for web design.
You can’t know the future. Yet, we will do our best to guess what awaits in the world of web design. We have seen more bravery and attempts to cut through the noise. There is no doubt that some of those will stay with us forever. We also remain certain that web designers have other innovative ideas up their sleeves waiting for the right time.
The word ‘headless’ is gaining popularity in the industry. High-performance results and great scalability tempt everyone – however, is it enough to give up on solutions that work? Headless WordPress is an outstanding tool but comes with great responsibility.
Static sites are a thing of the past. Your visitors desire an interactive website and Google is taking it to the next level with Chrome AR. At the moment the feature is only available in the developer build of the browser, but we already have insight into how it can revolutionise our browsing experience – especially on mobile devices.