To continue our story from part 1 and part 2… The teams have determined their individual impediments to Continuous Integration. You, as the technical program manager, and the technical program team can take those impediments, with input from the teams can see the impediments to program-wide continuous integration. You have used a similar problem-solving approach,
Let’s set the context (which I did not do in my most recent post–sorry). Define a Program A program is composed of several feature teams, which may well be working on several projects or different feature sets. I assume they are. The goal of a program supersedes the goal of any of the projects, and
I like continuous integration. A lot. I started being an aficionado of continuous integration back in my senior year of university. It was my very first (and last) team project in my college career. There were three of us. The project manager waited until the night before the project was due to get us all
We are looking for authors for the Agile Journal. Here is the 2012 editorial calendar as a guideline for you: January: Requirements; Agile Game Development February: Low Tech Test Tools March: Mobile, Redefining Quality April: Acceptance Test Driven Development May: What is Quality? June: Agile Management July: Cloud Development August: Business Value September: Agile Testing
When Matthias Bohlen interviewed me for the OOP conference (see my post about the podcast for the OOP conference), he asked how to interview about lean experience. How do you ask potential team members about knowing their WIP limits or knowing how to help the team see its system? Well, I’ve had a chance to
Matthias Bohlen interviewed me as part of the preparation for the OOP conference. We spoke on a wide range of topics, not just my talk which is “Six Behaviors to Consider When Hiring for an Agile Team.” We spoke briefly about program management, which is why I’m leading my influence tutorial. Hear the entire podcast
I missed one presentation in my last post. At Oredev, I had an opportunity to speak with the PMI Sweden folks (at least, the southern Sweden folks). I talked about Agile Program Management, and discussed my current thinking about agile program management. As I’ve been working with clients, I’ve been updating my thinking—what a surprise
I spent the most recent four weeks conferencing. I had a blast. Because I kept traveling, I nicknamed this series of conferences my “Northern Hemisphere Conference Tour.” I’ve posted the slides on slideshare.net. Oct 24-Oct 28, I was in Vancouver, BC at Much Ado About Agile 2011. I delivered a keynote entitled, “Where is Agile
Take a look at Rich’s Resume and Interview Preparation Tips. Look especially at the Value, Action, Method for resume bullets. That’s a great way to describe your experience.
I am writing a book about agile program management. I have some portion of the first draft written. I don’t know how much, because I have not had any review. When I write, I can’t tell how much I’ve written until I have my first review. Then I will know how much I have that