¿Es tu buzón de correo electrónico tu lista de tareas? ¿Te persiguen contínuamente con tareas a completar para ayer? ¿Perteneces a un equipo de mantenimiento y mejora de sistemas informáticos tales como aplicaciones web? Deja de correr, acércate a la fuerza de la agilidad. Te explicaré brevemente los pequeños grandes pasos que hemos ido realizando en nuestro equipo de programadores y técnicos de producción, y que nos ha permitido planificar semana a semana aquello que se espera de nosotros como equipo. Que tu equipo no sea un agente pasivo. Que el equipo sea un agente activo dentro de tu organización.

1. The force of being agile
Jordi Pujol Ahulló
Servei de Recursos Educatius - SRITIC - URV
jpahullo

2. #Agile, in my way 2

3. URV
SREd
A-Team

4. 95%
… of maintenance.
We do not develop new big projects.
4
All trademarks are propietary of the respective companies. They are only used here for reference.

5. What kind of
#conversation
do you have
with your #client?
5

6. I
want
to be a
good
professional
6

7. Why not ...?
#conversation
#expected
#ontime
#accordingToPriorities
7

8. I decided to
#research on
#Agile
methodologies
● #Twitter
● #Blogs: Javier Garzás
● #MOOC: 5th Spanish Edition
Agility and Lean (Miríadax)
● Join #Meetup @agileCampTgn
● and ...
8

9. 4 values
… of the #Manifesto for
#Agile #Software #Development.
9

10. Individuals and
interactions
over processes and tools.
10

11. Individuals and interactions
11
● Adapt processes and tools to
members of your team:
Boost your team
● If members change, processes
and tools may change.
Like:
● 1 week sprints
● Daily standups

12. Working
software
over documentation.
12

13. Working software
13
Goal: No errors on production
Goal: Confidence and reliability.
Feedback, feedback, feedback.
Like:
● Review issues’ detail
● Review code and testing
● Repeat, repeat, repeat

14. Customer
collaboration
over contract negotiation.
14

15. Customer collaboration
15
● Consider “boss” and other
“business” people as clients.
● Tell them new workflow.
● Share information
Like:
● Share priorities.
● Can we wait for it to next sprint?
● Email? Goes to product backlog

16. Responding
to change
over following a plan.
16

17. Responding to change
17
● It’s all about priorities!
● Sharing information.
● Make explicit what was implicit.
● Product/service oriented.
● Organizational issues.
Like:
● Include “clients” into workflow.
● Product: Weekly sprints.
● Org.: Montly retrospective.

18. Nowadays...
18
All trademarks are propietary of the respective companies. They are only used here for reference.

19. Lessons
learned

20. Everyday work
eats all your time.
Enforce sprint inamobility.
Lessons learned 20

21. Include few changes
into your team and
interactions with clients.
Lessons learned 21

22. Less is more.
Small changes + Apply + Feedback + Learn
Lessons learned 22

23. Make the
#difference
23
Hi! I’m Pingu!
#gamification
“giving thanks”

24. The force of being agile
#thanks #Techne18 #agile
Jordi Pujol Ahulló
Servei de Recursos Educatius - SRITIC - URV
jpahullo