Presentation about the chapter 8 of the book designing delivery re thinking it in the digital service economy

1. Building Quality In

2. Hello!
I am Alejandro Villa
2

3. Introduction
1

4. Every service or work after the post-industrial economy
requires coninual adaptation.
Therefore service becomes a process of continual repair
and quality assurance is just another name for the day-
to-day functioning of the business
4

5. Why continous design
matters?
2

6. It pushes the perspective even further
and challenges
Service organizations to acknowledge
that design and development are
never done, no matter how well testes
their products are. And detects gaps
between actual and expected in
production.
6

7. What is the job of a
tester?
3

8. Is not assure quality, but rather
contribute to it providing the
information needed to guide accurate
re-action.
Testing validates an organization’s
ability to hear accurately as part of
those conversations.
8

9. There are four dimensions(measures)
of digital service used to achieve
quality:
1. Outcomes.
2. Access.
3. Coherency.
4. Continuity.
9

10. Optimizing Feedback

11. Feedback improves adaptability and
thereby competitiveness.
The more quickly and continuously an
organization can use feedback to
detect changes in destination, the
more energy it can devote to paddling
in the right direction.
11

12. Infusion Changes Design

13. As software becomes more central to
out daily lives, UX design becomes
critical to service quality.
Users have become accustomed to
high-quality digital experiences.
That’s why the user interface should be
usable.
13

14. Always ask yourself:
What do i want the user
to do or feel?
What does the user want
me to do or understand?
14

15. Services Changes Development

16. As customers become
accustomed to the service model,
they begin to judge software
service by how smoothly and
continuously they can repair gaps
between actual and expected
quality.
16

17. This forces software service providers
to adjust the way we produce
software, long release cycles are no
longer feasible.
We need to deliver more often in
smaller quantities. This is when agile
comes handy!
17

18. QUALITY > SPEED
18

19. This forces software service providers
to adjust the way we produce
software, long release cycles are no
longer feasible.
We need to deliver more often in
smaller quantities.
19

20. Test-Driven Development

21. The most efficient way to produce
good code is to detect bugs while
coding.
Unit testing helps uncover logic
bugs
21

22. Test Driven Development is a
technique that involves writing unit
and integration test before writing
the code.
This ensures that the developers
will code thinking in terms of how
their code will be used.
22

23. Continuous Integration

24. In order to provide genuinely
useful feedback test needs to
automatically run whenever
needed.
You need to test the code when
something changes!
24

25. You can fix bugs if you can
associate them with small code
changes.
Code-writing and test-writing
need to happen synchronously
25