Project managers and architects

Project managers and solution architects are really two types of persons, each with their own responsibilities.

  • Project managers ensure the project is finished on time and within budget. Their main concern is the scope and planning of the project.
  • Architects ensure a technical solution that fits the enterprise architecture, now and in the future. Their main concern is avoiding quick and dirty solutions that will become costly in the long run.

Because of these different concerns it is good practice in projects to have not only a project manager, but also a solution architect. The project manager and the architect should work together as a team. The project manager being responsible for the process of the project (like the planning, budget, etc.) and the architect responsible for the solution the project creates.

Because the project manager and the architect have different concerns that could be conflicting sometimes, the project must have a good balance between quality (architect’s concern), time (project manager’s concern) and budget (also project manager’s concern). This sometimes leads to conflicts. Architects tend to create solutions that are "elegant" and reusable and therefore not always within the project scope. The design is made for instance more modular or more easily expandable than strictly necessary within the project.

Although in general this helps the organization in the long run, the project managers have different concerns. Project managers tend to keep the scope of their projects as limited as possible to prevent project risks in terms of time and budget. They want the project to do nothing more than strictly necessary. This conflict of interest can be solved best when the project manager and the solution architect have a good working relationship and they are aware of each other's concerns.

Good social skills are crucial for a good project manager and for a good architect. I have good experiences with projects organized with the project manager and the architect working as a team. It relieves the project manager from dealing with technical issues. Since the technical specialists communicate to the architect and not to the project manager, technical issues are handled by a technically skilled person. Technicians, including the solution architect, are not bothered with process issues like milestones, budgets and reporting to senior management.

In small projects sometimes the project management and architecture tasks are not separated. On the other hand in large projects usually more than one architect is working on the solution. Large project also often have project management at multiple levels.

But just like there is one project manager that has the overview of the whole project - maybe managing multiple teams with dedicated team leaders or project leaders - there is always one and only one (lead) architect. He has the overview of the whole solution. The lead architect can manage multiple teams working on parts of the solution by appointing multiple solution architects. But the lead architect is always end responsible for the complete solution. He will have to sign off all deliverables and makes sure all parts of the solution will work together and form one integral solution that adheres to the enterprise architecture and the requirements.


This entry was posted on Maandag 12 Mei 2014

Earlier articles

Infrastructure as code

My Book

DevOps for infrastructure

Infrastructure as a Service (IaaS)

(Hyper) Converged Infrastructure

Object storage

Software Defined Networking (SDN) and Network Function Virtualization (NFV)

Software Defined Storage (SDS)

What's the point of using Docker containers?

Identity and Access Management

Using user profiles to determine infrastructure load

Public wireless networks

Supercomputer architecture

Desktop virtualization

Stakeholder management

x86 platform architecture

Midrange systems architecture

Mainframe Architecture

Software Defined Data Center - SDDC

The Virtualization Model

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

The Zachman framework

An introduction to architecture frameworks

How to handle a Distributed Denial of Service (DDoS) attack

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

What is Big Data?

How to make your IT "Greener"

What is Cloud computing and IaaS?

Purchasing of IT infrastructure technologies and services

IDS/IPS systems

IP Protocol (IPv4) classes and subnets

Introduction to Bring Your Own Device (BYOD)

IT Infrastructure Architecture model

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

Computer crime

Introduction to Cryptography

Introduction to Risk management

The history of UNIX and Linux

The history of Microsoft Windows

Engelse woorden in het Nederlands

Infosecurity beurs 2010

The history of Storage

The history of Networking

The first computers

Cloud: waar staat mijn data?

Tips voor het behalen van uw ITAC / Open CA certificaat

Ervaringen met het bestuderen van TOGAF

De beveiliging van uw data in de cloud

Proof of concept

Een consistente back-up? Nergens voor nodig.

Measuring Enterprise Architecture Maturity

The Long Tail

Open group ITAC /Open CA Certification

Human factors in security

Google outage

SAS 70

De Mythe van de Man-Maand

TOGAF 9 - wat is veranderd?

DYA: Ontwikkelen Zonder architectuur

Landelijk Architectuur Congres LAC 2008

InfoSecurity beurs 2008

Spam is big business

Waarom IT projecten mislukken

Stroom en koeling

Laat beheerders meedraaien in projecten

De zeven eigenschappen van effectief leiderschap

Archimate

Een ontmoeting met John Zachman

Open CA (voorheen: ITAC) - IT Architect certification

Persoonlijk Informatie Eigendom

Webcast

Live computable webcast

Lezing Trends in IT Security

Hardeningscontrole en hacktesting

Kennismanagement

Information Lifecycle Management - Wat is ILM

LEAP: de trip naar Redmond

LEAP: De laatste Nederlandse masterclasses

Scada systemen

LEAP - Halverwege de Nederlandse masterclasses

Beveiliging van data - Het kasteel en de tank

Waarom je geen ICT architect moet worden

Non-functional requirements

Redenen om te backuppen

Log analyse - gebruik logging informatie

LEAP - Microsoft Lead Enterprise Architect Program

Archivering data - more than backup

Patterns in IT architectuur

Tot de dood ons scheidt

High Availability clusters

Hoe geef ik een goede presentatie

Lagen in ICT Beveiliging

Zachman architectuur model

High performance clusters en grids

Redenen om te kiezen voor Open Source software

Monitoring door systeembeheerders

Wat is VMS?

IT Architectuur certificeringen

Storage Area Network's (SAN's)

Systeembeheer documentatie

Wat zijn Rootkits

Virtualisatie van operating systems

Kenmerken van Open Source software

Linux certificering: RHCE en LPI

99,999% beschikbaarheid

Het infrastructuur model

Sjaak Laan


Recommended links

Genootschap voor Informatie Architecten
Ruth Malan
Informatiekundig bekeken
Gaudi site
Byelex
XR Magazine
Esther Barthel's site on virtualization


Feeds

 
XML: RSS Feed 
XML: Atom Feed 


Disclaimer

The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.

 

Copyright Sjaak Laan