Build Your Agile Tribe One of the reasons I use agile approaches is because they work. Not all of them, all the time. I find that I have to adapt my agile approach to the current context: the organization and its culture, the people, and the product(s) in development. Some people prefer to use a […]
See Your Agile Estimation Traps Agile estimation. Nothing seems to bring more fervor to an argument than by pairing the words “agile” and “estimate.” Well, controversy doesn’t bother me. Here are three estimation traps I’ve seen in agile teams: An expert signs up for their own stories, thinking it will help the team’s throughput. Your
I had a great time recording with two of the guys from the Agile Uprising Podcast. See Create Your Successful Agile Project with Johanna Rothman. We discussed the book. I had an opportunity to rant and rave about many things: agile project managers (no, the term is not an oxymoron) a little about why the
I have a new column up on projectmanagement.com, 3 Questions to Ask Before Estimating an Agile Program. Often, management wants an estimate for the program. I suggest that before a program manager ask the teams to estimate, she learn the answers to these questions from management: How much would you like to invest in time,
See Your Agile Measurement Traps In honor of my new book, Create Your Successful Agile Project: Collaborate, Measure, Estimate, Deliver, this is the second in a series of four trap emails, the measurement trap. Here are three common measurement traps: You/your management thinks velocity is a target or a measure of progress. Someone (often a
I’m writing a geographically distributed agile team book with Mark Kilby. We have a 30-minute timebox each morning to write. (We take time off for holidays, vacations, travel, etc.) Because we’re writing together, we first had to understand what we wanted to write in this book. We created a frame and a story map for
Tom Cagley interviewed me for his Software Process and Measurement Cast (podcast) a couple of weeks ago and the podcast is live. See SPaMCAST 468 – Johanna Rothman, Create Your Successful Agile Project. We had a blast. I ranted and raved (as I am wont to do) and had a great time discussing some of
See Your Agile Collaboration Traps In honor of the impending Create Your Successful Agile Project book release, I decided to send you a four-part series about agile traps. Yes, one for each piece of the subtitle. This one is the collaboration trap. Here are three common collaboration traps: Your team is a component team. (The
Let me summarize what I’ve been talking about in these posts. The problem I’m seeing is that too many teams and organizations plan too much in too much detail too soon. Instead of architectural BDUF (Big Design Up Front), it’s project planning as BDUF. They expect one single person (a product manager or a product
You’ve started thinking in feature sets. Maybe you’ve experimented with rolling wave plans inside one quarter, so you can change and replan as you need to support your project or program. You’ve discussed flow-based roadmapping as a way to create MVPs and MVEs, release smaller value more often so you can make better decisions. You