You can involve the relevant stakeholders in this process. Room for reviews after every phaseĬlearly defined and demarcated phases allow you to review the project after every phase. With its origin in the construction and manufacturing industries, the waterfall methodology is naturally rigid here. Requirement changes late in the cycle can be very expensive. Change management processes might also mandate a cost-benefit analysis before changing requirements. After you finalize the requirements, you can change them only if you have strong reasons. Waterfall projects typically implement stringent change management processes. Rigidity in terms of freezing the requirements You can define different resource requirements for this task then. Similarly, you can include the “post-production deployment support” phase mentioned above within the warranty support phase itself. You can add it to the “coding” phase if you want. Take the example of the code review phase mentioned above. You can define the tasks based on the characteristics of your industry and projects. However, the methodology doesn’t dictate the tasks within a phase. The waterfall methodology mandates clearly defined and demarcated phases. Flexibility in terms of the tasks in the phases While the warranty phase still requires the availability of the development team, you need less time from them. Once you have passed this phase successfully, you can start the warranty support phase. Such a period needs extra support from the development team. This helps if you expect too many support tickets right after the system goes live. You can have a post-production deployment support phase between the deployment and warranty support phases. Let’s take another example of this flexibility. You can have a distinct phase called “code review” between the coding and testing phases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |