We are a global team dedicated to developing and managing cutting edge IT systems and business processes.
The Enterprise Applications PMO oversees portfolio and program management within the EntApps organization. We collaborate with business teams during annual and quarterly planning to align with top priorities. Our services include portfolio, program and resource management, along with project tracking and reporting.
Explore our team’s structure in the organization chart.
The IT EntApps Portfolio planning & prioritization process has 6 steps:
This section provides a quarterly inventory of all the committed and planned projects for IT Enterprise Applications. Internal team members can use the IT EntApps Portfolio: Quarter Commits to track initiatives. Each project is ranked using a Corporate Stack Rank to ensure alignment with global optimization goals.
The IT Project Prioritization tracker serves as a centralized tool to log and manage new projects and initiatives. The PMO team evaluates these entries during the IT EntApps Quarterly Portfolio Planning process.
Involves identifying the project’s:
Achieved by:
All projects added to the IT EntApps Portfolio: Quarterly Commits are assigned resources based on priority and categorized under the following labels:
Projects added to the IT Portfolio: Quarter Commits are part of the IT EntApps OKRs for:
The release management plan helps the IT EntApps team to:
Visit the Governance and IT Program Management page to understand the methodology adopted by the IT EntApps PMO team for all GitLab EntApps programs aimed at achieving the following objectives:
When assigned to a project, the IT PMO team is responsible for creating and maintaining the project Epic. A single parent Epic is created together with (up to) 5 child Epics, each representing a distinct phase of the System Development Lifecycle (SDLC). Issues are used as a means to collaborate on ideas, troubleshoot problems, and strategize for their tasks. By using issues, teams can share and discuss proposals internally or involve external collaborators in the process.
To maintain uniformity across all PMO-led projects, the team follows the same Epic templates.
The System Development Lifecycle outlines a structured set of activities conducted at each project stage.
The Intake process begins with the completion of a business requirements document (BRD). This phase bridges the gap between business stakeholders defining project goals and the development team responsible for implementation.
The Define phase focuses on articulating the business problem and establishing the ‘definition of done.’ It includes identifying use cases, affected technologies, and requirements. The primary goal is to document processes and impacted areas rather than resolve every detail. Before moving to the Design phase, approval is obtained from key stakeholders to ensure accuracy and completeness of business requirements.
The Design phase establishes a roadmap for the future state of the project. The project team collaborates with stakeholders to refine requirements and design processes that align with business goals. This phase addresses outstanding details and resolves any questions from earlier stages.
During the Build phase, the project team collaborates with stakeholders to develop scalable solutions that meet business requirements while adhering to best practices.
In the Test phase, the project team works with stakeholders to create test scripts and oversee the User Acceptance Testing (UAT) process, ensuring solutions meet the defined requirements.
The Deploy phase involves creating a comprehensive deployment plan in collaboration with implementation teams. Activities include finalizing launch plans, enabling users, and managing go-live communications to ensure a smooth transition.
Hypercare is the phase immediately following the deployment or launch of a new process in production. During this period, enhanced support is provided to ensure a seamless transition and successful adoption of the new system.
The Maintenance phase begins after the new process becomes fully operational. It ensures the process continues to function as designed, with repairs or upgrades performed as necessary.
To efficiently track program progress, each Epic is assigned a start and end date. The GitLab Roadmap serves as a timeline to visualize and manage these milestones.
IT EntApps teams use GitLab issue boards to strategically plan, organize, and visualize their work. To learn more about how IT EntApps teams manage issue boards, refer to each team’s respective page.
The IT EntApps teams use labels to efficiently categorize issues and epics. A well-maintained, concise label list facilitates dynamic filtering and streamlined management of work. All labels are created within the gitlab.com/gitlab-com top-level group, making them applicable across all projects.
To better organize and manage their work, the IT teams have different label categories. Click on each category to view the current labels utilized by the IT teams:
The team has developed templates based on IT Compliance team guidelines to streamline the creation of comprehensive, well-structured documentation and facilitate efficient information gathering.
The IT PMO team collaborates with project stakeholders to create these documents and ensures that all necessary approvals are captured within them.
The IT PMO team initiates enablement discussions and collaborates with project leads to develop training materials and communication plans as needed.
There are several activities that take place to prepare for new OKRs / commits and report on the current ones:
IT EntApps Portfolio: Quarter Planning meetings to review the list of projects and priorities for the upcoming quarter with the Business stakeholders.
The team follows GitLab meeting practices and standards.
7827eac0)
