Agile phobias

12,291 views

Published on

Published in: Technology, Health & Medicine
2 Comments
2 Likes
Statistics
Notes
  • Abhishek,

    You are raising valid concerns. My 2 cents how to handle these situations better are as follows :

    a. Freeze the requirements early in the cycle. It's good to have an incremental design, which can cater to changes in business requirements. However, if components have to be added and removed late, we're wasting effort - which is not healthy in the long run. I think the design, project plan, and the implementation approach needs a rethink in this case.

    b. Scaling problems are more of design issues, which again should be addressed early in the cycle. If you get the right requirements early, and grounds-up design caters to the peak load, our lives will be easier

    c. Errors cited in the logs could again be some specific issues

    I agree that getting perfect requirements early, and building a foolproof design in a rapidly changing business environment doesn't happen in the real world. However, I think it's important to push for this perfection to make scrum successful.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I will not write UT's unless I get the following done in a fast paced environment where market is very dynamic and competitive:

    1) Typically if you are developing something new where features will keep getting added, subtracted really fast. You might realize that the core components might have to change. And not just change but might also vanish and new design components might also appear.
    2) So now your product is ready to go to the market and you just deployed your app on one of the hosting providers out there and you are now facing scaling issues – your app hangs when the traffic is on peak, you get 1000s of errors in the peak traffic time, your app is a memory hog and the GC runs a little too much. All of this is happening and you are thinking of major strategic design changes to make your code light-weight and stable.
    3)Your product is now out there, does not hang too often. But you still see tons of errors in the logs.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
12,291
On SlideShare
0
From Embeds
0
Number of Embeds
49
Actions
Shares
0
Downloads
51
Comments
2
Likes
2
Embeds 0
No embeds

No notes for slide

Agile phobias

  1. 1. 10 Agile Phobias,<br />and how to conquer them…<br />GlobalLogic Agile Community Event, <br />Noida,<br />7th July, 2011<br />Viresh Suri<br />Project Manager, GlobalLogic<br />Viresh.suri@gmail.com<br />
  2. 2. Agenda<br />Agile Scrum – Revisited<br />10 Phobias, are each of these justified ??<br />It’s a Revolutionary Change<br />Loss of Accountability<br />Leads to Micromanagement<br />There is no Commitment<br />Short Cycles don’t help<br />Insufficient Design, Documentation<br />Everyone is a Generalist<br />It is Anti-Management<br />Doesn’t work will in a Distributed Environment <br />Requires Automation, which is not my core requirement<br />
  3. 3. Agile Scrum - Revisited<br />
  4. 4. Then whyfearAgile?<br />
  5. 5. Phobia # 1<br />
  6. 6. Is changing to Agile too difficult?<br />
  7. 7. Is changing to Agile too difficult?<br />
  8. 8. Phobia # 2<br />
  9. 9. Does Agile lead to lost Accountability? <br />
  10. 10. Does Agile lead to lost Accountability? <br />
  11. 11. Phobia # 3<br />
  12. 12. Is Agile Micromanagement?<br />
  13. 13. Phobia # 4<br />
  14. 14. Is there No firm date, commitment ?<br />
  15. 15.
  16. 16.
  17. 17.
  18. 18.
  19. 19. Phobia # 5<br />
  20. 20. Do Short Cycles lead to Chaos ?<br />
  21. 21. Phobia # 6<br />
  22. 22. Is Design & Documentation insufficient?<br />
  23. 23. Phobia # 7<br />
  24. 24. Should everyone be Generalist ?<br />
  25. 25. Phobia # 8<br />
  26. 26. Is Agile Anti-management ?<br />
  27. 27. Role of the Agile Manager<br />
  28. 28. Phobia # 9<br />
  29. 29. Will Agile always fail in distributed environments?<br />
  30. 30. Phobia # 10<br />
  31. 31. Is it OK to be Agile without Automation?<br />
  32. 32. Agileshouldn’t be treated like a Dogma, a system of prescribed principles<br />It is about delivering Value to the Customer<br />Discipline, Passion to Communicate is the Key<br />There will always be criticism, but judge if you’re seeing some real advantage !<br />Summary <br />
  33. 33. http://www.mountaingoatsoftware.com/system/presentation/file/69/ADP2007_WaterfallaciesAndAgilephobias.pdf<br />http://blog.adsdevshop.com/2010/03/22/3-reasons-your-manager-fears-agile-and-doesnt-need-to/<br />LinkedIn ScrumAlliance Community Post (29th June)<br />http://www.scrumalliance.org/articles/103-the-managers-role-in-agile<br />References<br />
  34. 34. Thank You !<br />viresh.suri@gmail.com<br />

×