Como você compartilha as práticas recomendadas com arquitetos de soluções?

In my experience you learn more on the job than through the theories. For example, you can always go through the official documentation and examples, well-architected frameworks as advised by the vendor and then do a proof of concept(PoC). A PoC is a great way to validate your recommendation and coax the customer into buying your solution.

As per my experience in this area it’s better to share best practices with solution architects through regular meetings, centralized documentation, real-world use cases, peer reviews, mentoring, online forums, training sessions and leadership support.

Sharing best practices with solution architects involves creating a repository of guidelines, conducting workshops, implementing peer reviews, sharing case studies, fostering communities of practice, providing mentorship, encouraging continuous improvement, and establishing feedback mechanisms. These approaches help architects stay updated with new practices, tools, and technologies, and improve their skills through collaboration and knowledge sharing.

In my view, best practices evolve over the time, solution architecture core principles never change, but vendors, partners and enterprise architects keep developing use cases to fit to business needs and derive outcomes. as these solutions evolve , it is solution architect responsibility to document, create blogs, participate in road shows or demos and share the knowledge.

I formulate best practices related to a particular problem domain and solution implementation areas. I keep them illustrative and practical as much as possible, driving from our past experiences and relevant studied.

Sharing best practices with solution architects is all about collaboration and communication. Regular workshops, knowledge-sharing sessions, and creating a centralized repository for resources can be highly effective. Encourage open forums for discussion and innovation, ensuring a continuous flow of ideas and improvement.

Sharing best practices with solution architects is crucial for promoting consistency, efficiency, and excellence in solution design and development. Here are some effective ways to share best practices with solution architects: 1. Documentation: Create Comprehensive Documentation: Develop detailed documentation that outlines best practices in solution architecture. This can include design principles, patterns, guidelines, and coding standards. Use Templates: Provide templates for architectural documentation to ensure consistency in the way solutions are documented across different projects. 2. Knowledge Sharing Sessions: Hold Workshops and Training Sessions: Organize workshops and training sessions to share best practices.

Sharing best practices with solution architects involves effective communication and collaboration to ensure that they have the knowledge and resources needed to design optimal solutions. Here are some strategies for sharing best practices with solution architects: * Documentation: * Training and Workshops: * Knowledge Sharing Sessions: * Mentorship and Coaching: * Community Engagement: * Peer Reviews and Feedback: * Continuous Improvement: Foster a culture of continuous improvement where solution architects are encouraged to experiment, innovate, and iterate on their designs based on feedback and lessons learned. Encourage a mindset of curiosity, openness to new ideas, and willingness to challenge the status quo in pursuit of better

The way I keep abreast is to network, whether its a forum, user group or community, exchange ideas with your peers. Always expand your sphere of influence to adjacent practices and learn how to synergize with them.

Our team gets together every two weeks to swap success and more importantly challenging use cases. This helps others succeed and/or avoid pitfalls and it's an informal discussion, akin to story telling which makes it an enjoyable event everyone likes to participate in.

It's important to make distinctions between standards and guidelines to ensure there is an understanding of which are required practices and which are suggested or recommended practices. Often, ensuring that required standards are applied consistently is a critical success factor to preserving the health and longevity of a solution architecture. Applying recommended guidelines, on the other hand, may be left up to the discretion of the solutions architect. Much of this clarity can be established in a good governance framework.

I agree. Following are the key points: - Defining and evolving solution and reference architectures overtime - Create, maintain and share architecture repositories, principles and practices - Define project architectures, track them, review and discuss within architecture board and other key stakeholders

Effective solutioning: - Templatizing solution plan - Creating repositories for reference solution documents - Identifying the correct archetype - Preparing composable solutions with right customisation fitting the customers'/industry's need.

This is an interesting question. In my world if you are considered a Solution Architect with 25+ years of experience then you already know the best practices and they should be the ones teaching others what they are. If you have to spent time teaching them, then are they a Solution Architect? Not in my book and I would likely be firing them not teaching them. But a part of our process on best practice training is: maintain a knowledge base and wiki with practices highlighted and examples of use, mentors who help younger engineer see the use cases, required certifications that teach practices, and personal study. Every engineer should spent 15-30 min per day maintaining their industry knowledge. It’s part of the job.

One way to share best practices across the architecture and engineering community of an enterprise is by establishing a reference architecture framework. Typically, a group of architects from the Enterprise Architecture (EA) practice is responsible for creating templates for reference architecture artifacts. These can be (in descending order of abstraction) guiding principles, strategies, frameworks, architecture patterns, design patterns, reference implementations, and so on. In the most mature EA practices these artifacts are stored and instantiated in an Enterprise Architecture repository, accessible (with different level of permissions) by the architecture and engineering community, and other stakeholders.

