How to have a happier software development team?

In the fifth episode of DDD Plus we discussed "How to have a happier team?"

1. How to have a happier team? Masoud Bahrami @masoud-bahrami #DDDP 4 DDD PLUS4 http://DomainDrivenDesign.ir http://DomainDrivenDesign.ir

2. What brings us together?

3. Different lenses of Culture Individual Team Organization

4. Influencer: The Power to Change Anything Motivation Ability Personal Team Organization Does the person believe in the good behavior? Is the person physically able to behave well… Do people react directly to the person about the the bad behavior? Does the person follow others who spread bad bahavior? Does the company reward the bad behavior in some way? Are the physical resources and objets around the person pushing for the bad behavior?

5. culture eats strategy for breakfast --Peter Drucker

6. ( good )treatment over training

7. The gender knot Unraveling our patriarchal legacy

8. Culture values Trust Respect Accountability Continuous learning Flexibility

9. Organizational culture and its effect on the team

10. Suitable work environment Appropriate tools and equipment Suitable work space Cooperation opportunities

11. team's Values

12. Technical Excellence Agility depends on craftsman(woman)ship

13. Candor

14. Sympathy and empathy

15. Courage

16. Make mistake

17. Stream aligned team

18. Multiple teams is anti-pattern

19. Process over people

20. Context no control

21. Amazon Day-one culture

22. No Rules Rules : Netflix and the Culture of Reinvention

23. Keeper test

24. Focus on people Clear and open communication Trust and empowerment A culture of cooperation Balance between work and life

25. The 5 dysfunction of a team

26. Empiricism approach A comprehensive and valuable guide for engineers and engineering managers who seek to improve the efficiency and success of their teams

27. The first rule of every practitioner of a team “Speak positive words into your life every single morning.  Think big.   Think healing.   Think success. think happiness think growth mindset always start the day with positive energy. you deserve it ” --Sylvester McNutt

28. The Mythical Man-Month: Adding manpower to a late software project makes it later. Adding manpower to a late software project makes it later Communication overhead : As team size increases, so does the complexity of communication, leading to inefficiencies Conceptual integrity : Maintaining a cohesive design is crucial, and adding new people can disrupt this Beyond team size, project complexity, technology, and team experience also influence project outcomes

29. The Tuckman model

30. Skill Acquisition

31. Mind over machine

32. Toyota skill acquisition stages Knowledge Understanding Ability Continuous Ability Mastery / Instructor

33. The Dreyfus’s skill acquisition model

34. How to attain new skills Concreate experience is required to attain high level of performance Abstraction makes the task harder to perform

35. Beware that As the people become skilled, they depend less on abstract principles and more on concrete experience