Once the foreman discussed with a potential customer the renovation of a small house. The homeowner worried that the walls were tilting. The house was built of bricks, the brick walls just stood on the ground. Wooden supports were reinforced around the entire perimeter of the house, but the walls were still trying to collapse.
- Your house is in disrepair, reconstruction is required, - said the foreman. - We will stretch the power cable to power the equipment, dig a pit, make drainage, fill the foundation ... - No, no! - the owner of the house interrupted him, - I do not need a foundation pit, I need walls! House! - In this case, maybe you will think about buying a modular house? - suggested the foreman.
I spoke to a startup last month. He has a working web service that different people have been writing for several years, and now the management is thinking what to do with it. The founders told me they wanted to hire a team of a dozen developers to rewrite or modernize the app. I asked them about the user story, documentation, issue tracker, and they replied that they did not have it. They asked for a list of what I suggest they do, and I wrote this:
List the key parameters that affect sales: SLA, functionality - anything to link virtual tasks to the real world.
Define DDD contexts and create high-level documentation to discuss architecture and help new developers get comfortable with the project.
Identify system bottlenecks that are causing scaling and availability issues.
Agree on the IT team's medium-term goals with senior management.
Create a workflow based on team interaction tools such as a board, tracker, messenger, repository.
Organize the process of hiring and joining the project of new developers.
Establish monitoring and backup systems.
Make a decomposition of medium-term tasks in stages and write a timetable.
Make CI / CD.
Write an architecture change plan.
Prioritize tasks in the backlog.
IT- .
, , . . , , .
.
, : , , , , , . , , - , IT- - , . . , , - . - , . . , , , . Oracle. : , , — , , , , , , , . , -, , . Oracle corp, .
- - . , . , - . , .
- , . .
- , IT-. - , , , , .
, , , , , code review, , - . SLA - , .
. . , , . . . - , , , . . , , . , - .
, , - , MVP. , . , , . - , .
, , . - , .
(CI/CD) . , , . CI/CD - . , . . git. CI/CD - , , QA , , , . , . , , .
- , , . . . . , . , .
-, . SCRUM planning-. . - . , . , , .
, , , , , - . .
, -? , " Wordpress, 38% - ». . SAAS, outsource. , IT. , , . , , , -, , , , , .
What if you just write code without plans, tests, trackers - just call and discuss along the way? Maybe the developers will understand the problem correctly and write the correct solution, or maybe they will have to change developers several times and rewrite the application several times. The difference is in the predictability of the result.