5 Reasons to choose Agile

  1. FINANCE BENEFITS Every one wants to get to the end of the shining path with every new project they’re on and reducing risks is one of the keys to do so. Remember we are estimating something that is not even in a blue print so chances are you will go over your budget before the project is complete. Why is Agile the way to go? In the traditional model (Waterfall) clients invest their money for months, even years, without seeing the final product until it is finished and when its done we find out its not exactly what they wanted or the market requirements have changed and this product is obsolete at this point. So Agile provides us with a Sales Argument. Because Agile allows us to deliver something of value every two or three weeks we don’t have to wait for months or years to deliver features. We reduce risk and increase value in every delivery, ( 2 / 3 week sprints ) besides the client gets a ROI ( Return on Investment ) and doesn’t have to wait until the project is completely and delivered.
  2. VALUE INCREASE We can understand business value as the relevant items needed to achieve business objective. Remember Pareto’s ? When we talk about value items (PBI) we talk about this 20% responsable over the 80% of all business value inside our own final product so we have to focus on that during the whole process. Of course dividing the product in several sprints is not enough, we have to do it the right way so every delivery must contain the right amount of value for the final user. This is what we call Minimal Market Feature (MMF) which represents the smallest amount of functionality with a market value.
  • Provides concrete evidence that your code works.
  • Feedback in seconds/minutes.
  • Like it or not almost nobody reads documentation, we prefer reading working code in this case sample tested working pieces of code.
  • Less time spent debugging.
  • Get closer to the problem quickly.
  • Ensures changes and new code don’t break the existing code.
  • Simplicity; many bug comes from complexity.
  • Cuts time to Market; code is usually much shorter.
  • Makes developers accountable.
  • Daily stand-up: Every day for just 15 minutes allow developers to share a problem and show what they are involved and causes the load decreases effectively ; they make sure they make progress every day ; They discover that their co-workers actually have useful input.
  • Retrospective: This is the time to give the team an opportunity to share lessons learned showing the wrong and the right steps taken in the last sprint. If we want to improve our future sprint cycles this is the moment to improve team’s development process.




Engineering | Agile | Climbing | Travelling

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Quick start guide — Alpha launch of Ape Gang’s metaverse

My First Ruby on Rails App

Working with Modules in Python — Part 2 (Packages)

Which Is Better: Bluehost or GoDaddy Hosting?

Raspberry Pi Pico (Troubleshooting)

Depreciation Calculator in Visual Basic

CS373 Spring 2021: Tim Nguyen

7 Effective Skills All Software Engineers Should Know

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Nicolas Quartieri

Nicolas Quartieri

Engineering | Agile | Climbing | Travelling

More from Medium

Role of a SAFe Scrum Master: Things to know.

Prescriptive, Top-Down “Agile Transformation” is Wasteful Yak-Shaving

A yak standing in a plain while lifting its head up and apparently making some vocalization

Scrum: The lifecycle of a Sprint

Agile SDLC — Software Development Life Cycle #2