Review of the 4th chapter
Normally people are not used to plan because they think is a waste of time and make stress knowing how much they must do to make the project run, but normally is because they don’t know how to plan.
Last post I didn’t explain in short words what was upstream and downstream but here we go, upstream is the early part of the project, requirements, development and architecture and downstream is the later part of the project that consist of construction and system testing so is much cheaper make a change or fix a defect in the upstream than the downstream.
The thing is, we must plan because the average project spends 80 percent of the time on unplanned rework that is fixing or changing things that wouldn’t have happened if we had planned at the beginning.
Let start with specific features of a well-planned project. First we got a Software Development Plan this maps the course for the project, second the project estimates that leads to budgeting, staffing and scheduling the project, third revised estimates, check if what is going to be spent and how much the project will earn, after that is a quality assurance plan that will not succumb to a costly project and will be at perfect conditions, finally a staged delivery plan how the project will be constructed.
The first part of the project is essential because determines if the project is a “go/no go” if it’s correctly planned, the project will show you if is convenient per time and develop of the group task or not, so this part is very important that the client, user, customer is present so he can validate every point or any change before the project starts and check if the time/cost he will pay is worth the possible outcome.
In this chapter I learned that develop a plan and be aware of different situations that could be against the programmer (cost, time, impossible projects) is essential to make a quality software, that would be all for now, until the next one.