Remove Design Remove Document Remove Software Developers 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

The role of design thinking in fixed price contracts

Dawid

Design Thinking does very well when you have somewhat loose constraints. We have full permission to go back to the drawing board as failure is cheap in Design Thinking, and isn’t considered failure at all, but instead it’s feedback. That’s where Design Thinking methods are critically important. It’s not their role.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Why is developing digital products one of the solutions to overcome the crisis?

mjvinnovation

What makes us believe that developing digital products is not only a solution to overcome the crisis, but also to generate business value after it too. Who would have thought it would be possible to get a credit card without any contact with human service, not even sending the documentation? Don’t forget: Design creates a link.

article thumbnail

Agile vs Waterfall: what are the differences?

mjvinnovation

Traditionally, the Waterfall model is a linear approach that has a sequence of events somewhat like this: To Gather and document requirements; To draw; Code and unit test; To Perform the system test; To Perform the user acceptance test; To Correct any problem; To Deliver the finished product. There are good and bad things about this approach.

Agile 40
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
article thumbnail

The role of design thinking in fixed price contracts

Dawid

Design Thinking does very well when you have somewhat loose constraints. We have full permission to go back to the drawing board as failure is cheap in Design Thinking, and isn’t considered failure at all, but instead it’s feedback. That’s where Design Thinking methods are critically important. It’s not their role.

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?