Let’s focus on what I consider the capstone to development and “evolution” as an analyst; the ability to learn, recognize and apply patterns.
My personal study of what makes successful teams, to which I’ve recently alluded, is ongoing. Most recently I came across the article “Project teams are not teams”, which seems to provide a pretty direct answer to the question I posit in the title of this post.
Here are just a few impressions I’ve jotted down over the past few weeks that may never evolve into full blog posts, but that I wanted to share just the same. Please feel free to chime in with your support or challenges to my list, or with your own observances.
Adrian Marchis at Modern Analyst posted a helpful article on process mapping describing, among other things, diagramming the “as-is” process as part of the overall process mapping exercise.
A very interesting and active discussion has followed concerning whether modeling the “as-is” process is valuable, or a waste of time and effort.