I’ve been working on an application that uses Composite Application Guidance for WPF (Prism) and wanted to upgrade to use Enterprise Library 4.1 rather than the 4.0 version that Prism originally shipped against.
Turns out updating this is pretty straightforward (but not trivial)…
Thanks everyone who attended my talk today at Agile Development Practices 2008.
The PDF of the slide deck is available for download and includes some additional speaker notes.
This talk was based on two papers; Agility and the Inconceivably Large and Distributed Agile Development at patterns & practices which include lots more detail I didn’t have time to cover.
The books we based our process at patterns & practices on are listed on our agile showcase page (at the bottom).
The other book I mentioned was “Scaling Lean & Agile Development: Successful Large, Multisite & Offshore Products with Large-Scale Scrum”. It’s not available yet but I wrote about it and how to download a preview chapter here.
During the my repeat of this talk at the UW Extension Program I was also asked how many other teams at Microsoft were using agile approaches. I don’t have any hard numbers but there is some published data on this. You can read about it and my opinion on the data here.
In the future I’ll be publishing more related content on my blog and also on the new patterns & practices Agile Development Showcase - http://www.microsoft.com/agile.
Pat Helland gave an awesome keynote last week at the p&p Summit. I wasn’t able to blog about it until today as he gave the same talk at TechEd in Europe yesterday. You can read the abstract here. He got through over sixty slides in an hour so this just covers some of the things that really grabbed me, and a lot of his talk really grabbed me. I’ve been thinking a bit about Green IT since building a low power home server a couple of months back and Pat gave me a load more stuff to think about.
One of the questions I got at the p&p Summit after my distributed agile development talk was, how do you use Microsoft Visual Source Safe (VSS) with distributed teams?
This is an issue because VSS was never written with distribution in mind. The VSS client connects directly to the database file which needs to be on an accessible network share. Doing this over a less than 100% reliable network eventually results in database corruption. Bad news, and doubly bad news when you’re talking about the database that contains all your source code!
Turns out there’s a fix…
Someone asked me exactly how I configured the fans on my WHS to run really quietly. The previous post on this didn’t have sufficient detail so here’s some more wiring information.
As previously noted I’m going to be in Florida next week speaking at Agile Development Practices 2008 on Thursday afternoon (session details). It looks like there’s a great lineup of speakers for the conference… and then there’s me.
Here’s the abstract for my talk…
Scaling Agile Up and Out: A Tale from the Trenches
It seems like everyone wants to scale their agile teams. As projects grow in scope, the agile approach to software development needs to scale up to larger team sizes. Agile also needs to scale out to handle geographically distributed teams as businesses expand into new markets and seek the best talent available globally. These are challenging propositions for many teams.
I’ll be talking about my experiences at Microsoft—scaling agile up on the Visual Studio Tools for Office team and scaling out on the radically distributed teams within the patterns & practices group. I’ll cover some of the approaches we used—some which worked well, some not so well—and shares that the important thing is what was learned and how this new knowledge can be applied successfully to other projects. I’ll also present some successful practices when scaling agile projects as well as some key pitfalls to avoid on your projects.
Hope to see you there!
John deVadoss and David Hill gave this morning’s keynote at the p&p Summit. They ran through a top ten list of things that p&p will be focusing on moving forward…
We really do want feedback from customers on what we’re building, or planning to build. Leave a comment here or on one of the project discussions on our CodePlex communities.
On Tuesday at the p&p Summit in Redmond J.D. Meier talked for the first time about the work he’s been doing on the new Application Architecture Guide 2.0 for p&p. We’ve just released a beta of this on CodePlex and are discussing some of the thinking behind it with the community.
One of the things J.D. talked about was the Agile Architecture Method, which is something that has fallen out of the enormous amount of thinking and research his team has been doing while working on the Guide.
And just to round out the week, and the p&p Summit Dmitri’s Enterprise Service Bus team have shipped a CTP for ESB version 2.0.
The Microsoft ESB Guidance provides architectural guidance, patterns, practices, and a set of BizTalk Server R2 and .NET components to simplify the development of an Enterprise Service Bus (ESB) on the Microsoft platform and to allow Microsoft customers to extend their own messaging and integration solutions. The Microsoft ESB Guidance consists of a series of inter-operating components that support and implement a loosely coupled messaging environment that makes it easier to build message-based enterprise applications.
This is the first CTP release of the Microsoft ESB Guidance 2.0 for Microsoft BizTalk Server 2009. It incorporates several modifications and additions compared to the November 2007 release. The following list summarizes these changes.
New Features and Components:
Note: This release will be available only for Microsoft BizTalk Server TAP customers at http://connect.microsoft.com/
I said we were going to ship some SharePoint guidance “real soon”. It turns out that this means today, right now!
This guidance helps architects and developers build SharePoint intranet applications. The guidance contains a reference implementation (RI) that demonstrates solutions to common architectural, development, and lifecycle management challenges. This guidance discusses the following:
- Architectural decisions about patterns, feature factoring, and packaging.
- Design tradeoffs for common decisions many developers encounter.
- Implementation examples demonstrated in the RI and in the QuickStarts.
- How to design for testability, create unit tests, and run continuous integration.
- Set up of development, build, test, staging, and production environments.
- Managing the application life cycle including upgrade.
- Team-based intranet application development.
The following areas are not discussed in this version of the guidance:
- Content-oriented sites that use Web content management.
- Internet and enterprise-scale SharePoint applications.
- Multilingual SharePoint applications.
- Scale or security testing of SharePoint applications.
Welcome to my blog on software development and probably a whole lot more. If you're looking for alpine climbing you'll find it on my climbing web site and blog.
