Building things in a team is a difficult proposition.

1. WHAT THE REQ?
B U I L D I N G T H I N G S T O G E T H E R I S T O U G H !

3. ABOUT ME
• Coded, Managed, PO’d, Coach + Mentor
• Built many projects. Some were successful…
• …some failed
• Waterfall’d, RUP’d, Scrum’d, XP’d, Kanbaning + Leaning
• Community organizer – Agile Malaysia / DevOps Malaysia

4. THE FAMILIAR SAFE WATERFALL…

5. THE FAMILIAR SAFE WATERFALL…

6. THE FAMILIAR SAFE WATERFALL…

7. THE FAMILIAR SAFE WATERFALL…

9. 3 OR 4?

10. EXERCISING
BABY

11. CHICKEN & DUCK
TALKING

12. WHO MAKES PRODUCTS?
Engineering
aka.
Developer, programmer,
engineer, tester, ITPro,
SysAdmin
Marketing
aka.
Product Owner, Product
Manager, Marketing
Manager, Boss
&VS?

13. LET’S MAKE SOMETHING!

14. ORIGAMI
BuildRequirements
15 MINUTES (?)

15. RETROSPECTIVE
•What went well?
•What didn’t go so well?
•What have I learnt?
•What still puzzles me?

16. TIPS:
1. Present instructions in a way that
is clear and simple.
2. Make it clear whose point of
view you’re speaking from.
3. It is your responsibility that your
instructions are getting across to
the other party.
4. Form common vocabulary.
1. Ask questions. Lots of them. Its
OK to question the
requirements!
2. Try to understand the big picture
before starting.
3. It is your responsibility that you
understand the instructions
before executing.
4. Form common vocabulary.

17. ORIGAMI: ROUND 2!
BuildRequirements
15 MINUTES (?)

18. DONE!
• About me: linkedin.com/in/tzetang
• Agile Malaysia: www.agilemalaysia.org
• DevOps Malaysia:
fb.com/groups/devopsmalaysia/