Adam Gonnerman

My wrists ache. It's been two days since I worked on the line unloading trucks for FedEx, and my wrists still ache. The three week experiment has come to an end, and now I'm considering other options. It was a few weeks ago that I decided to try being a seasonal package handler for Federal Express. My 6 months of unemployment payments had come to an end, and something needed to take its place. It was never going to be enough hours to cover the difference, though. The process was simple enough. I applied online, went through a background check, and was called in for orientation and training. Orientation took just a few hours, and training was covered over two days, a few hours each. Then I went to work on the line, unloading trucks. The first two days they had me pushing heavy packages out onto the conveyer belt from the trucks. It was sweaty work but straightforward enough. Then they put me on small packages, which you would think would be easier, but really it's not. The s...

Job hunting is no fun, and this is especially true in the current job market. Endless applications with little or no response is draining on the soul. Here are some specific annoyances in the job hunt that I feel like listing out.  One of the most common issues is ghosting. This happens when I'm talking to a recruiter or even a hiring manager and they just stop communicating with me. It's a little embarrassing to follow up to try to get a response out of them, so generally I just let it go. Recruiters in particular should be keeping up with their potential candidates, especially after submitting them for a role. But it's about equally bad when I've been through a round or two of interviews and then hear crickets.  Another issue, and probably the most prevalent, is spam. I don't know how many emails, calls, and text messages I receive per week from "recruiters" excitedly telling me about roles that would "be a perfect fit." And then it turns out t...

 Almost 10 years ago I was invited to help set up some computers with Linux distros at a community center in Uberlandia, Brazil. My family had moved to Brazil to be closer to relatives, and I was teaching English as a foreign language while looking for a full-time job in project management. This invite aligned with my interest in doing social good, so I gladly accepted. It turns out that a bank had donated a lot of used computers to the NGO, and we were rehabilitating them for use with one of the Ubuntu derived distros (I don't recall which one). The more I got to know about Estação Vida the more I liked it and felt drawn to its mission. "The philosophy of the Estação Vida Project is based on four pillars: – Ethical Values and Spirituality – Educational Support – Sensitivity through Workshops – Preparation for the Job Market The institution contributes to the neighborhood in a broad way, encouraging the systematic participation of families. It also offers space for the Tele...

The other day I mentioned MoSCoW prioritization method in passing , and I realize it's actually worth a slightly deeper dive. So, I'm including a video here that should help clear it up.

Ideally, backlog refinement should be handled primarily by the product owner with input from the tech lead. The product owner is taking direction from the business on prioritization, and the scrum master simply makes sure refinement takes place. What do you do though when stakeholders aren't in alignment on on the priorities? Here are a few steps I take when this comes up. First, I ensure there's clarity in the backlog items. We need to have well-defined user stories complete with scope and definition of ready clearly outlined. Business value, effort, and dependencies should be plainly stated.  Second, I facilitate a stakeholder discussion based on these backlog items, focusing on organizational goals and not personal preference. This means I need to frame it in terms of return on investment (ROI), risk, and dependencies. Once this is understood by all, we can move on to actual prioritization.  Third, I use a prioritization framework to draw out the relative importance of the ...

When I was being interviewed for my first startup job many years ago my resume still reflected that I had been a minister and a missionary. One of the questions that came up in the group interview was how I thought my ministry experience might benefit me in this particular role. I must have given a good response, because I got the job. In fact, I've brought to my career learnings from both ministry and English teaching (ESL/EFL).  From the world of ministry I first brought working with people toward a goal. This sometimes involved volunteer management as well, though mostly it was working with a team. In Brazil I worked with a team of Brazilians to start a church. In the United States I worked with staff and volunteers to grow the church. People management is one of those so-called "soft skills" that's essential for project management, particularly when it follows a servant leadership model.  When I got involved in Agile, and Scrum specifically, I quickly realized tha...

Some time back I heard about a young man who had graduated college with a technical degree and had gone over a year without finding a job. It's a tough market, of course, but I learned he failed to do something very important, which made it even more difficult. While he was in college he did no extracurriculars, like a computer science club, and he never actually worked. As in, he didn't do any work of any sort. He was a true full-time student with nothing else going on. That's a problem.  When I was in college my plans were very different from where I would up. My heart was set on ministry, and I took every step to prepare myself. I studied, sure, but I also went on a mission internship, did some outreach work with my college class, and supply preached practically every Sunday. I built a background in student ministry that went on my resume.  I have a friend whose daughter is following a similar path in her student career. She's studying natural sciences and has alread...