Feedforce Inc. - Development Environment

Transcript

1. 2020 © Feedforce Inc. 2020 © Feedforce Inc. Updated: June 2021 Development Environment
2. 2020 © Feedforce Inc. 1. Team Overview What kind of team is it? 2. Development Process How the development proceeds 3. Languages and Tools What the engineers and designers are using 4. Initiatives to improve the team How we are doing kaizen 2 Contents
3. 2020 © Feedforce Inc. Team Overview 3
4. 2020 © Feedforce Inc. Product Introduction 4 There are three products that have UI. The way to proceed with development is left to each team. Data Feed Advertising Management Tools Social Login Data Feed Management Tools Data Feed Operation Data Feed Advertising Management
5. 2020 © Feedforce Inc. Member Composition Back-end Implement and optimize server-side applications Front-end Implement and optimize Front-end applications Product Manager Decide where we're going and what we're going to make Customer Support Supporting customer operations Design Optimize contact with customers Infrastructure Supporting system performance Sales Make proposals that are close to the customer Marketing Convey the value of the product Business Development 5 Each product has business and development members. We share information and support each other as we proceed with the project.
6. 2020 © Feedforce Inc. Connection of Occupational Axes 6 Designer Back-end Infrastructure (4 people) (12 people) (3 people) We share information and consult with each other about development and team management across products. Front-end (7 people) Some people are full-stack, working across occupations. As of 2021/02
7. 2020 © Feedforce Inc. Development Process 7
8. 2020 © Feedforce Inc. Overall Development Flow 8 Planning and Research Design Implementa tion Review Release PdM Front-end and Back-end Design Requirement definition Marketing Operation PdM Business Team Design Discuss in teams
9. 2020 © Feedforce Inc. Iteration Flow 9 Work with high value to the product is set as Priority 1 (P1) and shared with the team as the goal of this iteration. Smaller tasks and improvements are assigned as Priority 2 (P2), and each team member works on them independently. Planning Iteration Review planning Design Impleme ntation Test release 1 iteration (1 to 2 weeks) Iteration Development Sharing Progress and Problems Looking back Use KPT and other methods to improve the team on a regular basis. Align priorities, man-hours, and methods of collaboration. Break up the work into smaller pieces and release it once or twice a week. Check the progress and difficulties of P1 and P2 in the morning meeting. Share the tangible results through demonstrations and other means.
10. 2020 © Feedforce Inc. Planning and Requirements Definition 10 Design and implementation Deepen understanding of users and the environment surrounding them through interviews and specification research. Examine Based on the survey, identify the real issues of the users. Connect the value that should be provided and the reasons for it to clarify the overall picture. Summarize Come up with ideas to solve users' problems and turn them into concrete prototypes. Prepare for the fireplace Evaluate and validate ideas in a variety of ways, including team discussions and feedback from users after the beta release. Evaluation and verification Design the screens and APIs to realize the ideas, and actually give them shape. In order to deliver value to users quickly and to facilitate team discussions, we formulate ideas to solve user issues and discuss them with the team based on the "springboard for discussion". Determine topics to be addressed based on user requests and PdM ideas. Aim at Go back and forth with the team to discuss and refine the idea.
11. 2020 © Feedforce Inc. Surveys (User hearings) 11 When the plan has been solidified to some extent, verify needs and issues as necessary. Recently, it has been conducted via ZOOM, which makes it easy for engineers to participate.
12. 2020 © Feedforce Inc. Design 12 In order to reach the goal of the iteration, each job has its own subdivision of work. Each profession will work together to achieve the goal. Front-end PdM Back-end Design
13. 2020 © Feedforce Inc. Implementation and review 13 Mob production Two or more people will implement the system while talking to each other to share designs, support implementation, and provide feedback in a speedy manner. In phases where it is more efficient to divide the work, we will implement it individually. Review We check the visibility and behavior to the customer, and the correctness of the design and implementation. The PdM will also review any areas that affect the customer.
14. 2020 © Feedforce Inc. Release 14 Effect Measurement Check the usage rate, withdrawal rate, and operation feel, and use this as a reference for the next planning and improvement. If necessary, we will interview companies about their effectiveness figures and issues using the functions. Unveiling party There is a meeting where the whole team can watch the business members operate the system with a question and answer session. While sharing the functions, we can identify points for improvement. People from other teams may also come to observe.
15. 2020 © Feedforce Inc. Languages and Tools 15
16. 2020 © Feedforce Inc. Languages and Tools 16
17. 2020 © Feedforce Inc. Efforts to improve the team 17
18. 2020 © Feedforce Inc. Action Guidelines 18 Engineer's Principles It is a set of concrete action guidelines for embodying the values. We want to recognize and celebrate engineers according to various axes. We want to reduce mismatches in hiring by clearly defining the "culture of engineers”. It was created with this in mind.
19. 2020 © Feedforce Inc. Periodic review of how individuals and teams work. 19 KPT At regular weekly MTGs and upon completion of the project, we reflect on what went well and what didn't, and identify measures for improvement. Soundness Indicators Every three months, we review the severity of the code, system maintenance and performance, and overtime hours, and share our temperature with each other. 1on1 On a bi-weekly or monthly basis, we take an objective look at our work, career, and personal lives. The manager is not an evaluator, but a companion.
20. 2020 © Feedforce Inc. Eliminating Technical Debt and Focusing on Sustainability 20 Selection of adopted technology The selection of the language and tools to be used is left to each team. Refactoring Business members understand the importance of refactoring. Sometimes we work on it as a P1 task, and sometimes we refactor it at the same time as developing features.
21. 2020 © Feedforce Inc. We also value frequent information sharing and communication 21 Kickoff Share the same goal at the beginning of a project or at the end of a term. Morning assembly We share information and discuss problems within the team and the professional axis. Team Lunch Once a month, we have a program to promote lunch with four or more people. Chat time During MTGs and during work, chit-chat will suddenly start. Documentation Leave rules, specifications, knowledge, etc. in esa or Github.
22. 2020 © Feedforce Inc. Facilitate the output of knowledge and experience 22 FFTT This is a time for each team to share their work and problems that have arisen, and for the person on duty that week to present what they have learned recently. Some of us talk about coffee as well as technology. Technician Blog We publish articles about more practical experiences, such as insights gained in our work, difficulties encountered, and thought processes.