Firebrand Architect Cohorts
To manage technical and business complexity every architect needs an effective support group. Rapid changes to business models, ubiquity of computing platforms, and the flood of new technologies make it impossible for an individual to gather and process all the necessary decision making information. Responsible software architects understand that their past experience may not be the best solution for the next problem. Every software architect needs an effective support group to manage change and complexity; every architect needs a Firebrand Architect® Cohort for support.
Firebrand Architect® cohorts are small, exclusive, and discrete groups of architects who seek to improve their software architecture expertise through interpersonal learning with likeminded professionals. Cohort members are professionals leading from the trenches – they bear the responsibility for making early design decisions that fundamentally define and influence software solutions. They solve real world problems and use colleagues from their cohort for decision making support. Members exchange ideas and leverage their experiences to learn, to grow, and to innovate. Participants sometimes use the SEI Software Architecture Paradigm as the framework for discussing architecturally curious concepts. Each cohort forms its own microcosm and no two are alike, however all cohorts are guided by seasoned architects who are passionate about enabling peers to create software fit for purpose. Ultimately cohorts are for software architecture practitioners that understand that becoming better at architecting is a process and not an event.
Firebrand Architect® cohorts are small, exclusive, and discrete groups of architects who seek to improve their software architecture expertise through interpersonal learning with likeminded professionals. Cohort members are professionals leading from the trenches – they bear the responsibility for making early design decisions that fundamentally define and influence software solutions. They solve real world problems and use colleagues from their cohort for decision making support. Members exchange ideas and leverage their experiences to learn, to grow, and to innovate. Participants sometimes use the SEI Software Architecture Paradigm as the framework for discussing architecturally curious concepts. Each cohort forms its own microcosm and no two are alike, however all cohorts are guided by seasoned architects who are passionate about enabling peers to create software fit for purpose. Ultimately cohorts are for software architecture practitioners that understand that becoming better at architecting is a process and not an event.
Cohort Member Benefits
- Cohort members become aware of their strengths and weaknesses of their software architecture skills through feedback from others and self-reflection.
- Cohort members learn how peers apply SEI Software Architecture Paradigm concepts in real world situations, review quality attribute scenarios, review architecture documents.
- Cohort members discuss specific politically charged situations and best ways to address problems.
- Cohort members get feedback on their architectural design thoughts and design decisions, discuss appropriateness of trade off analysis rationale, validity of architectural drivers, evaluation approaches (including ATAM).
- Cohort members exchange ideas and plans for building and growing an Architecture Center of Excellence within their organizations.
- Cohort members discuss approaches for selling the merit of disciplined architecting to senior leadership by showing the benefits and results of using discipline architecture processes and artifacts as a critical asset. This includes building a business case for funding training and sustaining a mature software architecture practice.
- Cohort members build relationships with likeminded architects that last beyond the lifecycle of a cohort.
Cohort Membership Qualification
- You’re passionate about intelligently designed software solutions, and you consistently make reasonable efforts to prevent creation of mediocre software through all phases of SDLC / ALM.
- You have the desire to learn what you don’t know and teach what you know.
- You subscribe to the notion that extensive programming experience, team seniority, and years of experience do not automatically make you an architect.
- You’re able to check your ego at the door, and capable of professionally working with peers.
- Your approach to architecting software systems is methodical and your analysis is technology neutral.
- You’re able to make time to meaningfully participate in cohort activities (absolute minimum 3 hours a week).
- You want to make a positive impact on the evolution of the software architecture discipline.
