I am so happy to admit to you that I made a mistake.
I thought reaching the goal was the most important thing. “Isn’t that what Scrum is all about?” (I thought). I used to value making sure my team’s completed point values looked good at the end of the sprint. I thought pushing them to produce work would be more helpful so they learned how to commit to a goal. But sometimes that attitude of mine simply encouraged the developers to produce code that either they weren’t personally proud of or that I sure as heck wasn’t happy with when it came to the code review. So what was the value of making it to the goal line if the ball is busted and deflated when it whizzes past?
Keep reading to learn why admitting your mistakes in not only ”okay” but also possibly the most productive thing you can do.
Continue reading Why I was wrong about Scrum + “Hard Goals”
You’re staring at the blank screen and you have no idea what to write. Or maybe you’re staring at a bug in some software you have to fix. Every career has these moments where you have no idea where to start. You’re overwhelmed by the options, and you’ve found yourself firmly in a state of “analysis paralysis.” So how do you get productive when you can’t even begin?
We’ll share a wonderful tip from a surprising place: Hollywood.
Continue reading How To Be Productive + Avoid “Analysis Paralysis”
Ever feel like you have to finish the whole project before releasing it?
By mining an unlikely source, I will show you why these “all or nothing” thoughts are hindering your success. We can observe Charles Dickens’ release process and prove how iterative releases allowed for quick learning and better results for the user.
Continue reading How Charles Dickens Wrote Like An Agile Programmer
Have you ever slipped? Were you seeing positive progress with your Agile team at work only to watch them suddenly return to bad habits? It’s gonna happen. Even when you know the path to success, you and your team are going to backslide into the old behaviors that caused the initial grief. I can imagine it now–someone saying, “Hey! I thought we had a meeting where we agreed to stop doing those things!” Don’t let yourself or your peers make you feel bad for simply being human. I’m excited to share one of my favorite Buddhist stories about self-care which will help you to improve yourself in a healthy way.
Continue reading Fixing Bad Habits By Learning To Love Them: Agile Retrospectives
I can’t solve this one, and I think I need your help. So, a developer was responding to a code review comment I made and they simply asked me, “why would I do that?” I gave my standard, dusty answer: “because you have to code defensively— you don’t know what the future holds.” But I suddenly realized… am I proliferating a fear of the future? How could I code fearfully when I run CubicleBuddha.com where I blog so often about living happily in the present? I’ll share the specific code example with you. I’m hoping to hear from the community whether my solution is “coding in the moment” or if I am actually bowing down to the fear.
Continue reading Is “Defensive Programming” actually healthy?
Cycles, sprints, iterations… these are all buzzwords that the software process community has been using for years. Most of these words were design to help us “fail fast and fail often” so that we can learn more about how our users feel about the stuff we’ve coded. But have these words really helped us? Sadly, for many software developers, these words are empty. We’ll attempt to reinvigorate of these buzzwords (like “sprints” or Agile cycles) by analyzing one of the oldest words in human history: “samsara.”
Continue reading Samsara: 5 Agile Techniques to End Suffering And Increase Learning