Cultivate a Learning Culture: Foster a culture of continuous learning and improvement within the architecture team and the organization as a whole. Encourage architects to take ownership of their professional development and stay updated on industry trends. Cross-Functional Collaboration: Promote collaboration between solution architects, software developers, DevOps teams, and other stakeholders. Ensure that best practices address not only architectural concerns but also the needs of cross-functional teams. Feedback Loops: Establish feedback mechanisms to gather input from solution architects regarding the effectiveness of best practices. Use this feedback to make continuous improvements to the best practice guidelines and sharing methods.

Adding to the points made already, it is important to remember that standards and guidelines should never become straight-jackets that end up stifling innovation or become an obstacle to change. Standards and guidelines should be in place to bring a sense of discipline and order in a world which can easily run amok with individual preferences. However, they should not become tomes and volumes that are written once and never updated. Just as it is important to keep upgrading the operational world, it is imperative that standards and guidelines are revisited regularly to make sure they remain relevant and current.

In my view followings can be effective keys - - Reference of the best design or solutions done so far - Cost effective and Modern solutions - Consider the all security assurance while solutioning - Refer best examples from cross functions designs - Keep Automation/AI in mind

In my experience of working with geographically distributed teams of diverse roles and experience, conducting solution architecture reviews with stakeholders from diverse background (geographically distributed, diverse roles and different years of experience) does help improve the overall solution. Some of the diverse perspectives learnt from such reviews can be leveraged in subsequent assignments, thereby also helping solution architects improve themselves individually.

Within solution architects community, we can organize peer reviews to share knowledge and best practices. It can be the place to discuss new tech trends and how to apply them in our organization and how relevant they are. The goal is not to have a kind of approval or a validation process but to have open discussions for knowledge sharing.

In my personal experience, thorough study related to the problem in hand plus Peer reviews from other architects when you finalize some architecture is the most effective way to learn and improve your architectural knowledge. That's where they challenge your solution and give you different perspective to think about the same problem. Writing down the reasons behind each decision is the most important part. Also, reading new articles and attending relevant workshops on regular basis always boost your knowledge and keep you updated.

We can create knowledge sharing culture, internal communication channels, collaboration platforms, regular team meetings, Peer-to-Peer learning and mentorship programs. solution architecture forums and communities online, participation in discussions and Q&A platforms

ARBs are my least favourite part of being an architect. Lots of pseudo-architects jostling for attention while I'm trying to meet project-timelines. Attend as many as you can, get good at presenting to others, learn to sell architecture. Critical review will help you hone your skills.

I am a Solution Architect and lead them as well. The thing I teach the most is peer reviews. Do not be so bold to think you know everything and there is only one way to accomplish goals. Talk to your peers and have them comment on your designs and architectures. Learn from one another.

I agree with Saber. Peer review is very beneficial. As solution architect, we have to humble enough to hear others' perspectives of the proposed solution. However, it is important as managers, they need to cultivate a positive environment to make this happen.

There are few generic "best practices". A good solution architecture team will create the standards that work best for the organisation. Artifacts such as documentation or a wiki that outline the decision and the logic that apply to that approach can support future design, avoid mistakes, and support non-technical audits.

Sharing solution architecture artifacts and lessons learned is vital for architects. These resources capture design decisions and outcomes, aiding in knowledge documentation and communication. Formats like diagrams, reports, and blogs offer versatility. By sharing successes, failures, and insights, architects foster learning. Additionally, feedback from peers enhances practices and builds a collaborative community, i firmly believe in peer reviews and using predesigned robust architectural decisions as a standard

Share tools to document architecture artifacts like draw.io for example. Create documents templates to align architects to use the same diagrams models. It simplify the understanding even outside architects community.

One thing I’ve found helpful for building a useful documentation is to adopt a set of tools that translate code into diagrams or another artifacts, such as Plantuml, MADR, Fitness Functions etc. This allows sharing a live and versioned documents with the team members.

The aspect of architecture the most ignored: keeping your collateral and artefacts up to date. Agile Operations is a good way to iterate through your library and ensure they are current. A documented architecture as a point in time is only so useful. Learning from ones mistakes is also extremely valuable. Every one expects that you will not make the same mistake twice. Make sure your documents tell a story and not just vomit out details.

Tooling and Automation: Provide architecture-related tools and automation that align with best practices. For example, automated code analysis tools can help architects identify deviations from architectural guidelines. Integrate these tools into the development process for seamless adoption. Recognition and Rewards: Recognize and reward architects who consistently apply best practices and contribute to improving architectural quality. Publicly acknowledge their contributions within the organization. Online Forums and Discussion Boards: Set up online discussion boards or forums where architects can ask questions, seek advice, and share best practices. Encourage active participation and moderation to ensure quality discussions.

