Rajaraman Raghuraman

About Rajaraman Raghuraman

Rajaraman Raghuraman is a highly passionate software craftsman with 8+ years of experience in the IT industry. He is also the owner of AgileDevTest Blog (http://agiledevtest.blogspot.com) and author of an Ebook "Programmer's Motivation for Beginners" which is available at http://programmersmotivation.com.

Agile is not for you IF

In my previous posts I have tried to put forward my points on What an Agile Project needs for success, 11 areas an Agile Project Manager needs to focus o… and Scrum meeting. Are you kidding me?

In this post I am going to describe in my own words and experiences that Agile is not for you if you are among the following category.
 
 
 
 
 

  1. If you are not willing to change your mindset and continue to work the same way, you did before
  2. If as a manager, you think people are resources
  3. If as a developer, you think your job is just to code by specifications
  4. If your organization is run by bureaucrats
  5. If your team is not mature enough to handle changes frequently
  6. If you want to deliver something fixed within a fixed time frame
  7. If you can’t have customer or Product Owner inputs on a regular basis
  8. If you have fairly straightforward requirements

    Image Courtesy: utest blog

    Image Courtesy: utest blog

  9. If you think you can attend an Agile Training and everything will fall in place
  10. If you believe in strong team hierarchy
  11. If you think you are better individually rather than working in a team
  12. If you think you can be agile enough without following the engineering best practices
  13. If you are not ready to tailor your process to suit your project needs
  14. If you think Agile is standard across organizations, across teams, across the industries
  15. If your scrum master doesn’t have servant leadership skills
  16. If you take short cuts very frequently instead of thinking a long term solution
  17. If you think it is still better to just honor the contract rather than listening to the customer
  18. If you think automation is a waste of time
  19. If you think you can automate everything and don’t need manual testers
  20. If you think it is not required to balance between people, process and tools
  21. If you think you can be agile without having proper code quality
  22. If you take so much pride in your work and doesn’t take criticism
  23. If you think you can implement Agile in an already affected team morale and still manage to provide better outputs
  24. If as a project manager, you think writing automated unit tests, following TDD are an overhead instead of an investment for the future.
  25. If as a project manager, you think there is nothing called as Technical Debt or worse don’t understand what it is.
  26. If as a developer, you think the customer is stupid
  27. If as a tester, you think your work is just about writing test cases and test execution and not in giving quality related feedback
  28. If you think DEVOPS is a fancy term used in the software development industry and you don’t need it.
  29. If your management expects miracle out of Agile
  30. If your business requirements are fairly static
    Do you think there are other areas that I might have missed out or are there any points that you do not agree with?  Please feel free to shoot those out in the comments below.

 

Reference: Agile is not for you IF from our JCG partner Rajaraman Raghuraman at the Developers And Testers – A New Agile World blog.
Related Whitepaper:

Applying Agile Principles To The Development of Smarter Products

Agile development has become a cornerstone of most software development organizations.

Marked by iterative processes that deliver incremental value over time, agile development has enabled organizations to manage software complexity more effectively and to improve quality and time to market compared with previous development processes.

Get it Now!  

2 Responses to "Agile is not for you IF"

  1. I like this one: “12.If you think you can be agile enough without following the engineering best practices”.

Leave a Reply


5 − = two



Java Code Geeks and all content copyright © 2010-2014, Exelixis Media Ltd | Terms of Use
All trademarks and registered trademarks appearing on Java Code Geeks are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries.
Java Code Geeks is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.

Sign up for our Newsletter

15,153 insiders are already enjoying weekly updates and complimentary whitepapers! Join them now to gain exclusive access to the latest news in the Java world, as well as insights about Android, Scala, Groovy and other related technologies.

As an extra bonus, by joining you will get our brand new e-books, published by Java Code Geeks and their JCG partners for your reading pleasure! Enter your info and stay on top of things,

  • Fresh trends
  • Cases and examples
  • Research and insights
  • Two complimentary e-books