The Dev Manager should always have this number in the back of their head. They should always be working towards it. They see the big picture, they see how the requirements are flowing in, they see how QA is testing, they see how things are working, what is doing well, what is doing poorly, what is slowing down the team, and where they are excelling. They should always have this number in their head +…
Don’t change your process right after you kick off the next release. Don’t change your process mid-release. Doing either of the above actions is guaranteed to throw a wrench into your gears and slow your team down when you need them focused on what they are doing and not how they are doing it. Assuming you’re still delivering, gather feedback and if small tweak it in the next sprint, if it’s big, save it for…
There is a huge gap between what we do and what we track – and that is the gap between code and tickets. There are many great tools out there that can you help you manage one or the other, but the gap between them still exists and all comes down to one simple statement. I don’t want my work to be tracked. “I want to be creative” “I don’t want to be a factory”…
To do all the work you need to do, you need to have a connected environment to a network that not only lets you work on that particular task, but it opens a dizzying array of other things you can be doing. Watching YouTube while you work. Incoming messages coming at you. Seeing twitter updates scroll in. Seeing newsfeeds update. Now more than ever it is a task in itself to get yourself to focus…
Your last project is done. It’s over. It’s complete. It’s left the building. And now, everything you have been putting off has come flooding back to you. You can think now, it’s no longer consuming you and it’s time to finish everything else you put on hold.