Making new work work
Download as PPTX, PDF1 like95 views
The document discusses the concept of 'New Work', emphasizing the need for a purpose-driven culture, transparency, self-organization, and agile methodologies in the workplace. It outlines key strategies for improving team collaboration and the importance of maintaining high coding standards among developers. The authors advocate for a focus on personal development, work-life balance, and continuous feedback within an innovative work environment.
Making new work work
- 1. Jörg Zell | CEO Lukas Guziel, Marcel Liebischer Making New Work work Interaktiv GmbH | www.interaktiv.de | #InteraktivKoeln
- 2. What is New Work? © Interaktiv GmbH
- 4. New Work is a strategic answer to constant change © Interaktiv GmbH
- 5. Why people work Source: Gallup report „How Millenials want to work and live” Past Future My Paycheck My Satisfaction My Boss My Annual Review My Weaknesses My Job My Purpose My Perssonal Development My Coach My Ongoing Conversations My Strengths My Life © Interaktiv GmbH
- 6. Source: https://zerocater.com/blog/2018/06/04/workforce-newest-members-generation-z/ © Interaktiv GmbH
- 7. © Interaktiv GmbH © Interaktiv GmbH
- 8. •Transparency & trust •Purpose driven culture •Agile mindset •Self-organisation •Gamification •Keep things simple •Mentoring & coaching Leadership & Culture Work environment Collaboration #Interaktiv20 19 © Interaktiv GmbH
- 11. Self-organisation is not contrary to leadership © Interaktiv GmbH
- 13. • Transparency & trust • Purpose driven culture • Agile mindset • Self-organisation • Gamification • Keep things simple • Mentoring & coaching Leadership & Culture • Work-life balance • Co-working • Face2face communication • Open spaces • Health • Fun • Zoning concept Work environment Collaboration #Interaktiv2019 © Interaktiv GmbH
- 15. © Interaktiv GmbH © Interaktiv GmbH
- 16. • Transparency & trust • Purpose driven culture • Agile mindset • Self-organisation • Gamification • Keep things simple • Mentoring & coaching Leadership & Culture • Work-life balance • Co-working • Face2face communication • Open spaces • Health • Fun • Zoning concept Work environment • Co-creation • Design thinking • Agile principles & methods • Interdisciplinary teams • Iterative approach • Feedback • Knowledge transfer Collaboration #Interaktiv2019 © Interaktiv GmbH
- 18. Behaviour as a developer„Coding is a marathon, not a sprint “ © Interaktiv GmbH
- 19. 19 | Saying „Yes!“ taking full responsibility © Interaktiv GmbH Saying „No!“
- 21. Use your Mana carefully • Focus – Zone for 2 hours • Multi-tasking does not work Our Approach • Dedicated person for internal support • Time boxes for certain topics • Weekly developer meeting • Developer daily (optional) © Interaktiv GmbHhttps://scryfall.com/card/j16/2/mana-drain
- 22. Collaboration • No lone fighters • Passing on knowledge • Provide help and get help • Respect and appreciation © Interaktiv GmbH Programming is all about communication
- 23. Estimations • Holding on to time estimations.. • Unnessasary preassure • Trust is weakend • More estimations • More experience = Better estimations Planning Poker © Interaktiv GmbH Estimations are estimations
- 24. Practicing ● Make your work to your perfection ● Get into Open Source communities ● Agile game nights ● Gamification: share knowledge Examples : codekata.com © Interaktiv GmbH Your carrer is your responsibility
- 25. Behaviour while coding„Boy scouts need rules“ © Interaktiv GmbH
- 26. Our developer ruleset 98% 1. Boy Scout Rule 2. Functions should serve one purpose 3. Write Test as soon as possible 4. Code > Documentation 5. ... © Interaktiv GmbH
- 27. Rule 1 - Boy Scout Rule “Always leave the code you are editing a little better than you found it.” - Robert C. Martin © Interaktiv GmbH Problem • Code smells sometimes • No time to fix it :-( Goals • Easier to change over time • Small changes instantly • Keep it healthy
- 28. Rule 2 - Functions should serve one purpose Complexity is bad. Keep it simple! © Interaktiv GmbH How? ● Keep your functions small ● Flag arguments are forbidden ● Max parameters: 3 Why? ● Easy to test ● Easy to refactor
- 29. Rule 3 - Write tests in time © Interaktiv GmbH Problem • More and more tasks • No tests = no quality control Solution (Compromise) • Write tests asap, but.. • No internal review without tests • No rollout without tests
- 30. © Interaktiv GmbH Rule 4 - Code > Documentation Problem ● Comments are bad because they are LYING! Solution ● Self-explaining code ● Use code as documentation Goals ● No redundant comments ● No misleading comments ● No commented-out code
- 31. © Interaktiv GmbH 31 | THANK YOU [email protected] @InteraktivKoeln By e-mail: On Twitter and Instagram: Contact us JÖRG LUKAS MARCEL CEO PLONE DEVELOPER PLONE DEVELOPER