1. Agilism for Agilist
Martin N. Rabaglia

2. Agenda
Agilism for Agilist
What we do?
Why we fail?
How can we improve?
Communication
Day by Day
Week By Week
Build by Build
How to make it happen?

9. Waterfall Approach
Inception, elaboration, build, test, release
Agile Approach
It provides focus on fixed time, fixed cost, allowing
features to be more variable
Doesn’t account for the part of our process.
Creative Process = CHANGES

10. Adaptive Approach






13. 1. Incomplete Requirements & Specifications
2. Changing Requirements & Specifications
3. Technology Incompetence
4. Lack of Resources
5. Unrealistic Expectations
6. Unclear Objectives
7. Unrealistic Time Frames
8. New Technology
CHAOS REPORT - http://net.educause.edu/ir/library/pdf/NCP08083B.pdf

14. Solution Development
Process
=
Communication Process

15. The quality of solution
depends on the fidelity with
which the
team communicates and
conveys the message.

17. What Communication means?

19. Day by Day
Requirements
Designing Solutions
Code Documentation
Commits & Tags
Automated Testing

20. •How do you start your day?
•Who knows best what to do?
•How do you check what to do?

21. •Use Products Backlogs
•Priorize the use of Issue
Trackers
• Document Technical Stuff.

22. •Say what your commits are
about.
•Be clear when you resolve a
task or a bug.

23. •Document the most important
parts of your code. >
Checkstyles
•Use unit test as documentation

24. •Always over communicate
(ask,ask,ask)
•Update tech supportive docs
•Meetings to resolve, Mail to
confirm document the results.

25. •Continuous Integration is your
friend.
•Checkstyle.

26. Improved processes are
started with the establishment
of specific goals and incremental
improvements.

27. Questions?

28. Thank You