Why Agile is better for getting your app or website delivered

  • Planning: The clients’ objectives usually change over time. If the developer(s) already implemented parts of the solution that need to be changed, the client will often refuse to pay more for applying this change.
  • Understanding of needs: A developer translates his understanding of the client’s specs into a computer program. Two biases are implied: the correctness of the spec provided by the client, and the understanding of this spec by the developer. If you don’t realize and solve these biases before the final delivery of the project, the complete project will NOT be released on time, and a lot of frustration and anger may arise from this situation.
  • Temporal uncertainty: Projects are various, so it’s impossible for a developer to predict the time it will take to implement the project with 100% accuracy, because some technical problems can unpredictably increase the duration of development.
Waterfall VS Agile (2m45)
Waterfall VS Agile (1m30)
  • As a user, I can backup my entire hard drive.
  • As a power user, I can specify files or folders to backup based on file size, date created and date modified.
  • As a team leader, I need to see the performance of use of my team members, so that I can have a conversation with them about their performance.
Sprints and User Stories (3m30)
  • It makes it impossible for a development team to comply to the delivery of a final product for a given deadline. Indeed, there is no such concept as “final” or “complete” in the Agile methodology; if not talking about one single particular sprint.
  • It makes it impossible for a development team to comply to a budget in advance, except the cost of a sprint. Indeed, the price of development will depend on how many sprints the client wants to “buy”.
  • It also requires the client to be available to the development team before, during and after each sprint, in order to clarify user stories and take decisions in case of unexpected events. (e.g. a user story is more complex to develop than expected)
  • No “tunnel effect” (bad surprises after months of development);
  • Value-driven delivery: user stories that bring the most value to the client are developed (or even released) first => “First release in two weeks”Thibault Jouannic);
  • Flexibility towards evolving business objectives and constraints;
  • Control: possibility to interrupt a development team early, while still having something useable developed by the team at the end of the sprint;
  • Conflicts much less likely to happen between client and developer(s);
  • Much less specification, documentation and Q&A has to be done before starting development.

--

--

--

Web software development × personal development. https://adrienjoly.com/now 🚀

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

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
Adrien Joly

Adrien Joly

Web software development × personal development. https://adrienjoly.com/now 🚀

More from Medium

Hybrid Project Management: Why to rely in a non-binary approach to a face a continuous changing…

Scrum vs Kanban : A Brief Discussion

Giving Control Back to Your Users

What is Product Manifesto and How to Build One?