Remove Design Remove Software Developers Remove Training Remove Underperforming Technical Team
article thumbnail

Integrating ‘Agile’ Approaches into ‘Waterfall’ Cultures

InnovationTraining.org

is the guiding question, and we develop solutions based upon our understanding of the answer. If we can understand this set of desired outcomes, we can plan backwards from that endpoint to determine a series of steps in product or service design. Step 2 – Design : Build a system that responds to these requirements.

Agile 74
article thumbnail

Bringing User Centered Design to the Agile Environment

Boxes and Arrows

I built a team with a dedicated user researcher; information architect; interaction and visual designers and we even made a guerilla usability lab and had regular test sessions. As the Creative Director, I deferred authority to him to develop the product as he saw fit. This is an extreme example of where SCRUM went bad.

Agile 108
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Do You Know Your Users?

Boxes and Arrows

False consensus bias contributes to making bad decisions when we design software. Alan Cooper noted this type of bias while wondering why otherwise smart, talented people often created such crappy software. Have you ever heard anyone on your team say, “what if the customer wanted [some feature]?” What are personas?

article thumbnail

As our lives become more automated, these are the skills you’ll need

Faisal Hoque

For instance, an engineer who can develop brilliant new product designs but who can’t effectively communicate the value of those designs to others (or collaborate with design teams to bring those ideas to life) is doing himself and his organization a major disservice. FOCUSING ON “SOFT SKILLS” PAYS OFF–LITERALLY.

article thumbnail

As our lives become more automated, these are the skills you’ll need

Faisal Hoque

For instance, an engineer who can develop brilliant new product designs but who can’t effectively communicate the value of those designs to others (or collaborate with design teams to bring those ideas to life) is doing himself and his organization a major disservice. FOCUSING ON “SOFT SKILLS” PAYS OFF–LITERALLY.

article thumbnail

The Innovation Stack

The Inovo Group

A third model – the knowledge/flow model – offers an alternative perspective and approach to designing and building an innovation system. The innovation stack is analogous to a ‘full-stack’ in software. Software stacks are used to develop complex software applications.

article thumbnail

The Engineering Stakeholder Interview

Boxes and Arrows

This is an excerpt from from Kim Goodwin’s excellent Designing for the Digital Age. Try to speak with engineering management as well as the design engineer(s), if such a role exists; it’s seldom a good idea to involve the entire engineering team at this point. Programmers and engineers may initially be wary of designers.