Also, you don’t have to spend time training new members, as they can familiarize themselves with the project by reading the documentation.īecause everyone knows in advance what they'll work on, they can be assigned to multiple projects simultaneously. With an extensive level of documentation, knowledge won't get lost if someone leaves. As a result, Waterfall is risky.īecause you can't return to a previous activity, you're forced to create comprehensive documentation from the beginning, listing all the requirements you can think of. You can never be 100% sure how much time you'll need on something or how much you'll spend debugging. The problem with using the Waterfall methodology on a software project is that planning is tricky in software development. This is why Waterfall project planning is the most important thing in these projects: if you don’t plan right, a phase will be late and push every subsequent phase, thus putting the whole project over the deadline. Usually, 20–40% of the time is spent on requirements and design, 30–40% on coding, and the rest on testing and operations.Īctivities on Waterfall projects have to happen in the exact order, and one set of activities can't start before the previous one ends. Once you put all the activities on a Gantt chart, you get something that looks like the slopes of a waterfall, hence the name.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |