Since earlier this week, when we launched our research project on thought leadership in the technology industry, we've already received some very valuable feedback in the Forrester community, where the research plan (a.k.a. the development document) lives. We're looking for as much additional feedback about the topic and approach as we can get before the actual research begins. Many thanks to everyone who has contributed or will contribute soon.
As I explained earlier this week, this is our first venture into Agile Research Development, a very different way of doing research. Since it's officially Agile, I'll use even the thinnest of excuses to explain how we're applying Agile principles. Pictured here is our Scrum Master, Eric Hsieh, taking a picture of our initial list of items that we're putting into the backlog. That chart sits right next to my desk in the Foster City office of Forrester, so I threw in another shot that gives a peek at the scenic view from my desk. (If you've never been to Foster City, it's the mini-Venice of the Bay Area. I could kayak to work.) Also taken from the Agile canon are the user stories that define how we expect the collaboration between us and the Forrester community to operate.
Next week, we'll start incorporating the early feedback into the development document. I'll post what changed, and why, when we reach that point. I also plan to talk about the decisions we've made about our Agile approach, which shouldn't horrify too many Agilists out there. (As is the case with the vast majority of Agile implementations, we're following the Agile playbook as closely as possible, but not strictly to the letter.)