The Microsoft patterns & practices team has been around since2000. The patterns & practices team builds prescriptive guidance forcustomers building applications on the Microsoft platform. The primarymission is customer success on the platform. As part of that mission,patterns & practices delivers guidance in the form of reusablelibraries, in-tool experiences, patterns, and guides. To put it anotherway, we deliver code-based and content-based guidance.
I’ve been a part of the team since 2001. Along the way, I’ve seen alot of changes as our people, our processes, and our catalog ofproducts have changed over time. Recently, I took a step back tocollect and reflect our best practices. Some practices were moreeffective than others, and we’ve lost some along the way. To helpreflect and analyze the best practices, I created a map of the keypractices organized by discipline. In this post, I’ll share the map(note that it’s a work in progress.) Special thanks to Ed Jezierski, Michael Kropp, Per Vonge Nielsen, Shaun Hayes, and Tom Hollander (all former patterns & practices team members) for their contributions and insights to the map.
Best Practices by Discipline
The following table is a map of the key practices used by the patterns & practices team over the years.
| Discipline | Key Practices |
|---|---|
| Management Team |
|
| Architect |
|
| Development Team |
|
| Product Management |
|
| Program Management |
|
| Release Checklist |
|
| Test Team |
|
| User Experience Team |
|
Some practices are obvious, while some of the names of the practicesmight not be. For example, “Fireside chat” is the name of our monthlyteam meeting, which is an informal gathering and open dialogue. I maydrill into some of these practices in future posts, if there’s interestand there are key insights to share.
联系客服
