Task 4: Read the Agile Manifesto and reflect on the implications of your role
I wrote a blog post giving an introduction to the 30 days of testing challenge that I am doing. Today I complete Task 4: Read the Agile Manifesto and reflect on the implications of your role.
The Agile Manifesto has been around since 2001. It is a set of values that 17 thought leaders in the software community could agree on. You can find the Agile Manifesto here. The values and principles described in the manifesto have helped to shape my career.
I started my career as a Software Tester. Then discovered my true professional calling, a Software Developer. As I progressed in my career I started playing leadership roles on the team such as “Scrum Master” and “Tech Lead”. Each of the values has influenced me one way or another. But the one that influenced me the most is “Individuals and interactions over processes and tools”.
Individuals and interactions over processes and tools
Working for SEP gives me the opportunity to work with many different clients and help them solve many different problems. In my experience, the more integrated my client is on the team, the greater chance we have at success. Especially if one of the client team members plays the Product Owner role.
As a Scrum master, I encourage the team to get together often. The team I am on now gets together every day for at least 15 minutes for a stand-up meeting. We also meet 2 times a week for 45 minutes to groom and plan upcoming work. Discussion happens in person and over video call with a couple of remote team members. As a developer, I look for opportunities to Pair Program with someone.
The faster the teammates become friends. The faster the team gels and the faster they start kicking ass. Making friends is something I have to work at but I have some tricks I have used in the past:
- Pair programming. You get to know someone when you share a desk and work together on a problem. Especially if you ever have to wait for tests to run or your C++ to compile.
- Start a team Book Club. On a couple of teams, we did a book club about something we all needed to learn. We met once a week for lunch and ordered in.
- Team lunch. This is even more enjoyable when it is a celebratory lunch as a result of a Release or some other significant milestone
- Team outings. Such as bowling or happy hour
- Complete a task as a team. Start a new feature by creating a story map together or create a Kanban board together.
- Sit next to each other. it is impossible to work, head down and coding for 8 hours straight without taking a break. When taking a break, strike up a conversation with your neighbor.