How to Managing Software Project in IT Industry

In this 4.0 Industry, technology sector becomes huge and make impact for the whole industry and ecosystem. When application becomes matter, this slides explain some points what we need to managing software project

Transcript

1. How to Managing Software Project in IT Industry Didik Tri Susanto STIKI Malang - 29 November 2019
2. Didik Tri Susanto • Software Engineer • VP of Engineering DOT Indonesia • https://github.com/didikz • Twitter: @didikz • IG: @didikts
3. What Will You Learn... • Introduction in Software Industry and Business • How to Start Building Software • Managing Software Project
4. Software is Everywhere Software is Eating Our World
5. Where is Tech at? Non IT Industry • Government • Military • Education • Factory • Banking • Oil or Mining IT Industry • Startup Digital • E-Commerce • Software House • Digital Payment • Software as a Service • Cloud Provider • IT Consultant • Many more...
6. Where Should I Go? It depends on your goal...
7. Why Software is Need to be Built?
8. • Optimize Business Flow • System Information & Data Analysis • Increase Profit, Reduce Operational Cost • Helping People & Solving Problem • Creating New Ecosystem • Entertainment Purpose
9. Okay, let’s build one . . .
10. The Nature of Software Development
13. Software Development is... • Mostly Complex • Not many people understand enough • Need highly talented and skilled people • Always changing • Abstract • Sometimes mysterious
15. Where Do I Start?
16. Write Code Right Away • Apache • PHP • MySQL • Redis • Supervisor • Mail Server • NPM • Bower • Composer • NodeJS • ESlinter • Vue-cli • socket.io • postman • VSCode • SSH • GCP • Webpack • Gitlab • CI/CD • Selenium • Codeceptio n • Git • etc...
18. Waterfall Methodology • Mostly used at non IT Industry • Dependent to each state • Taking so much time to release a software • Require many documents • Fixed scope based on agreement • Fixed Timeline
19. • Requirement Gathering: 1 month • Design: 1 Month • Development: 3 months • Testing & UAT: 1 Month • Release Day! (After 6 months)
20. Suddenly Requirement has changed during development
21. Agile Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan That is, while there is value in the items on the right, we value items on the left more
22. Project Iteration
23. • Requirement Gathering: 2 Weeks • Sprint 1 - Release Flow A: 2 Weeks • Sprint 2 - Release Flow B, C: 2 Weeks • Sprint 3 - Update Flow A, B & Add C: 2 Weeks
24. Agile Fallacy & Misunderstanding • Agile is faster • Cutting corner to release faster • Scope Horror • Clueless Product Owner / Client • Deadline
25. Managing Your Project
27. • Make sure a project is running well • Manage people and other resources • Resolve impediment or conflict • Being servant leader for the team • Establish communication & collaboration • Coaching the team
28. Management Tools
30. Source Code Versioning : GIT
31. Common Problems • Unclear project goal / requirements • Deadline • Technical Difficulties • Dev team’s problem • Lack of communication • Project overload • Burnout
32. Handling Crisis • Stay calm • Find the problem and plan for the solution • Communicate • Get help • Apologize • Prevent same problem occur in the future
33. Engineering Skill ≠ Managerial Skill Dealing with machine is very different skill set than managing people or project
34. Leader vs Boss A good manager is also a good leader
35. Remember the difference between a boss and a leader: a boss says, “Go”. A leader says, “Let’s Go” Img source: https://www.cleverism.com/leader-vs-boss
36. Do . . . • Listen to your team, do not judge • Be professional and commitment • Be open minded person • Never stop learning • Know your team • Think before taking an action • Focus to build a great software
37. Don’t ... • Underestimate • Debating without valid data • Pushing your team without considering their limit • Follow your ego • Disappear in a critical situation • Accept all client’s requests without consulting to the team first