Bootcamp

From idea to product, one lesson at a time. To submit your story: https://tinyurl.com/bootspub1

Follow publication

Software Development Model — Iterative Development

Jayendra More
Bootcamp
Published in
3 min readSep 2, 2023

--

The Software Development Life Cycle (SDLC) is like a roadmap for creating software. It breaks down the process into stages and assigns tasks to respective people. This helps keep things organized and within a set schedule and on budget. There are several types of development models, and we’ll focus on Iterative Development in this article.

Iterative
Photo by Tim Johnson on Unsplash

Iterative Model

The iterative life cycle model avoids starting with a complete set of requirements. Instead, it commences by specifying and creating a portion of the software. This section is reviewed to uncover additional needs. This loop is repeated, generating a new software version with each cycle of the model.

For example:

Iterative Eiffel Tower
Source: Google
  • In iterative work, we make a basic version first, then make it better in the next round, and keep improving in each round until it’s done
  • Imagine drawing: first, a rough sketch, then cleaner lines, and finally, adding finishing touches
  • Similarly, in the iterative model, the entire product is built gradually, step by step

Diagram of the Iterative Model

Iterative Model

Advantages of the Iterative Model

  • In the iterative model, we start with a broad application design before building the actual product. We then create a preliminary version and evolve the design based on what’s built
  • In this approach, the product is developed and refined in steps. This helps catch defects early and prevents them from spreading
  • With the iterative model, we gather dependable user feedback. By sharing sketches and blueprints, we ask users to envision how the product will function
  • Documentation takes a back seat in the iterative model, allowing more time for designing

Disadvantages of the Iterative Model

  • Each phase in an iteration is rigid without overlaps
  • There might be costly system architecture or design problems as not all requirements are collected upfront for the entire project duration

When to Use the Iterative Model

  • Complete system requirements are well-defined and understood
  • Suitable for large projects
  • While major requirements are set, some details can change over time

Read the article on How SDLC Works?

I would love to hear your thoughts on this topic in the comments. If you enjoyed this article, please Follow me here on Medium for more stories on similar topics and other Product Management-related subjects.

About Me Jayendra More
Link to About Me Blog Here

If you are hungry for insightful and thought-provoking content? Look no further! Subscribe to my Medium Blog and get regular updates on the latest articles and musings.

I am always open to having a healthy conversation over a cup of coffee.

Let’s connect on LinkedIn! We can also connect on Twitter — I’m always up for a chat. Whether you have questions, need help, or just want to say hi, feel free to reach out!

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

Bootcamp
Bootcamp

Published in Bootcamp

From idea to product, one lesson at a time. To submit your story: https://tinyurl.com/bootspub1

Jayendra More
Jayendra More

Written by Jayendra More

Product Lead @ PlayerzPot. Have helped the company to grow the user base from 0 to 15 mil. Connect with me on Twitter, https://twitter.com/more_jayendra

No responses yet

Write a response