I received two questions this week about how well does agile allow you to do traceability matrix. Very well is the short answer. Here’s why. If you commit to implementing features (not chunks of architecture) based on user stories in an iteration, you know what you’re planning before the iteration starts. Because you’re working in […]
I write a roughly monthly email newsletter, the Pragmatic Manager. I (finally) posted Refocusing: Emerging from the Split Focus Schedule Game. Yes, I’m working on the July issue now. Enjoy!
I have a Stickyminds column up, Does Exploratory Testing Have A Place On Agile Teams? The column arose out of an email conversation I had with Jon Bach. Please leave comments there.
Dwayne’s comment on my post, Architecting from the Features, made me realize I hadn’t provided an example of how I’d changed the book. Head slap on me! One of my rules of writing, which I use when I’m revising because I rarely remember as I’m writing the first draft, is to explain what I’m writing
I’m writing the portfolio management book, and I just finished a whole big re-architecture. I’m so excited. I realize most people aren’t that excited about a rearchitecture :-), especially not of a book in progress. But I am, because I took my own advice. When I started writing the book, I had several partly done
On the long weekends, Mark and I make a concerted effort to clean up the house. That means I have to address all my little piles: go through them, recycle what I can, throw out what can’t be recycled, file others, figure out what to do with the rest. While Mark was helping me bring
I’ve been wanting to start podcasting for a while. Now, I finally seem to have enough tools that I can do it! Thanks to Clarke‘s suggestion, I’m using libsyn, and I do believe iTunes is syndicating the podcast also. So, here is the link to my first podcast: Timeboxes Help Multisite Teams on libsyn. I
I’ve been working with several clients on their transitions to agile–or at least, more agile approaches to their projects. In each case, the managers decided to move towards agile because the technical staff were in their words, “naive” about the project goals. To be fair, none of the projects had a vision or release criteria,
I recently spoke with a project manager. He was concerned about the product managers handing off the requirements to the development staff. He was right to be concerned. Handoffs don’t work. The more people think they are done with “their” part, the less likely you are to receive/finish a great product. That’s because no one
I’ve finally finished my first podcast, and don’t know where to host it. Any recommendations from you folks?