Recently, I attended a two day Scrum workshop. Someone in the workshop asked our facilitator if there was a better way to estimate the amount of work we could accomplish in a two week sprint to avoid dropping work. After some back and forth, our facilitator said, “We are professionals. The team does not hold each other accountable, we hold each other up.”
This comment made me think, “Do we think of ourselves as ‘Professionals’? And if so, what does professional mean to us?”
For most of my life, I only thought of athletes as professionals because there are tiers below the NBA, NFL, NHL, MLB, etc., where people are considered semi-pro or amateur and working towards “professional” status.
So do we, as engineers (quality and software), team leaders, business analysts and others in the technology world, consider and treat ourselves as professionals?
Overall, I think we do because I think professionalism comes down to meeting, and hopefully exceeding, clear expectations.
For example, a professional athlete is expected to be healthy, on time for practice and games, attend team meetings, practice their craft, mentor younger professionals (ie: rookies) and be a role model for non-professionals.
Similarly, as a technology professional, I expect all of my team members to be on-time, attend their meetings, work on their craft, mentor newer team members and more.
I found three tools that helped clarify what it means to be a professional in our technology world.
- Team Agreements – Everyone on the team brainstorms ideas about what expectations they would like everyone on the team to meet. Eventually the team filters the list down to 5-10 clear items to live by. Some examples that my team came up with: Everyone be able to read and diagnosis application errors, have a team discussion for all walk-ins, and take care of yourself first – healthy mind and body = successful team members, to name a few.
- Team Values – Values are your DNA; it’s what drives you and your team. One value my team lives by is “Give a damn.” Giving a damn is a fun way to say you care and when you care about your work, you will give it your all.
- Definition of Done – When you finish a feature, what does it mean to be done? Is the software working? Is the feature in your production environment? How much testing should you do before you consider a feature done? Answering these questions is important because it helps set a professional standard of what it means to be done with your work.
These are some tools I’ve found to be useful. What are some concepts you use to set a level of professionalism?