Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Agilism for AgilistMartin N. Rabaglia
AgendaAgilism for Agilist                               What we do?                               Why we fail?          ...
Waterfall Approach Inception, elaboration, build, test, release Agile Approach It provides focus on fixed time, fixed cost...
Adaptive Approach
1. Incomplete Requirements & Specifications2. Changing Requirements & Specifications3. Technology Incompetence4. Lack of R...
Solution Development        Process           =Communication Process
The quality of solutiondepends on the fidelity with        which the team communicates and  conveys the message.
What Communication means?
Day by Day                  Requirements             Designing Solutions             Code Documentation                ...
•How do you start your day?•Who knows best what to do?•How do you check what to do?
•Use Products Backlogs•Priorize the use of IssueTrackers• Document Technical Stuff.
•Say what your commits areabout.•Be clear when you resolve atask or a bug.
•Document the most importantparts of your code. >Checkstyles•Use unit test as documentation
•Always over communicate(ask,ask,ask)•Update tech supportive docs•Meetings to resolve, Mail toconfirm document the results.
•Continuous Integration is yourfriend.•Checkstyle.
Improved processes are started with the establishmentof specific goals and incremental         improvements.
Questions?
Thank You
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Rga.ba.agilism.july2011.v1
Upcoming SlideShare
Loading in …5
×

Rga.ba.agilism.july2011.v1

370 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Rga.ba.agilism.july2011.v1

  1. 1. Agilism for AgilistMartin N. Rabaglia
  2. 2. AgendaAgilism 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?
  3. 3. 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
  4. 4. Adaptive Approach
  5. 5. 1. Incomplete Requirements & Specifications2. Changing Requirements & Specifications3. Technology Incompetence4. Lack of Resources5. Unrealistic Expectations6. Unclear Objectives7. Unrealistic Time Frames8. New Technology CHAOS REPORT - http://net.educause.edu/ir/library/pdf/NCP08083B.pdf
  6. 6. Solution Development Process =Communication Process
  7. 7. The quality of solutiondepends on the fidelity with which the team communicates and conveys the message.
  8. 8. What Communication means?
  9. 9. Day by Day Requirements Designing Solutions Code Documentation Commits & Tags Automated Testing
  10. 10. •How do you start your day?•Who knows best what to do?•How do you check what to do?
  11. 11. •Use Products Backlogs•Priorize the use of IssueTrackers• Document Technical Stuff.
  12. 12. •Say what your commits areabout.•Be clear when you resolve atask or a bug.
  13. 13. •Document the most importantparts of your code. >Checkstyles•Use unit test as documentation
  14. 14. •Always over communicate(ask,ask,ask)•Update tech supportive docs•Meetings to resolve, Mail toconfirm document the results.
  15. 15. •Continuous Integration is yourfriend.•Checkstyle.
  16. 16. Improved processes are started with the establishmentof specific goals and incremental improvements.
  17. 17. Questions?
  18. 18. Thank You

×