• Microsoft Teams, SharePoint and 365 Implementation Experts.
Capitol Presence LogoCapitol Presence LogoCapitol Presence LogoCapitol Presence Logo
  • Services
  • Who We Help
    • Government
    • Commercial
  • Tools
  • Contact
0Book a Call
Agile Project Management: EPICS
January 2, 2018
10 Reasons you Should be Using Agile
January 8, 2018

What Makes Waterfall Software Development Model Fail in Many Ways?

Published by Capitol Presence on January 5, 2018
Categories
  • Blog
Tags
  • #TakeToTheCloud
  • Agile
  • Agile Development
  • Agile Methodology
  • AI
  • Azure
  • bricks
  • Cloud
  • Cloud Computing
  • Cloud Consulting
  • Cloud Solutions
  • Data & Analytics
  • Data Management
  • EPICS
  • goals
  • government
  • Optimize
  • Security
  • Take to the Cloud
  • Tech
  • Technology
  • telework
  • waterfall

Portrait of five businesspeople looking at camera with female leader in front

Studies have shown that in over 80% of the investigated and failed software projects, the usage of the Waterfall methodology was one of the key factors of failure. But why?

Phases in the Classical Waterfall Software Development Model

As shown in the image, when deploying the waterfall methodology there is a strict sequential chain of the different project phases. A previous phase has to be completed before starting the next phase. Going back is in most cases difficult, costly, frustrating to the team and time consuming.

The project timeline is planned at the start. A releasable product is delivered only at the end of the project timeline. If one phase is delayed all other phases are also delayed.

To avoid this users of the waterfall methodology normally try to anticipate all possibilities beforehand. This means that in one of the earliest phases of the project they try to define all requirements as fine grained and complete as possible. However, requirement definition in such an early phase of the project is often very difficult and therefore many requirements change (or should change) throughout the project. Studies have shown that in larger and complex projects about 60% of the initial requirements are changed throughout the project. Other requirements are implemented as defined but are not really needed by the customer and consume valuable time that could have been better used to implement functionality with a higher added value for the customer.

The separation into different project phases force users to estimate each phase separately. The problem is that most of these phases are normally not separate. They are working together and in parallel.

The waterfall approach for developing software can be used for implementing small and simple projects. But for bigger and more complex projects it can be said that this approach is highly risky, often more costly and generally less efficient than Scrum Project Management Framework.


Source: Scrum Institute

Original Article

Share
0
Capitol Presence
Capitol Presence

Related posts

January 3, 2021

Cloud computing trends in 2021


Read more
December 27, 2020

6 technologies that changed the way we work


Read more
Virtual Desktop
December 13, 2020

Top Cloud Trends to Watch for 2021


Read more

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Capitol Presence Logo

Capitol Presence is a Woman-Owned Small Business (EDWOSB) based in Tysons Corner, VA. We are an Agile Development and Solutions agency that specializes in customer-driven business solutions, born in the cloud. We focus on helping organizations communicate more effectively and work more efficiently together, to complete their mission.

Navigation

  • Tools
  • Services
  • Who We Are
  • Contact
  • Shop
  • Responding to COVID-19
  • Microsoft Office 365
  • Our Team

Industries & Information

  • Commercial
  • Federal Government
  • Employee Portal
  • Partner Portal
  • Remote Resources
  • Privacy Policy

Let’s Simplify Your Business

Book a Call
© 2020 Capitol Presence Consulting Group LLC. All Rights Reserved. Hosted on our Olympus Cloud by AWS