background preloader

Agile Design

Facebook Twitter

Agile Design. 1. Agile Design Practices There is a range of agile design practices, see Figure 1, from high-level architectural practices to low-level programming practices. Each of these practices are important, and each are needed if your team is to be effective at agile design. Figure 1. Agile design practices. 2. 3. Figure 2. Figure 3. When a developer has a new requirement to implement they ask themselves if they understand what is being asked for. If the team is taking a Test-Driven Development (TDD) approach the detailed design is effectively specified as developer tests, not as detailed models. When you stop and think about it, particularly in respect to Figure 2, TDD is a bit of a misnomer. Designing with agility — Mathew Sanders. 1. Distinguish ideation from execution It might seem obvious, but one of the biggest problems I’ve seen in design teams is the inability recognize an ideation mode of working and an execution (or refinement) mode of working.

Bill Buxton said it best: you have to get the right idea before you get the idea right. At the start of your project you should mostly be working in ideation where you must explore a wide range of ideas. Over time you will need to transition to an execution mode and focus on the finest details. You need to make sure that your team (and any stakeholders) clearly know what mode of work you’re in. 2. A common approach with agile projects is to add a design spike at the start of the project allowing the team to perform enough research for the project to proceed with confidence. If you can afford it, then go ahead! The alternative is to learn through making. Understand that during early stages of a project uncertainly will be high. 3. 5. This is the easiest to fix. 6. 7. 8.

Design sprint

Black&White™ » Blog Archive » Getting to the Customer – Why Everything You Think about User-Centred Design is Wrong. Let me ask you a question. If you had an idea for a new hammer and you wanted to test it, which of the following ways do you think would yield you the most valuable feedback? I am guessing most of you would choose #4.

After all, getting a feel for the hammer requires the customer to actually try it out. Looking at a picture of a hammer, cutting it out, or even providing a Styrofoam prototype simply won’t provide you or the customer with sufficient foundation on which to evaluate it. However, if I asked you to test a digital product, whether it be a website, an application or an e-commerce site, most of you would choose #1, 2 or 3. Isn’t that odd? A simple product like a hammer is best tested in its final form. Nonetheless, this is the current reality of applied UCD, or User-Centered Design. Usability tests, focus groups and personas to name a few, all are intended to increase usability, and create better products by having users test them.

There is something flawed in this approach.


Principles. Getting Real About Agile Design. Agile is here to stay. The economic difficulties of the past months have finally put waterfall out of its misery; now more than ever, long requirements phases and vaporous up-front documentation aren’t acceptable. Software must be visible and valuable from the start. For many designers, Agile is already a fact of life (and for those less accustomed, some recommended reading follows at the foot of this article). We are reaching the point where we must either acclimatize or risk being bypassed. The good news is that Agile does allow us to still do the things we hold dear—research, develop a vision, and test and improve our designs—we just need new techniques. Now is the time to get real, and prove design can adapt, if we want to stay relevant in these increasingly unreal times.

The story so far#section1 Time, research, and ideation have historically been designers’ comfort zones. Agile, on the other hand, aims to deliver software quickly and handle change smoothly. Research#section2. Understanding Agile Design and Why It’s Important. It’s no secret that the agile development process has been hurtling through the development world for several years now, swatting aside the older, clunkier waterfall development method.

To be fair, whether it was agile or something else, waterfall really had it coming, as its risk-averse, top down approach just can’t keep pace with the demands of today’s marketplace. While similar changes are occurring in the design world, the agile design process should necessarily look and feel a little different than agile development; they are, after all, different disciplines. Let’s take a deeper look first at what agile development is, and then at a few great ways to adapt the process to the design world. A Quick Primer on Agile Development More than anything, the agile process emphasizes the production of on-time and on-budget deliverables, not perfection, as products can always be tweaked down the road. So what steps can you take to adapt similar mentalities for a design setting?

In Short. Change on a Dime: Agile Design. What does it mean to have a good experience? Think of your favorite restaurant, the interior of your car, and the software on your phone; how do people craft these experiences? What details, planning, and design go into the process? Would it be possible to create a great experience if you were limited from laying out a full design before you got started? That’s the typical scenario in designing a user experience within the realm of agile software development. Development Through Agile In large part, the movement towards agile is a response to an industry perception of heavy, slow, and bloated software development. Agile was conceived as an alternative approach that delivers a constant stream of value through much smaller deliverables. The primary values of agile are to quickly deliver functioning software and allow for changes in requirements throughout development.

Assume for a moment that you’re tasked with creating a mobile travel application. Designing Without Design Upfront. Designing with Agile. Why Anders? Anders Ramsay describes himself as an obsessive and passionate explorer of ways to more effectively bridge the Yes/No world of computers with the Maybe-this/Maybe-that world of people.

And that undying curiosity is exactly why he is one of the most sought-after UX designers today. Beyond designing usable products for clients such as AOL, CBS, and Sony, Anders also is writing a book for Rosenfeld Media. In 2012, watch for the release of Designing with Agile: Lean User Experience for Successful Products Can't wait for Anders' book? Neither can we! But you can tell the awesome folks at Rosenfeld Media to let you know when it's available. The Agile Designer — Product Design. Knowing when to deviate from the norm is just as important as sticking to the norm. But prescriptive design processes are like prescriptive gym shorts.

A lot people who are almost close in size might be able to squeeze on the same pair of trunks but it’s going to get uncomfortable soon after the start of the run (not to mention the chance of sporting a camel toe. OUCH.) Away from cheesy metaphors, the way I design doesn’t necessarily work for the designer next to me or the one next to him or her. As a fellow designer or product manager, you might disagree.

I was once on a team who I adored but we fell down a waterfall path a year into working on a promising product relaunch. Overworked and often defeated by decisions that lacked any of our own creative input, more meetings were scheduled as opposed to working jams for creatives. A waterfall process is intended to remove unnecessary steps and too many people swimming in rapid waters. Agile design is not a process. Avoiding fatlogs.