Requirement definition document was the basics of the basics in program development. The requirement definition had to be organized properly in order to decide how to develop the requirements, how big the scale of the service will be, how they will decide on hardware specs, etc.
And currently, YongHo was participating in the meeting.
“Yes, that’s correct. Currently, the service provided by Shinseki is receiving 8 photographs in total. That means that one has to take 8 pictures while manipulating the screen. How inconvenient is this?”
However, image processing was a different field. YongHo didn’t even begin to grasp whether it will be possible or not. Dave and James were no different.
“Won’t it be difficult to process videos? Why don’t we just go in a direction where we can take all photos that would be processed, at once…….”
YongHo asked Brad who was sitting next to him.
“Yes… I did put out a notice but it’s not easy.”
In order for a user to feel an online space as realistic as possible, they needed a specialist in the image processing field, but it wasn’t easy to find such a person.
In the end, Kenneth also had no choice but to go to the next part. There were still over 100 requirements to talk about.
The biggest worry that YongHo had while he was in the conference room was when the meeting would end.
YongHo was in a position where he should listen. Moreover, the one called Kenneth, who took on the role of the SA, seemed older than YongHo.
“I will share the next parts via JIRA so please check.”
And when an issue occurs in the project, then an e-mail will be sent to all the registered people. As a program developed by a company in the US, recently, it was used a lot worldwide.
“Huh?”
“Aren’t you going?”
If it was Korea, the meeting would not have ended there.
After the meeting ended, YongHo came outside to cool his head. When he sat down on the bench and talked about what happened in Korea to his friends and colleagues, Jessie muttered as if it was absurd.
“I think they spent about more than half of the day in meetings……”
After being called to various meetings all day, they started doing their own work at night. It was a structure with unavoidable overtime work.
“The first meeting was only long since it was the overall briefing… From now on, the rest will be mostly done through JIRA. Or, it will end quickly like today.”
YongHo sighed in relief at the fact that he didn’t need to participate in long term ‘marathon’ meetings.
Jessie, who came back to the office, was sticking post-its on the wall. As he had already experienced it in Shinseki, YongHo also knew what she was doing.
YongHo was skeptical. He thought that this methodology will be ignored without being used due to being chased by the schedule.
“YongHo!”
“I got work, YongHo needs to start too!”
Dave spoke while waving the post-it on his hand. In the small post-it there were a lot of work written on it.
Service related schema design and writing generation script.
YongHo, who confirmed the contents of the post-it that Dave held, approached Jessie.
Vertically, there were ‘things to be done’, ‘in progress’, ‘completed’ written and on horizontally there was the names of the people in charge of them
“This project will progress according to something called Scrum of Agile development methodology.”
YongHo felt like he had heard of it before. However, he didn’t know clearly how it worked.
YongHo gulped dry saliva after checking the post-it that Jessie gave him
Deciding and designing the structure of each stack in the software.
“How long will it take?”
“Tw, two or three days will be fine?”
Although Dave was on his side, not all the members of the company were on Dave’s side.
And so, the pressure that he needed to do something faster and preciser than anyone was dominating YongHo’s thoughts.
“Really? I thought it would at least take 1 week. You sure are different, YongHo.”
“Didn’t I say so? That YongHo’s different.”
‘*Sigh*…How do I request now?’
The only thing he did from start to finish was developing a small function for an app.
YongHo first found his way to the front of Jeff’s company. The best method to solve this problem in 2 days was not going to the library but coming here – this was the answer he arrived at.
“Why should I? I’m really busy.”
“Didn’t that end with the algorithm tutoring?”
Jessie looked at YongHo with a doubtful gaze. He had already seen through YongHo’s ability to a certain extent through the algorithm tutoring.
Algorithm required an exceptional brain. One had to solve mathematical problems with a fast-calculating head.
As he saw that process while tutoring him, it was a mystery for Jeff that YongHo had solved a problem relating to performance.
“You don’t have anything to lose.”
YongHo felt a sudden surge of anger when he heard Jeff’s words. However, he was in the inferior position of the requester. He couldn’t do as he wanted.
“Jeff, why don’t you let him try? Didn’t you say that there was an error in the screen that you made as a prototype last time?”
“I made some libraries here but due to an error, I can’t use it. Since it had low priority, I had left it for later. If you solve this, then I will help or advise you in design as you said.”
Even without that, he was living while minimizing sleep. He didn’t think he would understand anything even if he read.
While checking the bug window which appeared next to the screen that Jeff showed him, YongHo spoke.
“Which computer should I use?”
“About 20 minutes?”
To solve this, he thought he would have to edit the libraries themselves so he had left it for later.
“Then use my computer. I will leave for a moment.”
When Jeff left, YongHo took off the bag he was wearing and took off his coat and hung it on the bag.
“Then here I go!”
YongHo quickly started typing on the keyboard. Jeff wanted to go outside to get some wind, but he couldn’t.
Not even 20 minutes had passed. When Jeff, who came back from the toilet, was about to put on his coat, YongHo called him saying the problem was fixed.