What is Agile? 

Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.

The Agile Manifesto

The Agile Manifesto has 4 main values and 12 principles which lead the Agile approach to software development.

The four core values  of Agile Software Development as outlined by Agile Manifesto

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan
agile core values (1)
Photo by Anna Litviniuk | Photo  by  Juliia Osadcha | Photo by Siwat V / CC BY | Photo  by  By Aha-Soft / CC BY


The Twelve Principles of Agile Software Development

The twelve principles of Agile Software Development as outlined by Agile Manifesto

  1. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  2. Business people and developers must work together daily throughout the project.
  3. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  4. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  5. Working software is the primary measure of progress.
  6. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  7. Continuous attention to technical excellence and good design enhances agility.
  8. Simplicity–the art of maximizing the amount of work not done–is essential.
  9. The best architectures, requirements, and designs emerge from self-organizing teams.
  10. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.



Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Why should you used Agile software development for your MVP?

Agile takes into consideration that product requirements change during the software development.

Agile is really important in creating your MVP because this can help you know what are the things that you need to prioritize in order for your software project become successful and will also help you get immediate and quick user feedbacks or comments.  

In building software product, one big characteristic that push around the choice of a life cycle method is the clarity and security of software product requirements. Occurring changes in these requirements- after the project started- can delay your progress. In these cases, you must pick the iterative approach because it can be an advantage to accommodate new requirements even after the software project has been started.

A well managed group of end users who can greatly influence on the software project can help your team know the essential requirements and manage changes together with your software dev team. This means that you can achieve your project requirements stability and allow you to use the waterfall method- or the traditional method. But, if your end users are allocated, you must really have a broad range of requirements. You cannot choose one feature over another until the end users use the system and start giving comment. Since Agile assumes that product requirements change, the project can handle multiple user requirements.


The agile methodology is a great factor for software development team to do their software projects work faster and more effective. But on the other hand,there is a dark side to agile approaches. They are usually caused by human mistakes. And there are different strategies you need to know in order to fix them.  

  • Daily stand up meetings- having a meeting could take time which could affect the individual work role. So it must be done effectively in order not to waste your time and also the time of your team.
  • Frequent change requests- several changes could affect the projects that you are doing. It can also delay on releasing project.
  • Non-professional influence on the product- it talks about your active user engagement, and it can make your product unfavorable for the user. You must accept feedbacks of users but trust your experts in making your final decision.
  • Frequent delivery- means that your working features for your customers or users as quickly as possible. This will ensure that the software dev team will receive information and feedback on important changes.  



We understand Agile. We understand how Agile can help make or break your startup. At Bootyard, we’ve developing Ruby on Rails applications since 2011 using Kanban. If you are currently building your MVP for your startup, we’d love to have dialogue with you on how Agile can help you move forward efficiently. Shoot us an email at info@bootyard.com.