Role Description
Technology Manager
A Technology Manager role is filled by a Technology Services Director, Director of Infastructure, Director of Release Management, Executive Director of Services, or above.
Responsibilities:
SDLC Note Action: AUDIT Workflow Not Needed Chooses the SDLC Design pattern for a given project. Approval; Proceed to Develop Phase
Approval: System Change
Development Manager
A Development Manager role is filled by a Technology Services individual responsible for managing a group of Developers.
Responsibilities:
Approval: Design Worksheet Approval: Technical Specification
Business Analyst
The Business Analyst Role is typically filled by a Technology Services Director or Technology Services Associate. The Business Analyst is responsible for initial problem identification and business need analysis, full life cycle ownership of project data in Display tab on SharePoint, full life cycle communication to end user/project Sponsor about project status and progress, and participates in User Acceptance and Training.
Responsibilities:
All Status changes in SharePoint. Document: Concept Proposal Approval: Project Initiation
Document: Vision and Scope (optional) Document: Functional Specification
Project Manager
The Project Manager manages timelines, coordinates resources, and manages documents associated with the project. The project manager must continually collaborate with the Release Management team throughout the project planning process in order to accurately represent project delivery dates within the Release Calendar.
Responsibilities: Project Plan
Technical Lead
A Technical Lead may be assigned from the Developer team, should the size of the project warrant one. The Technical Lead becomes a liaison between Architect, Project Manager, and
Business Analyst for communicating the Developer team progress, roadblocks, successes, etc. The Technical Lead is responsible for acting as an escalation point for project resource issues, determining response to scope changes, and potentially managing effects of Change Requests. He or she is also responsible for crafting Design pursuant to standards and frameworks
identified for the enterprise architecture. The Technical Lead responds to the Business Analyst’s Functional Specification with a Technical Specification when the size of the project merits one. Responsibilities:
Document: Design Worksheet (depends on project size)
Approval: Design Worksheet (watch for conflict of interests: the author and approver of the Design Worksheet cannot be the same person)
Approval: Technical Specification (watch for conflict of interests: the author and approver of the Technical Specification cannot be the same person)
Architect In larger projects, an Architect will be assigned from the Architecture team. This individual still essentially acts as the Technical Lead for the project.
The Architect is responsible for acting as an escalation point for project resource issues, determining response to scope changes, and potentially managing effects of Change Requests. He or she is also responsible for crafting Design pursuant to standards and frameworks
identified for the enterprise architecture. The Architect responds to the Business Analyst’s Functional Specification with a Technical Specification when the size of the project merits one. Responsibilities:
Document: Build versus Buy Recommendation (depends on project size)
Developer The Developer is responsible for writing code and performing unit tests on code. Responsibilities:
Standardized in-line comments in code. Comments in source code control database. Unit Test results communication to QA Analyst Document: Design Worksheet
Document: Code Review Instructions Document: Code Promotion Instructions Document: Supplemental Testing Instructions Document: Supplemental Training Instructions
IT
Operations Lead
The IT Lead is a member of the Infrastructure team. Responsibilities:
Document: Backup Plan
Document: Server, Network, Storage, and Security Report Document: Capacity Plan
Approval: IT Release Approval
Trainer The Trainer is responsible for creating training documentation and for end-user training. Responsibilities:
Document: Training Plan
Document: Training Document / User Manual
Code Reviewer
Depending upon the size of a project, the Code Reviewer may be an Architect on the Architecture team or a Development Manager or a peer Developer from the Services team. Responsibilities:
Reviewing code written by Developers Document: Code Review Worksheet Approval: Code Review
Release Manager
The Release Manager is a staff person on the QA and Release Management team. To control for conflict of interests, the Release Manager ought never to develop code on the systems that he or she is responsible for releasing code to, except under extreme and well-monitored circumstances.
Responsibilities:
Code builds and compiles
Application configuration management
Strategic bundling of release components (multiple projects in one release) Code promotion to QA and Production environments
Document: Release Plan Status Change: Released to QA Status Change: Released to Production
QA Analyst The QA Analyst is a staff person on the QA and Release Management team. To control for conflict of interests, the QA Analyst cannot be a Developer responsible for writing code. Responsibilities:
Documenting testing procedures Executing test plans
Reporting the results of testing
Collecting the results of Developer unit tests in order to appropriately inform the overall testing process.
Document: Functional Test Plan Document: Structural Test Plan Approval: Quality Assurance Milestone: Failed Quality Assurance Approval: Confirmed in Production
End User Stakeholder Sponsor
The End User is the project originator or Sponsor. The business need that he or she articulates ultimately determines the scope of a project. A project Sponsor may appoint a Stakeholder to serve as the primary “end user,” to review and approve the project documentation and
deliverables. The End User also ultimately determines whether or not a project will be accepted. The End User can change the scope of a project by formally making a Change Request through the Business Analyst.
Responsibilities:
Initiating the project
Requesting changes to scope
Collaborating with all members assigned to project to guarantee successful completion Approval: Concept Proposal
Approval: Functional Specification Approval: User Acceptance (Planning) Approval: User Acceptance (QA) Approval: User Acceptance (Production)