But does the band ever want to get back together? Sure maybe it worked for a reunion gig where everyone rejoiced at the good old days. But could they do it again? Do they want to do it again? Bands do get back together, they do succeed when they get back together, but only when they are willing to try something new, only when they are willing to let go of what they accomplished before…
Who does what? Who actually does what? Who needs support? Who is struggling? Who is doing great but getting lazy because they aren’t learning anything? Who is overloaded? Who is being missed? Who needs a kick? These are the questions you need to ask yourself when taking stock of your team. This is what helps you understand who needs help, where and when and how to plan your strategy out to help them.
I’ve done 1 week to 6 week sprints (yes at 6 weeks we called it a sprint) – if you’re not sure what fits best for you, here’s some guidance. 1 Week – It’s all bugs, it’s all known quantities, you have minimal code and your deployment model is code, commit, deploy. QA happens when you ship to Production, teams of 1 – 2 developers. The Theme is “MVP”. 2 Weeks – User Stories are…
Can we put everything into this fix to get it right and get it out there? Have you tried putting everything into one fix? I remember when 100 MB was considered too big for a patch and now I’m downloading 20 GB updates. Focus your fixes on the problems they are meant to solve – no one ever complained about a fix that addressed the one issue it was meant to.
In video games, there are many side-quests to getting to your primary quest. They might give you XP (experience) to help in your primary quest (i.e., unit testing, additional coding, etc, etc). We sometimes discard them because – “Bah, when am I going to use this” – but then when we complete the primary quest, we begin the work to go back and clean up our side quests and think – “huh, this would have…