I am conducting research into the best practices in how Enterprise Architecture teams perform scenario planning. Enterprise architecture teams are the group to answer questions such as:
- What happens if the business adds a new sales channel?
- What impact does latest technology widget XYZ have on our technology ecosystem?
- How do we ensure that security and compliance is built into new enterprise applications on day one?
I have observed differing practices for arriving at how the answers to the above questions are formed across Gartner clients . I would like to identify both commonality across organizations as well as novel ideas/techniques used arrive at an answer. I am especially curious to know how enterprise architecture teams are preserving the answers to this questions in some form of body of knowledge and how they might be represented in application portfolio management tools.
Got any thoughts you would like to share?
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.