|
Is the Cost of Continuous Integration Worth the Value on Your Program?, Part 3 To continue our story from part 1 and part 2…
|
|
|
Is the Cost of Continuous Integration Worth the Value on Your Program?, Part 2 Let’s set the context (which I did not do in my most recent post–sorry).
|
|
|
Is the Cost of Continuous Integration Worth the Value on Your Program?, Part 1 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 together (argh #1). I had completed much of my code several weeks before (argh #2: who can remember what they’d written several weeks ago?). We wrote code madly for hours, and then tried to make it work, starting about 9pm. It didn’t work. We stayed up all night (argh #3).
|
|
|
OOP Podcast Posted 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.
|
|
|
Updated Agile Program Management Slides Posted 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.
|
|
|
Slides Posted from “Northern Hemisphere Conference Tour” 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.
|
|
|
What Time Was the Knock at the Door? So often we assume the worst and expect delivery and arrival times to be late. We're so convinced that we'll be disappointed that we fail to give proper credit when a promise is kept and a delivery goes as planned. Give a little bit of credit and allow yourself to be pleasantly surprised!
|
|
|
Yak-Shaving and Many Appreciations 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 is good and how much is throw-away. (When I write a book, I have to write enough so my reviewers have enough context to review, but not so much that I’ve gone too far. I find it difficult to know how much to write before review.)
|
|
|
Understanding Loss: A Key to Managing Change By understanding the type of loss that you, or someone on your team has experienced, you enable yourself to process it, grow, and move forward. Sometimes even the gain of one thing means the loss of another. Losses and gains are ultimately changes, which aren't always easy to deal with.
|
|
|
Estimating the Unknown: Dates or Budgets, Part 5 In many ways, estimating project budgets or dates for agile projects turns out to be irrelevant. If you have a ranked backlog, and you finish features, you can always stop the project if you hit a particular date or cost.
|
|