Small Changes to Waterfall Can Bring Significant Results
You suffer from inefficiencies in workflows and organizational structure, don’t you? What if you could present an idea to improve the performance of the projects using the "waterfall methodology" in your organization, an idea that would create fewer conflicts and deliver benefits with less risk?
Sure, some may have tried this already and been slapped down or ignored. They tried to sell agile. Managers and leaders may have seen adopting new frameworks as too difficult and divisive.
Suppose though that your idea helps your organization to be a little more agile than the standard waterfall technique. Your idea can make some relatively easy adjustments without so much organizational consternation. Here are a couple of ideas…
1. Cut big projects into smaller bites. In some environments, there is a tendency to bite off more than can be chewed. A project is started, a load of requirements is documented and a plan is developed to deliver too many of those requirements in a fixed amount of time. Later, there has to be schedule extensions and budget increases.
There is a better way. Projects can select a smaller number of requirements and get started faster using a smaller budget and less overall risk. A subsequent set of requirements can be applied to a project that starts later, the schedule staggered so that overlapping similar activities (phases)
Please log in or sign up below to read the rest of the article.