My column, Roll Your Own, about how to organize for teamwork for a geographically distributed agile project team is up. Please leave comments there. Enjoy! Oh, and I am just about to send the logistics email for our workshop next week on geographically distributed agile teams next week in Pleasanton, CA. I am sure we […]
I’ve had several conversations in email and with clients recently that have all been about this question: “What do we do about our infrastructure?” Either the project or the program has to create/update/upgraded their architecture or automated test infrastructure, pay down technical debt, or somehow do something that’s not part of a story. And, that’s
As a consultant, I want the flexibility to adapt my work to take advantage of opportunities that might arise in a given week–to write an article or blog post, or to propose a project to a new client. And, while I try to plan a week’s worth work, I need the flexibility to adapt my
I’m tech-editing an article for the Agile Journal. I’m having a discussion with the author about the words “productivity” and “throughput.” I believe that what we measure in agile teams is throughput, the number of features through the team over time. I don’t think we measure productivity, the number of features per person or per
Back at OOP 2012, I gave a talk called “Six Behaviors to Consider When Hiring for an Agile Team.” These are all team-based, interpersonal skills that any team needs, but are critical on an agile team: collaboration; how to stop when something is good enough–especially when the customer says so; how to ask for help,
I’m doing a webinar with Rally on March 7. It’s about selecting the Number One project in your project portfolio. Please join me and Isaac Montgomery, who will attempt to rein me in (ha!) for What’s the Number One Project in Your Project Portfolio? on March 7. Here’s an excerpt from the description: You have
I posted my most recent Pragmatic Manager: Are Your “Shoulds” Driving Your Decisions? Yes, in case you couldn’t tell, I am doing a series on project portfolio management, so that you do take a look at my Peer Project Portfolio Coaching. Several people took advantage of the early bird pricing. We’re in the not-quite-early-bird pricing
If you missed my most recent Pragmatic Manager newsletter, Focus on One Thing at a Time, it’s posted. In it, I ranted about the delays of multitasking and introduced a new service: Peer Project Portfolio Coaching. I keep seeing people trying to make the transition to agile, still multitasking and not able to say No
A manager took me aside at a recent engagement. “You know, Johanna, there’s something I just don’t understand about this agile thing. It sure doesn’t look like everyone is being used at 100 percent.” “And what if they aren’t being used at 100 percent? Is that a problem for you?” “Heck, yes. I’m paying their
I hope that this 3-part series on how to move to continuous integration and how to evaluate if it’s worth moving to continuous integration on your program convinced you moving to continuous integration was worth it for programs. The reason continuous integration is an issue on programs, is because the lack of CI can delay