I’ve been writing the networking part of the Agile Job Search book, and realized you could use some of the advice before the book is ready. I receive lots of requests to link with people on LinkedIn. Some people I’ve met at conferences or workshops. Some people I know. Some people I share common groups […]
The nice folks at getabstract like Manage Your Project Portfolio: Increase Your Capacity and Finish More Projects. Some of the takeaways they highlight are: Project portfolio management helps you finish your software projects on schedule. You must understand your mission to make choices about prioritizing software projects. Managers must select which projects to undertake and
I’ve been working with several management teams who want me to train them or their project managers to take over the agile training. It’s not unreasonable from their perspective—it’s how they’ve transitioned to all the other process improvement approaches over the years. Except, none of the other process improvement approaches have been built on the
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
I’ve been blogging about agile architecture, and the responses have been fascinating. Some people are totally against the idea of an agile architect, regardless of the size of the program. Others are ready to give me the benefit of the doubt. In this column, let me clarify the case for (or against) the job-titled agile
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