Please enable JavaScript.
Coggle requires JavaScript to display documents.
03 Team roles and relationships (Relationships and responsibilities…
03
Team roles
and relationships
Main roles
Project
stakeholders
Project manager
Business + system analysts / requirement engineers
Architects, DB admins, release engineers, sys admins
Designers / developers / testers
Business
stakeholders
Project sponsor
System end-users and managers
Subject matter experts
External
stakeholders
Customers (affected by inputs and outputs of system)
Regulators (industry statutory regulatory bodies)
Suppliers (affected by changes to interfaces)
Relationships
and responsibilities
Project sponsor
Owner of new system
Does system meet goals and realise benefits?
Sign-off powers, budget authority
Final decision on all project matters
Accountable for terms of reference
Initiates project reviews
Resolves key project issues
Champions the new system
System end-users
and managers
Are functionality and usability requirements properly specified?
Are the requirements workable and complete?
Represents day-to-day users of system
Subject matter
experts (SME)
Is sometimes an external resource
Might be a "consultant"
Provides answers and ideas on business issues / possibilities
Works with analysts: are knowledge+ideas clear in requirements?
Provides specialist business knowledge
Project
manager
Plans and controls the project
Is project on time + in budget?
Is requirement engineering process being followed?
Resolves requirements conflicts between other stakeholders
Business analysts
(requirements engineers)
Elicit, document, analyse, validate and manage requirements
Earlier involvement than system analysts
Work with senior business + IT staff
Perform feasibility studies
Develop business requirements + business cases
Investigate business problems + propose solutions
Reports + presentations
Solution development
User acceptance testing
Produce supporting models
Systems
analysts
Specialises in analysing, designing and implementing IT systems
More technical focus, so after business analysts
Analyse role of IT in process, current system, document "as is" processes, define new system requirements
Design system to meet requirements, write tech specs for developers, participate in reviews + testing
During implementation, produce documentation + trainer material
Review of system implementation
Technical
architects
Design the solution's technical architecture
Ensure non-functional requirements are met (performance, operating system, network, database, security, auditing...)
Designers
and developers
Create the new IT system to meet requirements
Designers specify the system (navigation, screens, reports, interfaces and components)
Developers turn specifications into code (including unit testing)
Testers
Ensure the quality, design integrity and functionality of the system
Planning test activities, specifying and executing tests
Recording results, checking and reporting progress
Release
engineers
Builds and deploys system, from finished code
Maintains tracking between source code and live environment
Customer
Affected by inputs and outputs of system
Customers' legal rights must be taken into account
Should be informed of changes
Should be consulted regarding preferences / specific needs
Regulators
Many industries have statutory regulatory bodies
Regulatory constraints affect requirements of project
Changes in the law can impact requirements too
Suppliers
May be affected by changes to interfaces
May have to change their systems too
Need to be kept informed / consulted
External roles
and processes
Operations
Responsible for processes and services administered by IT
Factors: internal / external / quality / cost
Take over after system deployed
Should be involved before end of project
Aspects include
Backup / restore
Disaster recovery
User management
Maintenance tasks
Data load and migration tasks
Periodic checks for security vulnerabilities
IT service
management
Strategic approach to managing IT improvements
Frameworks
include...
ITIL
COBIT
Microsoft Operations Framework
Six Sigma
ISO 20000
TOGAF
Users
Customers
Agile
Impact
of agile
Less bureaucracy + documentation
Cross-functional, collaborative, self-managing teams
Work closely with customer, accepting change
Flexible appoach
SCRUM
roles
Product owner
Scrum maser
Development team
Others
Customers
Users
Management
Technical groups
Project management office
DevOps
Multi-skilling of people to make whole development, operations and testing workflow more agile
Characteristics
Automation and monitoring
Continuous integration and deployment
Objectives
Shorter development + release cycles
Dependable releases
Alignment with rapidly changing business needs
Challenges
Culture shift
Conflicting roles and objectives
Architecture requirements
Diagram (c) 2018 Andrew Burgess
QA Apprenticeships