Over the past few years, I would ask Product Managers or Business Analysts to send me some sample requirements so I could help out some new people on our team with how to write requirements. If they were using Agile, I’d sometimes get back a response akin to – “Oh we don’t do requirements, we write notes” or “Yeah, I don’t have anything to send you because we don’t have documents on any of it.”…
When what you are working on gets stale, uninspired, and never changing, it’s easy to get discouraged that “nothing” will get better and the only way to break out of the monotony of it all is to start looking elsewhere. Generally, when we do this we are racing somewhere else for a quick fix to get that change and break the cycle as quickly as possible, before monotony sets in again. It’s why starting new…
Proof of Concepts is great, they solve a piece of a problem in an isolated way with minimal investment. The problem with a Proof of Concept (POC) is when they prove the problem and stay there, they don’t get integrated into the mainline. They don’t get incorporated, they go back on the shelf while the problem they were meant to solve goes on and on and on. And then they nag at the team, because…
Some say you immediately start looking for your next job the moment you get the current one. But that means you’re not focused on giving your best in your current job, instead, you’re focused on what’s next, what’s after, and where are you going afterward. It splits your focus on what you need to do and where you want to go. And it sends the signal you aren’t happy where you currently are and missing out…
What’s your perfect job description? When was the last time you wrote it out? On paper, in front of you? Do you keep it posted so you can check against it each day to see if it is what you want? Are you missing skills to get there? Is that list prioritized or is it spaghetti against the wall to see what sticks? What’s next after you get that perfect job? These are the questions…