No just as this is not possible in any other maturing field. However, by having sufficient SMEs with diverse backgrounds and skills on your project team, you can cover most of the necessary information needed to deliver a project. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
No.
Knowledge in any field is ever-expanding.
Knowledge is not possessed by mortal individuals but by longer-living communities. That is why we have libraries, and universities, and teaching and learning never stops. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The key here is to define "necessary". Saving Changes...
Every area of knowledge continuously changes through innovation, investigation, discoveries, or according to global, political, or environmental situations. Particularly, Information Technology is one area of knowledge that has the fastest changes through time, so, you can get knowledge about the latest tendencies continuously, taking advantage of the global information provided by the web; but focusing and specializing in one Information Technology field would convert you in an expert in that theme.
In the case of managing an IT project of various disciplines, you can take advantage of the specialized knowledge of each team member, creating a multidisciplinary team. Saving Changes...
George FreemanThought Leader | Author | Architect| Florida, United States
Bahati,
It’s not feasible or prudent for a project professional to become a specialist in every knowledge area within a domain (e.g., information technology). However, focusing on the strategy and structure of a given domain (i.e., the perspective at a 30,000-foot level) provides a path to gain the depth of knowledge one needs to navigate with “material acumen.”
A few years ago I wrote an article on this subject called “The Practice of Architectural Awareness,” which provides a high-level template on how to approach the domain knowledge problem that we all face.
- https://www.projectmanagement.com/articles...tural-awareness
In general, “Architectural Knowledge” is non-engineering, big-picture knowledge that focuses on, as mentioned above, the strategy and structure of domains. It becomes functionally realized when one can understand, interpret and communicate with said knowledge at a given level.
[U] – Understand: Acquire and comprehend domain knowledge
[I] – Interpret: Translating domain knowledge to a strategic and structural level
C] – Communicate knowledge through visualization and in audience vernacular
Although it would be nice to assimilate this type of knowledge with a snap of our fingers, the reality we face is that we need to set “knowledge depth/level” goals. Hence, the concept of “Competency Levels” for architectural knowledge as follows:
[1] – Collaborate: Comprehend, keep up with, and materially participate in domain-specific discussions using audience vernacular.
[2] – Moderate: Moderate debates through acumen-level knowledge (i.e., keen insight) of the subject matter.
[3] – Challenge: Challenge-out resolutions through principled level knowledge of the subject matter.
To further translate:
When it comes to information technology, do NOT focus on low-level implementation approaches and techniques, but instead focus on that 30k foot level where you can see the strategy for solving a technology problem and the principled structural elements that are necessary to provide a solution.
And per the information I provided above, focus initially on the [C]ollaboration level of architectural awareness, that which allows you to materially participate in domain-specific discussions using the audience vernacular.
I know it’s a lot to take in, but taking it one step at a time, works.
