IBM Design Thinking Framework

1. IBM DESIGN THINKING FRAMEWORK
PERCIVAL LUCENA * ALAN BRAZ * ADILSON CHICORIA * LEONARDO TIZZEI

2. HOW THE BACKLOG WAS BORN?

3. SCRUM BACKLOG GROOMING
Chand Warrier - Scrum Alliance

4. ANALYTICAL SCIENTIFIC METHOD VS DESIGN THINKING

5. DESIGN THINKING

6. IBM DESIGN THINKING
DT phases
IBM DT practises

7. SPONSOR USERS
➤ Sponsor users are real people, from outside your
organization, who can share his or her
experiences and point of view with the team
about the context of the problem.
➤ They are active participants who co-create with
you and your team. Every interaction you have
together closes the gap between your
assumptions and their reality
➤ Sponsor User must be willing to commit some of
their time to help you and your team understand
their needs and wants in the experience that
you're designing.

8. HILLS

9. PLAYBACKS

10. ROLES

11. ROLES

12. TEAM EMPOWERMENT
➤ Product Manager defines a certain number of
hours that could be invested on each Hill.
➤ Teams are fully empowered to achieve the Hills,
within their investment parameters, and make
the trade-offs required to hit the marks

13. IBM DT - SURVEY

14. DT - SURVEY

15. CONCLUSIONS
➤ IBM DT Framework focus on users’ needs and the ever-changing technological
landscape as an opportunity to re-think how a problem can be solved.
➤ IBM DT Framework visioning phase identifies and investigates with known and
ambiguous aspects of the current situation to discover hidden parameters and open
alternative paths that may lead to innovative solutions.
➤ IBM DT Delivery wave provides iterative software development using Sprints and
Delivery Playback meetings.
➤ Project Survey helped to understand qualitatively important aspects on how to
implement IBM DT as ASD method.
➤ Further studies should be done in order to understand the strengths and the
limitations of the software developed framework