After one release that goes well, you’re perfect. If your second and third ones go just as well, you’ll maintain that perfection. But eventually, the more you do, the greater you open yourself up to the chance that something will go wrong, that you won’t have the perfect release. That your code might blow up. That a bug might get missed. What factors outside of your control will cause you to slip? Because presumably, you…
Maybe make a plan (I do this from time to time). Writing it down helps (I heard and have tried). Committing to a schedule (yes this is definitely great). Get a support group (this never helped me too much). Break it into smaller tasks and when you’ve mastered one task, move on to the next (this helps greatly). Always keep challenging yourself with variations on what you are doing (prevents falling into a mold). But…
Good Leaders show up every day, keep things humming, and tell everyone they are doing a great job. Great leaders show up every day, they ensure the team is working on the right things at the right time and aren’t afraid to make a call to change the direction of the ship if it means the team can get better and stronger, they are always looking towards what is coming down the pipe, prepping it…
Have you scheduled it yet? Have you thought about it? Are you waiting for someone else to do it? What’s your Budget? Team events don’t need to be expensive, they can definitely be simple and their entire goal is to bring people together, have some laughs, and get to know each other better. The smallest team events that have been ad-hoc, end of the day, 30 minutes to an hour I rate better than the…
I originally titled this “Components of a Great Sprint Retrospective” – but behaviors is the better word. You can have all the processes and systems you want but at the end of the day, it’s the behaviors that the team excuses that make a team’s Sprint Retrospective successful.