--Originally published at Blog Oliver
I dint like this chapter so much because its not related to the main story, we just see Webster, Kenoros and Belinda talking about Kenoros grade of each project. This grade is bases on the amount of time dedicated to the designing of the project. When we talk about design we refer to dividing the project into parts or modules not talking about UI, color, fonts, etc. We see lower grades in projects with more people. Trying to find an explanation Webster asks to Kenoros about this situation.
We learn that projects with a lot of people tend to write a political document and call it design. We just needs a few people for designing the project, you cant put most of the team in stan by until designing team finishes their job. Thats why this stage is skipped in large teams. But thats a big mistake, this is one of the most critical parts in creating software, its like the foundations and steps we need to follow in order to complete our job.
Belinda once again saves the day an explains how we need to divide the project in the design stage and what advices we can follow. First of all we need to divide the project in chunks of almost the same size this way we have a proportional distribution of all the work needed. Also this chunks must make sense and wee need to order them in a the correct way. We can divide big groups into smaller ones and assign a chunk to each small team. But all teams must know what the others have done and what are they woking on. This way we dont lose time explaining everything to each team.
In the end we cant skip designing. A good design can save Continue reading "The most important part of software development"