I finally heard about the almost-complete financial numbers from the Agile 2009 conference. The conference is supposed to generate enough monies for the Agile Alliance to fund research, other conferences, guest speakers, and a whole bunch of other initiatives that are on the site. I was happy, because early indications are that we did. No, […]
I receive a number of please-link-to-me requests each week. Some are for products, some are for random sites. I received one a couple of weeks ago and decided not to respond because I wasn’t going to accept the link request. I received another request, this time with a please respond with an “aye or nay”.
Dave and Bob have great comments on my post, Might Three Backlogs Be Better Than One?. Dave is describing situations where management is making reasonable decisions, not incurring management debt, and by extension, technical debt. Bob and I have experience with significant management debt. (Take a look at Musings About Management Debt for more information
I’ve been working with several clients on their transition to agile approaches to their projects. They all have a common state: Many features to implement Huge technical debt Many defects They want to get a handle on all the work they have to do. I suggested they consider three backlogs, making sure that for a
I’m not a fan of ROI (Return on Investment) measures for software, except in the case where you have waste. Several of my clients have huge technical debt which creates waste for the development staff (not just developers, anyone involved with the development of the product). When you’re dealing with waste, user stories just might
I’m slow to post this one: Giordano Scalzo’s lovely review of Manage Your Project Portfolio is up at Reviewing Manage Your Project Portfolio. I love the part where he says: This book is a must read for everyone involved in IT world, from junior developer ’till C-level executive. As usual, Johanna Rothman uses a very
In their comments to my post, Agile and Remote People: Part 1, Telecommuting, Matt, Lisa, Pete, Abby all had great rebuttals. They successfully make their remote teams work. They have successfully built trust. They use a variety of communications tools that allow their team members to work together. Good for them. (I mean it. I am
A twitter follower was concerned with a piece of my post, Do What’s Effective For You, when I spoke of team bits. Was I saying you could not telecommute and do agile? First, let me explain what a team bit is. A team bit is a person or a group of people grouped by geography
At a prospective client, a senior manager asked me, “In agile, when does the spec freeze?” I said it either didn’t, or did at the end of any iteration in which people wrote a spec. He had a puzzled look on his face, so I explained that if you discuss how to design or what
I have an article up on PM Boulevard: Choosing the Strategically Important Work. Enjoy! (I think you need to register for this site too. Free.)