software industry 101 (introduction)

1. Software
Industry 101
Iman Tunggono - 2018

2. About Me
● Gojek Enginner for 3 years
● Total 8 years++ as Software Engineer
● Binusian 2009

3. Software Development

4. Requirement/Analysis
Design
Development/Code
Verification/Test
Maintenance
Classic SDLC
(Software
Development Life
Cycle)

6. From Agile to became Lean

7. Methodology: Scrum
● Inspired from (american) football
● Sprints: 1 - 3 weeks to deliver feature
● Daily Stand-up: Quick update report/re-plan
● Role:
○ Product Owner
○ Development Team
○ Scrum Master

9. Methodology: Kanban
● Inspired from car factory
● Break down the project into kanban cards
● Kanban Board: Place of card that represent process
flow or dstatus
● No Specific Role

11. Agile Manifesto (1/2)
1. Our highest priority is to satisfy the customer through early and continuous delivery of
valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change
for the customer's competitive advantage.
3. Deliver working software frequently, from a coupleof weeks to a couple of months, with
a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they
need, and trust them to get the job done.

12. Agile Manifesto (2/2)
6. The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users
should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes
and adjusts its behavior accordingly.

13. Back Then Today
Requirement/Analysis Analyst
Engineer
Design Architect
Development/Code Programmer
Verification/Test Tester
Maintenance Support
Job Title

14. Practices & Cultures

15. Environment
Deployment
● Local
● Development
● Integration
● Test
● Staging
● Production

16. 1. Code — code development and review, source code
management tools, code merging
2. Build — continuous integration tools, build status
3. Test — continuous testing tools that provide
feedback on business risks
4. Package — artifact repository, application
pre-deployment staging
5. Release — change management, release approvals,
release automation
6. Configure — infrastructure configuration and
management, Infrastructure as Code tools
7. Monitor — Applications Performance Monitoring,
end–user experience
DevOps
=
Developer
+
Operations

17. Extreme Programming
● Pair Programming
● Test Driven Development

18. Scaling

19. Vertical Scaling Horizontal Scaling

20. Load
Balancer
Web
Server 01
Web
Server
02
Web
Server
03
DB
Web Server Cluster

21. MicroservicesMonolith

22. Passenger
Service
Driver
Service
BIlling
Service
API
Gateway
Payment
Service
Trip
Service
Web Portal
Notificatio
n Service

23. Virtualization
● Bare Metal
● VM
● Container (Docker/LxC)
● Orchestration (k8s/Docker Swarm)