Awareness is the knowledge or perception of a situation or fact, which based on myriad of factors is an elusive attribute. Likely the most significant unasked for skill… perhaps because it's challenging to “measure” or verify. It is challenging to be aware of aware, or is evidence of it's adherence. This session will cover different levels of architectural awareness. How to surface awareness and how you might respond to different technical situations once you are aware.

Within this session we look holistically an engineering, architecture and the software development process. Discussing:

• Awareness of when process needs to change (original purpose of Agile)
• Awareness of architectural complexity
• Awareness of a shift in architectural needs
• Awareness of application portfolio and application categorization
• Awareness of metrics surfacing system challenges
• Awareness of system scale (and what scale means for your application)
• Awareness when architectural rules are changing
• Awareness of motivation for feature requests
• Awareness of solving the right problem

The focus of the session will be mindful (defined as focusing on one's awareness), commentating in sharing strategies for heightening awareness as an architect and engineer.