We can iterate, nimble, agile, push, ship daily and continuously improve as much as we want, but if the team isn’t catching up you’re doing more harm than good. This doesn’t mean you give up, this means you find the breaking points, you find what is holding people back and you zone in on them. Doing the basic math, if they are stuck on Step 1, then you know they are going to be...
Always Lead to Win Always Play to Win. Always Code to Win. Always Bake to Win. Always Ship to Win. Always Wake up to Win. Always Debate to Win. Always Knit to Win. Always Create to Win. Always Check-In to Win. Always Compile to Win. If your whole purpose is to win, in everything you do, how will you focus on growth? What does you being first to complete your code, leaving the team behind do for...
People. A room of people all engaged, all sharing the workload, all working towards a common goal. A team of people that don’t care what their roles are, only what has to get done. A group of people that are less concerned with individual skillsets but more concerned by what they can do if they all pitch in. We all know it, but we often forget just how we really get there (and how we do it...
Dates are great to hit, but if you get there with nothing, with poor quality, with lackluster user support, with no excitement from your team. Did you really hit a date? Better, to focus on the Story, what are we delivering, what are we giving users, what are they getting. If the Story is going to take too long to deliver in the date you have in mind, then perhaps you need to change the Story so...
Have finished feature are okay. Work that gets pushed off to the next sprint, it happens. Features that get canned, it’s not going to stop. All of these “events” happen that shift the development of what we are doing in the delivery of software. However, what is not okay, is to leave what half of the work has been done in the code that renders a feature partially unusable and/or...