All next week, colleague Dave West and I will be at Agile 2010. On Monday, I'm doing a workshop on the effect of Agile in technology companies, in the rest of the organization beyond the development team. IT professionals might see a lot of similar effects in their organizations, too. The workshop is chock full of exercises, including at least one serious game. So, expect some Agile fun in the Orlando sun.
At the end of the week, Dave is doing a presentation on the new trend toward product-centricity in IT organizations. How do you combine two disciplines, Agile and productization, to achieve even better outcomes? Dave's a great speaker, so if you're going to be at Agile 2010, you'll kick yourself if you miss his session.
As Forrester analysts, we're always available to our clients for inquiries. If you're in Orlando with us, we'd be glad to try to set up an inquiry face-to-face instead of the typical phone call. Drop me a line at email@example.com if you're interested in meeting while we're at Agile 2010. See you there.
Today was our first official update to the research plan (a.k.a. the development document) for our project investigating thought leadership in the technology industry. A quick refresher: this particular piece of research is our first venture into Agile research development, which (1) applies Agile principles to our research, and (2) opens the project to the community to participate in the research process from start to finish. In other words, we're using the newly-launched Forrester Community as the forum where the voice of the customer will speak directly to us about our research as we're doing it.
You can see the current development document, including the updated text and the comments that inspired those changes, here. As promised, we're also maintaining a change log for tracking these changes over time. (The development document is also versioned, so we can look back on the history of edits through that mechanism, too.)
During a vendor conference, I sat down with 12 application development professionals and asked them a very simple question: "What will be the biggest themes for application lifecycle management be in the next 5 years?" The resulting debate and discussion highlights some key areas that application development professionals should look to when building their ALM strategy.
Who owns the code?
The reality of open source, partner-developed code and vendor value add-ins was not lost on the group. The overarching theme from this discussion was that customer organizations not only need to own the overall supply chain but also are responsible for ensuring its quality. That means, as writing code decreases, inspection, validation, and testing increase. The result is that traceability, workflow, and reporting are inclusive of customer code but also supplier code. For example, defects with an open source project need to be captured, shared, and tracked in a similar way to internal defects. The difference is that, unlike with internal development, those defects will also feature in the open source project and be fixed by people outside of the customer's organization. The implication of licenses and IP ownership was discussed, with one in the group painting a very bleak picture. He described a scenario where because of the result of one massive IP infringement a company is forced to stop operating, with the resulting fallout being a massive, wholesale movement away from open source software and associated complex IP and licensing issues. Though this example was extreme, the group agreed that licensing should be part of the governance for any ALM solution. This increased complexity of code ownership will require ALM solutions to: