Software Engineering, Project Management, and Effectiveness
A final PDF is now available for our patterns & practices Application Architecture Guide, second edition. This is our platform playbook for the Microsoft application platform.
Here are the relevant links:
Here are some of my related posts:
This post is a summary of my lessons learned from leading distributed teams. I've managed distributed project teams since 2001, spanning the UK, Argentina, India, and other parts of the world. While I preferred having everybody together on site around a whiteboard to simplify and improve communication, flexibility with distributed teams gave me access to the right talent, wherever it may be.
Key Challenges These are some of the most common challenges I faced:
Distance didn’t matter as much as differences in time zones. If the time zone differences were too much, it meant a lot more information, knowledge and state had to be packaged up and handed over. However, when you leverage time zone differences, the experience can feel like you carry the baton forward, or, it’s like “The Elves and the Shoemaker,” where you make progress around the clock.
Success Patterns for Distributed Teams The following success patterns helped improve distributed team effectiveness:
No single pattern is a silver bullet. Instead, it’s the composition of these patterns and practices that help improve distributed team communication and overall effectiveness.
Tools of the Trade The following are some common tools of the trade:
What about you? … What have been your best lessons learned when it comes to distributed teamwork?
The Microsoft Application Architecture Guide, 2nd edition, is now available on Amazon and should be available on the shelf at your local bookstores soon. The PDF was downloaded ~180,000 times. This is the Microsoft platform playbook for application architecture. You can think of it as a set of blueprints, and as your personal mentor for building common types of applications on the Microsoft platform: mobile, RIA, services, and Web applications.
The backbone of the guide is an information model for the application architecture space. It’s a durable and evolvable map to give you a firm foundation of principles, patterns, and practices that you can overlay the latest technologies. It’s your “tome of know-how.” While it’s not a step-by-step for building specific applications, it is a pragmatic guide for designing your architecture, with quality attributes, key software principles, common patterns, and architectural styles in mind. It’s holistic and focused on the key engineering decisions where you face your highest risks and most important choices.
Key Features of the Book The book has several compelling features for slicing and dicing the application architecture body of knowledge:
Contents at a Glance The full Microsoft Application Architecture Guide is available for free on MSDN in HTML. This is the contents of the guide at a glance:
The Team Here is the team that brought you the guide:
Application Architecture Knowledge Base The guide was developed in conjunction with our Application Architecture Guide v2.0 Knowledge Base Project. The knowledge base project was used to inform and steer the guide during its development. The Application Architecture Knowledge Base includes a large amount of material that expands on specific topics in the main guide. It also includes draft material from the main guide that is targeted and packaged for more specific audiences, such as the Pocket Guide series.
Key Links at a Glance Here are the key links at a glance: