Download to read offline
Uploaded bySebastian Helzle
Improving conceptual understanding in development
Sebastian Helzle discusses the importance of conceptual understanding in web development, highlighting the complexities involved in creating usable products. He emphasizes the need for project ownership and communication between development teams and clients, along with the use of agile methods and testing to improve product performance. Helzle advocates for fostering empathy within teams to enhance client relationships and encourage sustainable solutions.
More Related Content
Similar to Improving conceptual understanding in development
Improving conceptual understanding in development
- 1. Improving conceptual understanding indevelopment by Sebastian Helzle
- 2. Who am I? •Developing websites since Geocities was cool ~1996 • Working with TYPO3 since 2005 • Freelance consultant since 2007 • Fell in love with Neos in 2013 • Certified Scrum Master since 2015 • Love hiking, mountains and cooking
- 3. What I willtalk about • Why is conceptual understanding important • Fostering project ownership • How can agile methods help you • What you can do
- 4. Why is conceptual understandingimportant?
- 5. Websites and webappsare not Rocket science Just pieces of code
- 6.
- 7. Idea & finalresult Can look similar but the result might behave unexpected
- 8. So, why arethey complex?
- 9. Organisational complexities • Requirementsengineering • Team work • Limited budgets
- 10. Technical complexities • Dependencies& their management (bower, npm, composer, bundler, …) • Continuous delivery (build, test, integrate) • Performance & scalability
- 11.
- 12. People must actuallybe able to use your product
- 13. What makes aproduct usable? • Customised solutions • Well thought out workflows • Good performance
- 14.
- 15.
- 16. Every change canhave undesired effects • Performance degradation • Usability • Stability issues • Relationship with the client
- 17. There are alreadysome solutions • Automated testing (stability & performance) • A/B testing for user experience
- 18. Sadly, no automatictests for editors efficiency or clients happiness :(
- 19. Clients are usedto bad solutions This is not a good thing!
- 20. Many development teamsdon’t know what clients are doing
- 21. Ignorance? I don’t thinkso (maybe sometimes)
- 22.
- 23. Empathy • Client hasbad experience? -> a team should • feel the urge to improve it • find sustainable solutions • work with the client • try to understand the client • Let a team get to know the client (he’s not the devil)
- 24.
- 25. Retrospectives Talk about yourprocesses, teamwork and growing as a team
- 26. Reviews Do internal reviewsand user testing Let developers present their work Invite the client
- 27. Keep some slackin your planning Improvements need time too
- 28. Don’t kill ideaswith overcomplicated processes A process can be bent
- 29. Refresh a projectsvision regularly Sometimes the trees block your view on the forest
- 30. As a developeryou can • See tasks as challenge • Try to see your work from a different point of view • Involve in shaping a project • Defend your ideas and concepts • Teach others • Cooperate & ask for help • Write down or draw what you know
- 31.
- 32.
- 33.
- 34. More 🐦 @sebobo ✉ me@helzle.it 📖http://www.mind-the-seb.de