I am a firm believer of mentoring. I mentor and am mentored by peers and seniors alike. Things are not that fundamentally different from back in the day. Basic concepts and approaches are common unto this day. Learn from your the smart people around you before they retire. It will help you figure you own stuff out.

Frameworks, Mindsets, and Examples. These three guide me to be mentored by the senior architects I admire. I use similar perspectives to mentor other aspiring architects. -Your frameworks should be as global as possible. -Your mindset should be scalable. -Your examples should be relevant.

Solution architect mostly are people with logical and structural thinking. One way to start sharing best practices to them is sharing the background, objectives, why it is important, as well as what problems could be solved by the best practices. Solution architect at management level have more practical question such as, how it could benefit us or our company or our customer ? By giving this reasoning, we could have interesting conversation with solution architect

Mentoring, while often seen as a chore by those who haven't yet done it, is a big gift to the more senior architects. The enjoyment of seeing a junior architect or an application engineer grasp a new topic or work through a problem and their gratitude for the help is very rewarding and more importantly it builds good bonds in an organization

I agree with all the points made but the bottom line is there is no substitute for getting bloodied. Pick a project, use technologies that you're not yet an expert in, feel the pain, and when you're done you will have made great strides because you now understand how to use the technology in the real world.

To share best practices innovatively with solution architects in an enterprise, interactive workshops following solution implementation can be highly effective. Engaging the developer community to share stories on the solution's effectiveness and lessons learned is valuable. This gives confidence to the tech and product communities as well. Architects can get great insights and also engage themself in debating what could be next or can be done better. Gamification can also enhance engagement and knowledge sharing. Additionally, conducting Solution Modernization and Technology Stack review sessions can provide valuable insights. I have personally witnessed the effectiveness of these approaches on multiple occasions.

The biggest hurdle to overcome is not usually the topic or technology, but rather finding the right audience and then the peer review that comes with a best practice. A blueprint for sharing can start with reaching out for guidance from a mentor or peer on the topic. Create a narrative and identify the team you would like to present it to. Craft the message based on your insight. Find your internal chat channel and create a custom group for best practices in Solutions Architecture. Sharing internally has the advantage of a familiar audience and raising the overall teams skills. Solicit others to participate and build a repository in a topic driven and shared file system. If it doesn't exist, then create it, then write about it!

Sharing best practices with solution architects involves fostering a collaborative environment. Utilize regular workshops, knowledge-sharing sessions, and documentation. Encourage peer reviews and case studies to illustrate practical applications. Emphasize open communication channels, forums, and collaborative platforms. Facilitate continuous learning through webinars, industry conferences, and staying updated on emerging trends. Recognize and reward adherence to best practices, fostering a culture of excellence and shared expertise among solution architects.

Solution Architecture without Enterprise Architecture is the equivalent of an architect designing houses in a city unconstrained by any overarching city design, planning, etc. Consider coordinating with the Enterprise Architecture function to standardize governance mechanisms, best practices, etc.

A good solutions architect looks at the existing environment and analyzes what technologies are available and what software product must be developed to provide the best solution for the problem that needs to be solved.

Much as we would all like to think that the same challenge can be found in many places, what we all need to remember is that, just like 2 human beings are not same, 2 places facing the "same" challenge are different from each other even if one parameter between them is different. It is important for architects, and their organisations, to understand that what worked in one situation may not work in another and it would not be surprising to tweak things here and there. So, the "total and complete reuse" really remains a utopian concept. However, true architects have the knowhow of what makes a solution tick and they can make the required tweaks to make it work when moving from one challenge to another.

More often than not, knowledge, lessons learnt and best practices remain restricted within the operating environment that the architects find themselves in mostly because sometimes there is a level of information in the details that is specific to that organisation. There should be an incentive from the organisation to allow architects to share on external platforms lessons learnt and best practices without compromising any confidentiality points. The more they are allowed to share and collaborate outside the corporate structure, the higher the chances for them to learn new things and bring them back to their own day-to-day responsibilities and activities.

Architecture Continuum When sharing best practices with solution architects, leveraging consistent, comprehensive documentation with required abstraction and a feedback-driven approach for continuous improvement is essential. Tools like iServer, ArchiMate, LeanIX, and SAP PowerDesigner stand out for their capabilities in facilitating these processes. All three platforms support established methodologies like TOGAF, FEAF, etc., to ensure a common language through a centralized repository. The key to successful knowledge sharing is not just in disseminating information but also in fostering an environment where the architecture community is encouraged to learn, discuss, and contribute to the pool of best practices.