patterns & practices

patterns & practices

patterns & practices Solution Engineering

This is one of my favorite figures that shows how we do solution engineering in patterns & practices at Microsoft:   Architectural Scenarios It all starts with...

Vision Scope Examples

On the Microsoft patterns & practices team, we use Vision / Scope as a key milestone. It’s where we frame the problem, identify the business opportunity, and paint a vision of the solution. It’s a forcing function to get clarity on the customer, their scenarios, and our scope for the project. We generally use a “fix time, flex scope” pattern, so this means having a candidate backlog that we prioritize with customers.
lessons in patterns and practices

Lessons Learned in patterns & practices

I've been a part of the Microsoft patterns & practices team for several years.  I've shipped a lot of things and learned a lot...

Customer Connected Engineering

Customer Connected Engineering (CCE) is a practices we use across our patterns & practices teams for engaging customers throughout the life cycle. We involved customers during the planning, development, and release of our deliverables. This is a draft slide set that shares how we do Customer Connected Engineering inside patterns & practices, including our key practices and guiding principles.

Best Practices at patterns & practices

The Microsoft patterns & practices team has been around since 2000. The patterns & practices team builds prescriptive guidance for customers building applications on the Microsoft platform. The primary mission is customer success on the platform. As part of that mission, patterns & practices delivers guidance in the form of reusable libraries, in-tool experiences, patterns, and guides. To put it another way, we deliver code-based and content-based guidance.