Generally, it is best to plan, develop and release in small chunks for the following reasons:
- You’d want to get the new features out ASAP into the hands of your users
- It is faster and easier to test small chunks compared to big chunks
- Big projects will take forever to release and they usually take 2–4 times longer than anticipated because of complications that almost always arise
- You’d want to start earning sales on what you have developed sooner than later to fund the on-going development
- Get feedback from users sooner than later about the usefulness of features developed
- It easier to keep the team focused on small projects vs a big one
- And more
Three books that really helped us understand this concept are the following books:
- Getting Real by 37 signals
This is a free book and you can download the PDF here. This book is by
2. The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim, George Spafford, and Kevin Behr
3. The Lean Startup by Eri Ries
I suggest reading Gettig Real first. It shows you the way to decide which features to develop and which ones to NOT develop. We hurt ourselves in our software development by developing too many features that made our software bulky, fragile and hard to test. We also developed too many features that were not valued by users!
I would recommend reading these books before or during the development of your software to save your self a ton of headache and time.
Hope this helps and good luck
To your massive success
Mostafa Hosseini
PS: Please share and upvote, if you find this useful
