(2015 - 4/11) Agile Management

CALIBRATE 2015 (4/11) - http://www.calibratesf.com/

Agile Management -- Kate Heddleston

http://engineering.sharethrough.com/blog/2015/11/06/agile-management/

Managers in fast-paced technology companies deal with constantly changing environments - from hyper-growth to employee turnover. As a result, managers need to be agile enough to respond to anything that comes their way. This talk is about how to manage teams more effectively by adopting some of the principles used in agile software development.

Transcript

1. If we built software the way we manage people, we would never ship code.
2. What if we managed people the way we build software…?
3. People
4. Kate Heddleston kateheddleston.com/about @heddle317
5. What is Agile Management?
6. Agile management is a framework for solving problems quickly and iteratively.
7. Continuous planning, testing, and integration.
8. Rapid and flexible response to change.
9. Agile Management Manifesto Management as a service over a position of power Employee well-being over manager self-promotion Communicating ideas over implementing ideas Solving employee problems over aversion to change
10. Solving employee problems over aversion to change.
11. An iterative approach implementing change
12. Assess Problems and Solutions Feedback and Monitoring Implement Change
13. Implementing Change Assess Problems and Solutions Feedback and Monitoring
14. Getting everyone on-board.
15. Feedback and Monitoring Assess Problems and Solutions Implement Change
16. It is your job as a manager to know what’s going on with your employees.
17. You don’t turn off bug-tracking just because there aren’t any bugs.
18. You don’t stop having 1x1s with people just because they say everything is okay.
19. Assess Problems and Solutions Feedback and Monitoring Implement Change
20. Coming up with a clear system for assessing whether the change worked.
21. It’s not enough to slap a bandaid on problems.
22. Let’s say you want engineers to have better test coverage.
23. You decide your team need to write more tests
24. You decide your team need to write more tests You tell your team, “We need to write more tests.”
25. You decide your team need to write more tests You tell your team, “We need to write more tests.” No one writes more tests
26. You decide automation is a better idea.
27. You decide automation is a better idea. You create a code coverage tool that shows PRs their code coverage.
28. You decide automation is a better idea. You create a code coverage tool that shows PRs their code coverage. Test coverage increases.
29. You set a clear goal of 85% code coverage.
30. You set a clear goal of 85% code coverage. PRs can’t be merged without 85% code coverage.
31. You set a clear goal of 85% code coverage. PRs can’t be merged without 85% code coverage. Merging comes to a halt. People are angry.
32. You set a clear goal of 70% code coverage. PRs can’t be merged without 70% code coverage. People are happily merging PRs with 70% code coverage
33. People are willing to forgive a lot if they believe that you care about them.
34. Why is Agile Management so important?
35. Diversity problems are just a subset of management problems.
36. To sum it all up…
37. Agile Management Manifesto Communicating ideas over implementing ideas Management as a service over a position of power Employee well-being over manager self-promotion Solving employee problems over aversion to change
38. Assess Problems and Solutions Feedback and Monitoring Implement Change
39. Questions Kate Heddleston kateheddleston.com @heddle317
40. –Agile Manifesto “That is, while there is value in the items on the right, we value the items on the left more.”
41. Take the org chart and flip it on its head.
42. Bad management is very easy to see, while good management is almost invisible.
43. It’s not your job as a manager to be everything to everyone, but to make sure everyone has everything they need.