Sprints are a race to get work done in a smaller period of time. We’re not rushing to get work done, hopefully, we’re taking on just what we can, but the word itself is a sprint – so we are trying to get it all done. Farming on the other hand, is slow, meticulous, and planned out by pre-determined steps that take a period of time to accomplish. You can’t demonstrate farming at the end…
There are 85 steps you need to take to deliver that project. All 85 are important. You can’t skip one and expect to be successful. There is an order to those steps that you know are the path to success that you need to take. In your head, you can see them all coming together and working and crystalizing in front of you. But your team can’t, your stakeholders can’t and your customers definitely don’t…
When the email responses have bounced around five times. When the chats are upward of ten responses and each reply is getting lengthier. When side conversations are starting to splinter off. You might have a different set of thresholds in your mind, but having the threshold is important so you can go “I think we need to get together and talk this out.” Your first response from someone might be – “Oh we don’t need…
Prompts are little pushes to help you do something. Reminders and Alerts are great prompts – “don’t forget you have an appt”. But there are other prompts, ones that are more valuable that you can give your team. “Hey, do we need time this week to clean up our tickets?” “We should work on those unit tests for all the code we wrote this past week.” “The team’s delivery is slipping… was there a reason…
There is much discussion about what is written in a ticket and what is actually coded. In some cases, there is alignment, in others, it’s a quick close and onto the next ticket. In this case, the ticket doesn’t tell the story. The solution isn’t to shut down the world while you’re building and reworking all your tickets. The solution is to ensure there is alignment on what the final solution and if there is…