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.
- If you are not willing to change your mindset and continue to work the same way, you did before
- If as a manager, you think people are resources
- If as a developer, you think your job is just to code by specifications
- If your organization is run by bureaucrats
- If your team is not mature enough to handle changes frequently
- If you want to deliver something fixed within a fixed time frame
- If you can’t have customer or Product Owner inputs on a regular basis
- If you have fairly straightforward requirements
- If you think you can attend an Agile Training and everything will fall in place
- If you believe in strong team hierarchy
- If you think you are better individually rather than working in a team
- If you think you can be agile enough without following the engineering best practices
- If you are not ready to tailor your process to suit your project needs
- If you think Agile is standard across organizations, across teams, across the industries
- If your scrum master doesn’t have servant leadership skills
- If you take short cuts very frequently instead of thinking a long term solution
- If you think it is still better to just honor the contract rather than listening to the customer
- If you think automation is a waste of time
- If you think you can automate everything and don’t need manual testers
- If you think it is not required to balance between people, process and tools
- If you think you can be agile without having proper code quality
- If you take so much pride in your work and doesn’t take criticism
- If you think you can implement Agile in an already affected team morale and still manage to provide better outputs
- If as a project manager, you think writing automated unit tests, following TDD are an overhead instead of an investment for the future.
- If as a project manager, you think there is nothing called as Technical Debt or worse don’t understand what it is.
- If as a developer, you think the customer is stupid
- If as a tester, you think your work is just about writing test cases and test execution and not in giving quality related feedback
- If you think DEVOPS is a fancy term used in the software development industry and you don’t need it.
- If your management expects miracle out of Agile
- 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.
A FREE guide for agile teams.
Are you running retrospectives regularly? Perhaps you run retrospectives once a week, or fortnightly. Do you feel like you could be getting more out of your retrospectives and fuelling continuous improvement in your teams? You may already find retrospectives valuable, but suspect there are ways of making them better.