01:58
Faizan
Agile is mainstream. Agile isn't flawless. Agile works, that's a fact - although it receives rather polar opinions in the world of software development. Sure it's way closer to good than bad. There are lots of successful projects and rapidly growing startups who owe their success to making their mobile products via agile. Meanwhile everything in this world has its strengths and weaknesses. Everything serves its purposes. You obviously can't write with a hammer and drive nails with a pen.
But how should you know whether agile development is right for you? How do you know that it's an agile team that suits best for making your product? Just take a look at the 12 main principles of agile - the more of them apply to your vision and business plans, the more agile approach suits you. Here is the easiest way to find it out.
The 12 Principles Of Agile:
1. Client satisfaction by rapid delivery of useful software.
You have deadlines. You don't want to wait until someone rolls out a product with the same idea as yours. You need to act promptly and give working software to end users as soon as possible. Same with generating ROI for further improvement of the product - and further revenues.
2. Welcome changing requirements, even late in development.
This brings competitive edge to the resulting product. Returning to previous work and having to alter it gets a bit frustrating, but it has to pay off as vital relevance.
3. Working software is delivered frequently.
Weeks rather than months - commonly 2-4 weeks. It allows to guide and alter the direction of the project and facilitates Principle #2. At the same time you receive frequent insights into what's been achieved over each iteration.
4. Working software is the principal measure of progress.
Since agile receives many accusations of rolling out half-baked software, many agile software companies accentuate quality as the priority par excellence. A quality that works is just what you need. But to achieve it, you'll have to accept Principles #5 and #6 (at least, the latter), and never cut the costs of quality assurance.
5. Face-to-face conversation is the best form of communication.
Oops, here we've come to contradictions with the idea of outsourcing. Indeed, you can assemble an in-house IT department. It will take time to find the human resources and provide them with equipment. It will cost more - you'll have to provide salaries no matter if the team is busy or not. Otherwise, you may outsource the project. That's not face-to-face, but it works faster and cheaper, as far as experience goes.
6. Close, daily cooperation between the client and the development team.
But how should you know whether agile development is right for you? How do you know that it's an agile team that suits best for making your product? Just take a look at the 12 main principles of agile - the more of them apply to your vision and business plans, the more agile approach suits you. Here is the easiest way to find it out.
The 12 Principles Of Agile:
1. Client satisfaction by rapid delivery of useful software.
You have deadlines. You don't want to wait until someone rolls out a product with the same idea as yours. You need to act promptly and give working software to end users as soon as possible. Same with generating ROI for further improvement of the product - and further revenues.
2. Welcome changing requirements, even late in development.
This brings competitive edge to the resulting product. Returning to previous work and having to alter it gets a bit frustrating, but it has to pay off as vital relevance.
3. Working software is delivered frequently.
Weeks rather than months - commonly 2-4 weeks. It allows to guide and alter the direction of the project and facilitates Principle #2. At the same time you receive frequent insights into what's been achieved over each iteration.
4. Working software is the principal measure of progress.
Since agile receives many accusations of rolling out half-baked software, many agile software companies accentuate quality as the priority par excellence. A quality that works is just what you need. But to achieve it, you'll have to accept Principles #5 and #6 (at least, the latter), and never cut the costs of quality assurance.
5. Face-to-face conversation is the best form of communication.
Oops, here we've come to contradictions with the idea of outsourcing. Indeed, you can assemble an in-house IT department. It will take time to find the human resources and provide them with equipment. It will cost more - you'll have to provide salaries no matter if the team is busy or not. Otherwise, you may outsource the project. That's not face-to-face, but it works faster and cheaper, as far as experience goes.
6. Close, daily cooperation between the client and the development team.
Posted in: business
