At some point in a project, sprint, release, etc we have the process for what we are delivering mapped in our head and we are grinding on it. We are tweaking as we go and it might not be perfect but it’s what we’re doing to get things out the door. We are under pressure, overwhelmed, and trying to keep everything together on a shoestring to get it out the door. As much as small…
Yes, your release is late. Yes, the bugs are piling up. Yes, you have code that needs to go out the door. Yes, your chats are blowing up with everyone and anyone messaging you. Getting angry, chippy, or frustrated doesn’t help the problem and doesn’t help your team. Be the calm within the storm. The release will go out, the more bugs that are found the better the quality, your code will see the light…
No one wants to do the heavy lifting, especially if you’ve done it before, you know just how heavy it can really be and that what is being said at that next meeting or on paper is just a glimpse into what is required. But at the end of the day, it needs to get done and you can either ignore it or start lifting. What you might not realize is that if you’re seeing…
Yes, AI will automate many things. But you will still have to learn how to do things and that will not get faster (depending on your speed of learning). What AI will never automate is our abilities to learn, process and decide. It can provide metrics, analysis, and dashboards, but that last piece will always rest with us and we will always have to take the time to learn new things to be able to…
Developers should be writing code in the current sprint. QA should be validating the code completed in the last sprint and/or bug fixes found in the current sprint. Product Management should be finalizing/confirming requirements for the upcoming sprint and answering questions for this sprint. Only take on what you can do “-1” – the “-1” being something is always going to go wrong, so cramming in your delivery to your topmost capacity is a surefire…