First Steps during chaos
30 articles.
2015
2014
- A Value System for Code Reviews, and How to Scale Them for a Large Project
- Signs you might be in survival mode
2013
2012
- Team Leader Manifesto - Take #4
- Team Leader Manifesto - Take #3
- On time, with quality - why is this mostly failing?
- Middle Management or puppet management?
- What should a good code review look and feel like?
- Do new startup leaders need to grow their teams?
2011
- The Chaos Addiction
- Video: How to manage a person who is always late to a standup meeting
- Video: Mistake #1 - Not Understanding Team Maturity
- Video: Ten Mistakes Software Team Leaders Make
- The Fear Of Failure And What To Do About It
- What to do if some people in the team just don't want to take a task?
- Video: Elastic Leadership in software - InfoQ interview
- 12 Behavior Anti Patterns You Will Face As a Software Team Leader
- Slides: Team Leadership In the Age of Agile
2010
- Video – Code Leaders and Beautiful Teams
- The 3 maturity stages of a software team and how scrum fails to identify them
2009
- Do Not Fear Confrontation
- A simple way to know you're missing some leadership skills
- Spend at least 50% of your time with your team
- Step #4 - Start doing code reviews – Seriously
- Daily Standup Meetings - Introduction and 5 useful tips
- If you don’t own your team, Someone else will
- Step #2 – Use a big visible board with post it notes
- Step #1 – Claim Your Territory, Own your team