A full remote engineer is very good. You can work anywhere, so while traveling abroad, you can work at any time.
Supporting this wonderful freedom is the trust of our customers.
The full-remote job is judged only by products because they can not see the process of your job.
Delivering value to customers, being trusted by them, and establishing good relationships are necessary to survive as a full remote engineer.
How can we deliver value, be trusted, and have a good relationship with customers?
I think there are many elements, but I think the following three things are important.
- Shows your result every week
- High quality
- Responds quickly to feedback
Agile development methods can respond to the above three in the following way.
- Start development from top priority story
- Test-driven development
- Refactoring Regularly
In order to explain each in detail, I would like to explain how to proceed with agile development with the following orders.
Order: The owner of the used bookstore requests you to develop a web application that can manage inventory and also allow customers to check the inventory . The owner can register the purchased book, and he wants to know the number of stocks immediately. His Customers can visit the site to find out what books are in stock, how much they are for sale, and search by title. I think that it is best if you can see other products that sell well and suggest products recommended from the browsing history.
You listened to this owner's request and decided to develop all the features. You will tell the owner that it will take 3 months for development, and you will start working immediately.
The owner cannot see how you work. So if you don't get the work done for a month or two, he will be anxious, and say, "How is it going?"
You would answer, "I have done detailed design, set up DB, wrote Model and Controller. I also tested them properly. Next, I will write the View and complete it. I can do it in one month." You will show him the source code.
But He doesn't really know if it's really nearing completion, because he can't see the work that is moving. It can not be said that there is a trusting relationship between you and him.
What do you do with Agile? Determine the top priority story and develop from there .
The story is, in a nutshell, the "feature that works end-to-end" .
The top story is the most important value story (feature) in the list of stories.
In this example, “I can register books and view inventory in a list” is the core value. You can not do anything without this.
In Agile we start to create products with only this feature .
Because the functions are limited to one, you can do it in a week.
Show the owner a product that will move in a week. The owner can confirm that the book can be registered, so he must be glad to know the progress, rather than looking at the source code.
In the next week, We will implement the next important story and let him see the product that is moving next week . The owner can see the product being added features each week, so he can leave work to you with great peace of mind.
The owner is happy now to confirm that the book can be registered, but he noticed that registering a blank book title would cause a bug. There are many other bugs, such as being able to put text in the price, or being double registered if he clicks twice. You use the whole week to write tests and fix bugs, but nothing features have been added since a week ago. You will lose the owner's trust.
No matter how quickly you deliver a product that moves, products of low quality will lose the trust of customers .
What do you do with Agile? Agile development is basically done with test-driven development .
Test-driven development is a method that proceeds from development by writing from test and implementing it so that the test passes.
The important thing is to do a minimal implementation for passing the tests you are writing.
Test-driven development can ensure the quality of the written test, and can also avoid excessive-quality (too much implementation).
Because test-driven development is deep, I would like you to study other materials by all means.
Whenever you see a product that moves once a week, be sure to get feedback.
When I try to touch moving things, there are more and more requests that did not appear when discussing on the desk .
For example, "Because there are more than 100 books in a month, it is better to register as easy as possible" or "If the link to the Amazon is also attached, the price of our house may seem more reasonable".
All these feedbacks are stories. Put in the story list, we will develop from the highest priority story.
The more feedback there is, that is, more corrections .
Refactoring is essential for the agile handling of feature additions and modifications.
When is the best time of refactoring? It is always.
To be precise, while doing test-driven development, we always take time to refactor when we pass the test .
It is this as a flow.
Test-> Implementation-> Refactoring
Repeat this to create a product, and the product will be resistant to change.
When the owner sees the request he has given immediately added, his confidence in you will grow. So be sure to always have a codebase that can quickly change to customer's needs.
The word agile development is the buzzword, but I think that there are few people who are studying to what kind of method and how to proceed specifically.
I think you can see how Agile is better at delivering value through this example.
There are a lot of things that have not been reported this time, so please search for the word Agile Development or Scrum Development and get the information.
Well then, have a good engineer life.
PS. I'm searching remote job. I specialize in iOS app (swift), Web app (React, Vue), API development (Python, Typescript, Java). My strength is in delivering value with agility.