“Who” Creates Risk
Costello: Well then who's on first? Abbott: Yes. Costello: I mean the fellow's name. Abbott: Who. Costello: The guy on first. Abbott: Who. Costello: The first baseman. Abbott: Who. Costello: The guy playing... Abbott: Who is on first!
Today’s blog is triggered by the entry authored by my friend and colleague, Ben Sommer, reflecting on the laziness of describing architecture with pronouns. In our roles as architects, IT strategists, or just technical leaders guiding successful project implementations we frequently find ourselves defining plans and parceling out tasks.
Issue Resolution – Celebrate Your Success
This blog is the third in a series of posts designed to help technical leads get over the hurdles that inevitably pop up during any complex implementation; a series that was started by Understanding the Problem and continued in Determining a Solution.
With the course set and the implementation of the recommended solution underway, it’s time to finish strong. Read more
Issue Resolution – Determining a Solution
This blog is the second in a series of posts designed to help technical leads get over the hurdles that inevitably pop up during any complex implementation; a series that was started with Understanding the Problem.
Once the problem is sufficiently understood, it’s time to roll up your sleeves and get down to business. Read more
Cost, Time, & Architecture – The Zen of Options Analysis
Solution architecture is typically designed within a project context. Although we focus on the right process for this design activity frequently in our blog, the intersection of that process with the process of delivering an actual production solution is very important. Constraints are a key reality in projects, and often they compete with achieving the “right” architecture. A process to guide a design through this gauntlet of project constraints is why we created our “Define Solution Options” process.