Project Management in LINE NEWS Service Development

Masaki Nakagawa
Service Development Department 3 Senior Manager
https://linedevday.linecorp.com/2020/ja/sessions/9535
https://linedevday.linecorp.com/2020/en/sessions/9535

Transcript

2. Agenda › About LINE NEWS › Important Factors in Development › Approach to Issues
3. About LINE NEWS
4. History 2020 2017 2013 Launch App & Web Launch News Tab Sunset App
5.   2020 2017 2013 75M (MAU) . 17.5B (MPV) . .
6. Contents News Earthquake Train Info Fortune Telling
7. 50+ 14 14 Product Planner Front-End Engineer Server-Side Engineer QA 10 1 PM
8. Development Team Manager Manager Leader PO PO LE PO Cross-Functional Small Teams LE LE Product Owner Lead Engineer Product Planner Front-End Engineer Server-Side Engineer QA PM PM
9. Cross Functional Small Team
10. MySQL Redis Kafka CDN CMS App Memcached User External Contents Batch Operator API
11. Traffics 00:00 12:00 20:00
12. Stability
13. Content Collect Content Deliver
14. Many Types of Content News Earthquake Train Info Fortune Telling
15. ex1. RSS Importing System MySQL Redis Kafka CDN CMS App Memcached RSS & Media Contents Batch API
16. MySQL Redis Kafka CDN CMS App Memcached RSS & Media Contents Batch API
17. MySQL Redis Kafka CDN CMS App Memcached RSS & Media Contents Batch API
18. MySQL Redis Kafka CMS App Memcached Live Data Batch API ex2. Play-By-Play System
19. MySQL Redis Kafka CMS App Memcached Live Data Batch API
20. MySQL Redis Kafka CMS App Memcached Live Data Batch API
21. MySQL Redis Kafka CMS App Memcached Live Data Batch API
22. Design
23. Communication
24. Important Factors Stability Design Communication
25. Approach
26. Development Team 2019 Manager Manager Leader Member Member Member Member Member Member Member Member Member Member Member Member PM Product Planner Front-End Engineer Server-Side Engineer QA PM Planners
27. Development Team 2019 Manager Manager Leader Member Member Member Member Member Member Member Member Member Member Member Member PM Product Planner Front-End Engineer Server-Side Engineer QA PM
28. Problems › Getting increased the dependency on managers/leaders because of organization scaling up › Getting increased the lead time of the product delivery process
29. Manager Manager Leader Member Member Member Member Member Member Member Member Member Member Member Member Manager Manager Leader PO PO SM PO SM SM Product Planner Front-End Engineer Server-Side Engineer QA PM Product Owner Scrum Master
30. Fundamental Problem Manager Manager Leader Member Member Member Member Member Member Member Member Member Member Member Member Planners Communication Gap
31. Why aren’t you cooperating… It’s not funny…
32. Estrangement Stability Design Communication
33. “Heart-to-Heart Talk”
34. Promoting Monotonous Work › Lack of overall service understanding › Lack of communication beyond one’s own area of responsibility › Diminished sense of ownership
35. Backlog Refinement Effects Background Objective Manager Manager Leader
36. Write DesignDoc
37. LINE NEWS DesignDoc Format › Project Info • Members • Glossary › What is this? (Objective) › Why needed? (Background) › Requirements › Design Overview (High-Level Architecture) › Design Details (Low-Level Architecture) › Special Note › References
38. DesignDoc Details › List the members of all roles in this project › Make it clear who to ask when you have a problem Member Glossary › List the terms specific to this project › It’s very helpful when others see this document later Project Info › Link to project proposal document page and epic ticket › Relate planning specifications to development specifications › Project Info • Members • Glossary › What is this? › Why needed? › Requirements › Design Overview › Design Details › Special Note › References
39. DesignDoc Details › Why develop it? › Describe the environmental factors, social context, and business requirements Why needed? What is this? › What will you develop? › Describe purpose and goals › Project Info • Members • Glossary › What is this? › Why needed? › Requirements › Design Overview › Design Details › Special Note › References
40. DesignDoc Details › Describe the overall architecture of the system › It’s better to use a system configuration diagram Design Overview Design Details › Describe detailed design information required for implementation › (e.g.) component diagrams, database schema, and API specifications › Can describe it step by step along with the design, or link to separated documents Requirements › List the functional requirements › Project Info • Members • Glossary › What is this? › Why needed? › Requirements › Design Overview › Design Details › Special Note › References
41. DesignDoc Details › Link to related document that will required in this project › (e.g.) planning specifications, other DesignDocs, and external system specifications References Special Note › Include things like "known issues", "security risks", "project rules", "constraints and prohibitions" › Identify the points that should be taken care of during development, or even after release › Project Info • Members • Glossary › What is this? › Why needed? › Requirements › Design Overview › Design Details › Special Note › References
43. Lead Engineer in Small Team PO PO SM PO SM SM PO PO LE PO LE LE Assign “Lead Engineer”
44. with Background at System-wide Level Stability Design Communication
45. Backlog Refinement with Lead Engineer
46. Lead Engineer Effects › Design decisions are now being made more appropriately › Contribute to smooth communication within the team by leading discussions in Small Team Lead Engineers Themselves › Awareness and responsibility for the role › Motivation is up from Planners › Lead Engineers are generally received favorably, and have received good feedback › Lead Engineers have become a point of contact, so making it easier to discuss and ask questions
47. Lead Engineer Effects › Design decisions are now being made more appropriately › Contribute to smooth communication within the team by leading discussions in Small Team Lead Engineers Themselves › Awareness and responsibility for the role › Motivation is up from Planners › Lead Engineers are generally received favorably, and have received good feedback › Lead Engineers have become a point of contact, so making it easier to discuss and ask questions
48. Lead Engineer Effects › Design decisions are now being made more appropriately › Contribute to smooth communication within the team by leading discussions in Small Team Lead Engineers Themselves › Awareness and responsibility for the role › Motivation is up from Planners › Lead Engineers are generally received favorably, and have received good feedback › Lead Engineers have become a point of contact, so making it easier to discuss and ask questions
49. Maintenance & Refactoring Stability Design Communication
50. Development Infrastructure Team Independent Unit No Product Owner PO PO LE PO LE LE Manager
51. Major Refactoring Issues › Spring Boot Upgrade › Perl2Java Migration › Java Upgrade
52. Conclusions
53. Finding and Solving Problems › We have put in place the Development Team › We have put in place the Development Process › We talked anyway many times
54. We DON’T have any magic.
55. Quick Decision
56. Sharing a Vision
57. Show the Way
58. Thank you