When adopting an agile way of working, changing culture not the banner you put up on the wall. Instead, we apply a set of good practices that help to incrementally and iteratively continuously improve.
Talking about waterfall project management is not something we hear as much in 2022 as we did in 2012 – ten years has changed a lot. That said, I still hear the tone used when talking about the different approaches to get things done, and the question, “why use waterfall?” This article doesn’t answer that question, but it looks at the conversation.
It seems like there are many words we use that may or may not be the meaning or context we actually want as an outcome. The words efficient and effective are two those words. Leaders and team members alike might talk about one more than the other when what we typically need with these to outcomes is a balance.
Back in 2015, I originally wrote this article on Agile Bacon. I wrote this at time while working with teams and leaders that seemed to be struggling to see that things can be better. As leaders, we need to recognize that there will be bad days, but if we work together, fix our challenges, stay focused, and stay positive — we can get through whatever is dealt.
It is not too uncommon for teams to have ebbs-and-flows on the roller-coaster of Forming-Storming-Norming-Peforming. But when teams are using agile frameworks, specifically Scrum, things can feel very chaotic. Let’s explore ten possible reasons for this.
High-performing agile teams are considered self-organizing and accountable. These attributes are put on display during sprint planning when the team decomposes a user story into a list of things that need to be validated and coded to deliver. These things are usually called tasks and when they are, they sometimes are micromanaged. Well, avoid this — these are just the team’s to-do list … read on.
Dealing with defects and staying on top of code bugs can be challenging for teams when you are chasing a release date. Well, take a step back and set aside a day (or few days) dedicated to making code better — Happy Testivus.
No matter what agile framework you are using, the value of an awesome, team-oriented backlog refinement is amazing for the delivery of products your customers will love. Here’s a handful of ideas that should help.
A key ingredient to grit is having a mental image of what things will look like if we are successful. Well, that is what a great vision can do for us, whether we are motivating a product team or a whole organization. A Hero’s Journey is a great format for a vision.
Get updates on new articles, curated helpful stuff, and some positive vibes in your inbox.
Just so you know, all fields are required. Â We promise to keep your information to ourselves and only provide you with what you’ve asked for — more free stuff. Â See our Privacy Policy for data use information.