Download as PDF, PPTX
Uploaded byLemi Orhan Ergin
How Do You Build Software? Software Engineering Practices of an Agile Developer
Lemi Orhan Ergin, a principal software engineer at Sony, emphasizes the importance of agile methodologies in software development to address common issues like missed deadlines, bloated costs, and poor product quality. He outlines key principles for successful agile development, including prioritizing customer satisfaction, adapting to changing requirements, and fostering collaboration within cross-functional teams. The document advocates for practices such as continuous integration, frequent releases, and a culture that views developers as talented contributors rather than mere resources.
More Related Content
Similar to How Do You Build Software? Software Engineering Practices of an Agile Developer
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
How Do You Build Software? Software Engineering Practices of an Agile Developer
- 1. Software engineering practices ofan agile developer how do you build Lemİ Orhan ERGİN Principal Software Engineer @ Sony @lemiorhanagilistanbul.com software @lemiorhan ?
- 2. Lemİ Orhan Ergİn PrincipalSoftware Engineer at Sony has worked in Tüsside, BYM, GittiGidiyor/eBay and Sony as lead developer, technical leader, technical coordinator and scrum master got CSM certificate from Jim Coplien year as Scrum Master sprints in 4 years as team member and scrum master experienced in agile transformation and building agile culture in teams & organizations 2001 2013 2009 1 56 agile CSM, PSM1 0.5M total number of views of his presentations
- 3. but it sucks! softwaredevelopment is cool because we hardly find successful software
- 4. missing deadlines extra costs neverused features unknown risks unmotivated employees bugs, failures, errors legacy systems incompetent developers micro managing managers huge technical debts
- 5. are failing Software projects “50%of IT projects go into trash in Turkey” Agile Turkey mercer consulting “When the real costs are added up, 80% of the technology projects costs more than they return”
- 6. only very few canmake it by following non-traditional ways
- 7.
- 8. of reasons to failalotwe have
- 9. company politics some of them aredue to we are unable to do anything here
- 10. developing software in unnatural way butthe reason of all the others is
- 11. The nature of software and9 main rules
- 12. The ultimate goalis customer satisfaction 1 Customers have rights to get software developed with the features they need in a fast way of course, you might not satisfy your customer at this level. that’s fine.
- 13. In general thecustomers do not know what they really want 2
- 14. UNCERTAINITY exists in everystep of development process 3
- 15.
- 16. Software development is notjust 5 Programming
- 17.
- 18. Software development isa social activity 7
- 19. BIG-Up-front detailed estimation &Design are UNNECESSARY 8
- 20. Today or later 9 Youhave to pay the technical debt
- 21. requirements design Implementation verification maIntenance requirements design Implementation developmentprocess of our dreams one step starts after another completes Maintenance
- 22. THE REALITY INSOFTWARE DEVELOPMENT requirements requirements requirements requirements DESIGN DESIGN DESIGN DESIGN DESIGN IMPLEMENTATION IMPLEMENTATION IMPLEMENTATION IMPLEMENTATION VERIFICATION VERIFICATION VERIFICATION VERIFICATION VERIFICATION VERIFICATION MAINTENANCE MAINTENANCE MAINTENANCE MAINTENANCE MAINTENANCE IGN
- 23. agility concept emerges forhelping developers to let them develop in natural way
- 24. Agile development isnot only about project planning Project planning is just a part of agile software development
- 25. Agile software development Agileplanning and management Software engineering practices Customer satisfaction Teamwork Motivation this is the topic we are interested in
- 26. Let’s develop aproject by using agile development practices
- 27. message to companies Seeyour developers not as resources, but talents “ ”
- 28. Define your valuesandlet everyone know Educate everyone up-front Define your team’s norms and values the manifesto
- 29. Build your teamoneteam per product, not per project Cross functional teams swat team sit together Cultivate collaboration culture
- 30. Start the projectandfollow these basic practices Minimum viable product Emergent simple design short up-front design Agile Documenting
- 31. Developmentthat will neverbe the same again use git code branching code / Peer review Pair Programming Clean code principles collective ownership build as if it’s open source refactoring
- 32. testing strategyyou cannever succeed without it TDD ATDD BDD Testing legacy systems A/B Testing chaos monkey MULTI LAYER TESTING design?
- 33. never release anunreviewEd code to production! NEVER!
- 34. reproduce the bugswith tests before fixing it or the fixed bugs may rise again!
- 35. get feedbackas soonas possible, as much as possible code coverage continuous ıntegration continuous build code analysis 10 min build evergreen build status
- 36. continuous deliverybeing alwaysready to go-live snapshots daily Builds continuous delivery central package repository
- 37. release & deployitshould be smooth and error-prune short frequent releases continuous deployment fast bootup devops enterprise environments cloud compatible
- 38. and adabt tochange in any circumstances Building robust, stable, flexible, extensible, high quality software with teams having highly-competent, motivated people in a fast and efficient way
- 39. No methodology isas effective as being passionate and disciplined“ ”AltuĞ AlTINTAŞ Lean-Kanban Consultant
- 40.
- 41.
- 42. Lemİ orhan ergİn lemiorhan@agilistanbul.com @lemiorhan @lemiorhan agilistanbul.com @lemiorhan LINKEDINTWITTERSLIDESHAREBLOG PrincipalSoftware Engineer @ Sony Founder & Author @ agilistanbul.com flyingtomoon.com