No matter how many teams, no matter how many boards at some point you are going to need one, masterful backlog to rule them all. You’ll need a roll-up, THE roll-up that will signify what everyone in your team is doing. This view isn’t for everyone and it won’t be broken out by sprints (they might be listed and each group might have its own) but invariably they will be listed by resource. And that’s…
I dread being in a meeting with a ton of people I’ve never met because I know it’s coming, the statement that is going to make everyone groan in unison. “Why don’t we go around the room and introduce ourselves!” Truth be told, I’ve never been great at introducing myself, I don’t know why – I mumble some words, hear someone else’s great intro, and then go – “wow that’s amazing” – but I’m still…
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…
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…
If you can’t code 8 hours a day. Can you jump in, on small tasks, and hammer out 1 hour a day? If you can’t do 5 hours a week can you find time to do 3? Bit by bit is the origin story of many overnight successes.