Stakeholders and their concerns

Stakeholders are parties that have a relation to the system that is being built in a project. There are many stakeholders in a typical project. Some examples of stakeholders are:

  • End users
  • System managers
  • Project members creating the solution
  • Project manager
  • Testers
  • Business managers
  • Financial department
  • Vendors of IT systems
  • System owners of adjacent systems
  • Business partners outside of the own organization

In a project each of these stakeholders has concerns about the new system. These concerns are sometimes conflicting. Some examples of concerns are:

  • End users are concerned with the useage of the new system - the way it will help them perform their daily tasks. The system must provide a fast and always available business service. End users should not be forced to perform tasks in a more complex way that absolutely necessary.
  • System managers want to make sure the newly created system can be managed with the tools they already use. The new system must be fully documented and tested. The system must fit the technology already in place and it must run on already existing infrastructure. The system's components must be serviceable and vendor support must be in place. The system must preferably use proven technology.
  • Project members creating the solution want freedom to create the system in a way that best fits their expertise (Java programmers want to develop in Java, not in .Net). They want the opportunity to find elegant solutions to design and build the system, if possible using the latest technology.
  • The project manager wants to keep the scope of the project as small as possible to reduce project risk. He does not like changes to appear during the project. Therefore he wants to have as many interfaces out of his scope and make other parties responsible for the connectivity of the new system to other systems.
  • Testers want the system to be testable. Therefore they want all parts to be defined in a SMART way (Specific, Measurable, Attainable, Relevant, Time bound). At the start of the project testers want the requirements to be fully clear and testable. Testers want the project team to produce test stubs for interfaces and repeatable test cases for functionality and non-functional aspects. They want to explicitly define all non-functional aspects of the system (like high availability and performance) in advance.
  • Business managers want the new system to have ways to monitor the system on a high level using for instance KPIs (Key Performance Indicators). They want reporting capabilities for their superiors and their customers. They probably want the new system to have connectors to be able to connect to business partners.
  • The financial department wants to use their knowledge in the purchasing process of the project. They want to be able to negotiate with vendors of IT solutions about terms and conditions and want to reuse already existing contracts with known vendors. They want the new system to be purchased from vendors the organization does business with already.
  • Vendors of IT systems want their customers to use the latest technology they provide. They want to sell licenses and hardware. They want a long term relationship with their customers and want therefore to sell long term maintenance contracts.
  • System owners of adjacent systems in the organization want the new system to seamlessly integrate with the systems already in place. They do not want to create new interfaces or perform many tests. It can be a challenge to get specialist staff appointed to the project, since they are usually busy with their own systems.
  • Business partners outside of the own organization want the new system to follow their internal procedures and interfaces. They do not want to be bothered with the fact that a system is replaced by a new system.

The examples above are just a few of the concerns a few of the stakeholders have. In the real world many more stakeholders exist and the concerns may be much more complex. Therefore for a project to succeed proper stakeholder management is crucial.


This entry was posted on Vrijdag 15 Maart 2013

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